New Tournament Date - Wednesday, the 24th of August!
The tournament has been moved out to Wednesday, the 24th of August! Thank you for helping us apply pressure to move the date out, it wouldn’t have been possible without your help
New Release
Regarding this latest release, we have put forward a fix for the gold/stone integer overflow issues that have been raised over the past few days. This is basically a check to prevent division by zero.
Thank you @kobus-v-schoor for figuring out this bug and for all the help so far! Could you also just confirm for us that this bug is fixed
Good luck guys, the extra time should help a lot. Please keep the queries and bugs coming!
Just ran my bot that triggered the issue against the new starter pack, looks like the issue is resolved, thanks @Jordan! And thanks for extending the deadline, it is much appreciated
I’ve had a couple of game engine crashes when claiming territory. The game engine crashes completely and the match doesn’t complete.
The error is as follows (sorry, not much to work with):
[ERROR] [Core]: Failed to run GameRunLoop with error: Object reference not set to an instance of an object.
ConState: Connected
Bot: de3cb14b-2f3b-4098-92af-4b80525307f3
[DEBUG] [PLAYERCOMMAND]: PlayerCommand: [ command: {"PlayerId":"de3cb14b-2f3b-4098-92af-4b80525307f3","Actions":[{"Type":3,"Units":0,"Id":"145e424f-e1b3-4f10-a07f-217340873dcc"}]}, , bot: de3cb14b-2f3b-4098-92af-4b80525307f3 ]
[INFO] [ActionService]: Invalid action received
[DEBUG] [Core]: at Engine.Handlers.Actions.OccupyLandActionHandler.ProcessActionComplete(Node node, List`1 playerActions) in /home/runner/work/2022-Arctica/2022-Arctica/game-engine/Engine/Handlers/Actions/OccupyLandActionHandler.cs:line 43
at Engine.Services.EngineService.SimulateTickForBots(IList`1 bots) in /home/runner/work/2022-Arctica/2022-Arctica/game-engine/Engine/Services/EngineService.cs:line 359
at Engine.Services.EngineService.ProcessGameTick() in /home/runner/work/2022-Arctica/2022-Arctica/game-engine/Engine/Services/EngineService.cs:line 193
at Engine.Services.EngineService.GameRunLoop() in /home/runner/work/2022-Arctica/2022-Arctica/game-engine/Engine/Services/EngineService.cs:line 83
at Engine.Services.SignalRService.<Startup>b__8_1(Task task) in /home/runner/work/2022-Arctica/2022-Arctica/game-engine/Engine/Services/SignalRService.cs:line 122
This does not appear to happen when only one of the bots is claiming territory (that is, if I play my bot against three reference bots)
Initially, I thought that was the case. But I have since spotted it in a round with bots that don’t claim territory, so I’m not so sure anymore.
Edit: It happens intermittently, so it’s hard to recreate and I’m speculating on possible causes. Is there anything that would make a claimable piece of land “not claimable”? What would happen if one player were to construct a building on a cell while another player has units on the way to claim it?
What happens if you try and claim a land, and someone builds on said land?
Does this happen when you try and claim Resource nodes, Or perhaps you are claiming open land,
And because the build action was started it completely freaks out.
Thats a case I can think of.
Lol… Replied before I finished reading your post…
The tournament has been moved out to Wednesday, the 24th of August ! Thank you for helping us apply pressure to move the date out, it wouldn’t have been possible without your help
Does this mean entries close Midnight on Tuesday?
Just want to be sure.
it’s midnight Wednesday!
