@Bryukh the ball goes through the wall at the beginning of this match
maybe it’s not bug
ball goes through the wall, but the end, it isn’t inside a wall.
Sometimes, I win as blue, and then lose when I play the same person as red. Or vice versa. For example, Bryukh, I beat you when I play as red, and then as blue, I lose, here’s red: Golden Goal - CodeCombat | CodeCombat here’s blue: CodeCombat - Coding games to learn Python and JavaScript | CodeCombat
I think he means he means if you ghost into a wall, then the ball is dead and it should be respawned
there do seem to be some variations probably because one player gets simulated before the other on frames but I’m guessing some players use random in their code
even you seem to, so it could cause those things
i thought ball’s position is checked only at the end
but i’m not sure. which was expected? @Bryukh
@Bryukh I don’t think this match should be a tie
It happens with the same guy in this match too
Weird. I see the problem but I was sure I fixed it. Let me check.
Oh, my bad. I forgot about some specific case and NaN which can pass through null and type checking. Definitely need to make already some inner use library for type checking.
I got that exact same thing too, was it against QSSJOUMANAE
@Bryukh what about his one
Whats wrong about that? I like this trick 
In the docs its said
- If the ball ends up inside a wall, it is respawned.
So why not.
1 Like
Ok, because I thought it meant if it was in a wall at any time, then it should be respawned 