Ok, as temp thing Im thinking to respawn a ball if it “unghost” in a wall
Collisions can be nightmare, so I “cheated” a little (plus its more logical imho) – so if you ghost inside a wall, then its the end for the ball and it would be respawned.
Phase shifting and teleports are dangerous abilities if you choose exit coordinated wrong
Boost isn’t working for me, it doesn’t boost when I run this code:
if (count < 2 || count === 4) {
ball.rollTo(62, 85);
ball.rollTo(78, 100);
ball.boost();
} else {
ball.rollTo(69, 30);
ball.rollTo(69, 30);
ball.rollTo(85, 30);
ball.boost();
}
Do you make a roll after that? Boost works for the next roll only.
I will add an icon or visual effect to show when the boost is active.
@Bryukh is ghost supposed to work on hole? Also, the bug where hero.getObstacleAt doesn’t return to null after the obstacle is no longer there is still there
I’ll try that, thanks!
Nope, the hole destroys a ball anyway.
Also, the bug where hero.getObstacleAt doesn’t return to null after the obstacle is no longer there is still there
Thanks. Will check it.
I just ranked my code, but my matches aren’t simulating, last time I ranked my code it only simulated 3 matches in 8+ hours. Is this happening to anyone else, and can I fix it?
Just wait a little bit this happened to me when I ranked mine
Is boost supposed to be able to avoid the hole, because it seems to? Also, what is supposed to happen if you end a ghost in another obstacle
Nope, sounds as a bug. But can be a feature Need to think about it a little.
Also, what is supposed to happen if you end a ghost in another obstacle
I think you would be pushed out, based on where it ends. Need to test. However I don’t want to punish the same as with walls for un-ghost in temp obstacles.
Something weird I’m noticing in my ranked games, whenever I’m blue against a c++ or java user , my code freezes however their code still works causing a draw or loss. I can pm @Bryukh my code to make sure there are no bugs.
this bug is lowering my ELO so much
Oh no. If it’s the bug that I think about, then it’s bad. I thought we solved it, but… maybe not. Could you send me a link to a match where it happens – it would be more useful than your code, as I think the reason is somewhere in C++ error processing.
Match 1: CodeCombat - Coding games to learn Python and JavaScript
match 2: CodeCombat - Coding games to learn Python and JavaScript
match 3: CodeCombat - Coding games to learn Python and JavaScript
there was one more match where it happened but I couldn’t find it.
Hold on, are prizes still the same?
I think the blue spawn delay is shorter than the red spawn delay, watch this:
https://codecombat.com/play/level/golden-goal?team=humans&opponent=688cbfe0bda8eeb9911ce12c
I checked the refereeJS code and it seems fine, but please check it
And Bryukh, if you have time, can you help me with the refereeJS code, I would appreciate the help:
I think it shouldn’t be a feature because boost is already really good
what should I see there? Blue ball respawn in 1 second. Red ball doesn’t respawn.