That’s helpful, thanks.
Suggest adding the healthScoreMultiplier and energyScoreMultiplier to state.json gameDetails for future releases.
That’s helpful, thanks.
Suggest adding the healthScoreMultiplier and energyScoreMultiplier to state.json gameDetails for future releases.
A new release (1.1.3) was just made for the Game Engine, Game Runner and Starter Pack.
Download the new version here
Just when I had a perfect bot… Boom, Maps bigger (G)…
Now I need to calibrate…
New version 2.0.0 for the Game Engine, Game Runner and Starter Pack.
Download the new version here
New version 2.0.1 for the Game Engine, Game Runner and Starter Pack.
Download the new version here
I think something is wrong…
It still looks like a tesla tower is killing its owner…
New version 2.0.2 for the Game Engine, Game Runner and Starter Pack.
Download the new version here
I think something is wrong…
You are absolutely correct. It seems we missed one of the version numberings in the sub projects, this ultimately made the compiled product use older code instead of the actual fixes.
The Tesla Tower will now be attacking enemies instead of yourself
The community is really awesome in helping us spot these things, it is much appreciated
New version 2.0.3 for the Game Engine, Game Runner and Starter Pack.
Download the new version here
Hi guys,
Minor bug, not sure if anyone else has noticed this:
Seems like the building stats as displayed state.json files don’t agree with the stats as specified in game-config.properties.
Specifically:
could you please update examples/example-state.json to an output from a 2.0.3 game?
in games from matches run on the 2.0.3 engine I’m getting constructionTimeLeft values for buildings constantly decrementing after the building is built (eg. -50, -51, etc.). is that intended behaviour?
in the example-state.json constructionTimeLeft gets set to -1 once the building is build and remains there until the end of the game.
I do believe the constructionTimeLeft
decrementing is intentional. They have used it as an indication of building age, which is required to determine which Tesla tower fires first. At least that’s how I read it when analyzing the game round processing code.
@sschocke is indeed correct, thank you for the answer, we have left it in intentionally to do just that.
@MarcinK, I will have the guys take a look at the example and update it to reflect this change.
I don’t know if I’m doing anything wrong, but the results of the match on the portal seem wrong compared to my local (I’m using a tester to check the state files) version 2.0.3. Is the portal using a different version to run matches?
Edit:
Missiles have speed 1 on the portal.
I’ve made adjustments to align with the player on the portal, if it changes back can I please use my previous upload?
Hi @pierre.roux,
I’m a little worried about inconsistencies I get sometimes when I run the engine… sometimes turns are being skipped by one of my bots due to no fault of their own (that I can find)… it may just be that my laptop is a little weak but I’m worried that if the tournament machine is under heavy load it may cause bots to skip turns also (maybe due to a memory IO error or something else???)…
when I run the same 2 bots against each other (neither bot having any randomness programmed in) I get the following:
1st what the result should be:
and then the same test again with an error:
I see on the 2nd run there is an error:
but on the 1st there is no error on round 31:
my bots are written in JavaScript… I don’t know if anyone else with a js bot has come across this problem? or bots in any other languages?
Hi @Andre
To put your mind at ease, I also use JS bots for testing the new features we add into the game (it’s easy to mold JS bots into testers for this purpose ) and I never get the execution failed error on them. This might very well be due to slow I/O if many processes are hogging your resources.
As for the tournament runner, it only runs each bot alone after killing any other bot’s process. This ensures that each bot gets access to all the resources just for itself when it is its turn.
Try and have a look at the BotOutput.txt
file, as this should contain the stdout
or stderr
that NodeJS would print errors to. Or else check if the file write library gets “overloaded” in any way (this is just speculation), so test setTimeout(() => { mainFunctionHere(); }, 100);
in the bot to see if you can replicate it with such delay.
If you can find a way to easily replicate this bug please let us know.
I see it on occasion with Java as well.