I notice the deadline for the changes to the Round 3 code is coming up, and weβre still on the virtually unchanged version of the game engine.
Especially considering the near-unanimous support among lots of players for removing the Perlin noise generation entirely and going back to the old map generation, as well as possibly changing the object generation percentages, I hope weβll see a version with these changes made.
But will we have a chance to review these changes and comment on the balancing of the new percentages, etc, before the deadline, or will the deadline be extended so that we can comment before the final version is decided on?
This might also be important with the number of bugs being found in the damage and speed code - the fixes to this will probably be substantial enough to also need the many eyes of the players to check on it and comment before the final version.
Hi, I was wondering if I could get some clarification on some of the new rules:
Does getting hit by an EMP do any damage/have a score penalty to the player getting hit?
If it is decided that a boost should be capped by the damage (as the current rules state, but not what is currently implemented):
When there is no damage, the boost speed is 15 as usual
When there 1 damage, will the boost speed be capped at 9 or 8? Because, as I understand it, the maximum βnormalβ speed (which you can obtain by accelerating) when your damage is 1 is capped at 8?
If it somehow happens that you are at a speed above your currently allowed maximum speed (not sure if this could happen, but asking hypothetically) will you be slowed down the next/current round to your maximum allowed speed?
I would really like at least 2 weeks from the last bug fix to the tournament. Pretty please ? If that means the third tournament is pushed out a bit does that matter ? There is a large time gap between the third round and the finals.
Yeah, this happens when you boost, and then manage to hold the boost until the counter runs out. Then you drop back to speed 9 (MAXIMUM_SPEED).
Things should correct when next you hit damage, fix car or try to accelerate (I think)
Thank you for all the feedback in this thread, issues on github and issues raised elsewhere in the forum.
We are working on ingesting all the feedback (largely around map gen and the fix mechanic) and will have a new balancing update release for you soon. We are still analyzing all the feedback but once we are done will give an ETA for the new release.
Thank you so much for these fixes.
I think the terrain is quite sparse now but that will allow for more player interaction and less dodging terrain.
Iβm excited to try it all out.
Hi, thanks for all the work on the new release! Iβve been playing around with the new map generation for the past day or two and Iβm really glad that the gigantic blobs of walls and mud have been removed, but I personally think the new maps might have gotten a bit too sparse. I think this is mainly due to the new code that ensures that there is always a path through which to navigate - Iβve found that it often leads to long-ish stretches with nearly nothing on the map with the new damage mechanic also playing a much smaller role - this leads to rather simple navigation which I personally find a bit disappointing. Also, I think there might be a possibility that the code that that makes sure that there is always a navigable path might be biased toward the left side of the map - you can see this if you crank up the mud or wall generation percentage up really high.
This is an example of one the matches with the new map generation (three consecutive rounds, seed 52658):
This morning Iβve been testing the new code and I disabled the bit that ensures that there is always a path to navigate through. I find it to be a good balance between allowing easier navigation and higher speeds but also still making the damage a relevant problem. An example of a map generated with it disabled (also three consecutive rounds, seed 6857):
I realize these are nitpicked examples, but they illustrate my point nicely. Sorry for the long post - Iβm fine either way with the map generation, but I thought I rather say something earlier on while it might still be possible to tweak the game engine.
Hello @kobus-v-schoor and @LouisLotter , thank you for the feedback on the map generation. This version was very generous with the guaranteed path being 15 blocks and the object generation being scaled down.
We may look at reducing the guaranteed path length to get more interesting results but if we do it would be minor. Given this is the final stretch we donβt want to make any major changes to how the engine behaves (bug fixes aside).