from rank 19 till 210
from 19-50 as far as the username shows, it ends with WAR
from 51-82 it ends with BRW
from 83-114 it ends with SHM
from 115-146 it ends with OGR
from 147-178 it ends with THR
from 179-210 it ends with MUN
P.S.: I took this screenshot a while ago, now it shows “an hour ago” for the time of submission
I can add a property like vec which returns a Vector. WDYT? Can’t use pos as we mirror coordinates and don’t want to mess with the base code (yeah, maybe Proxy works but it’s better not risk)
Can add.
I know, waiting bot testing results to rebalance colossuses. I think Cronus need some nerfing.
It’s a bug, maybe it’s a reason of OP if Cronus.
Huh? All docs or some? Maybe a permission issue as I see it.
Simply .pos would be ideal, but people would likely use pos.x instead of .x and create a bunch of unnecessary vectors. .xy is another possibility, could signify the meaning better than .vec. I’m usually not a fan of getXXX functions, but CodeCombat uses them around the place. Perhaps a .getPos() method?
I can read .specialRange on a colossus, but not .specialCooldown or .attackRange. I don’t know which properties of that type are readable, but it would be nice if all of them were.
I can now see level-specific documentation as both sides, but Vector documentation is missing when playing as ogres.
Is it possible to separate documentation into different sections for hero commands, unit commands, and colossus commands? I’m thinking like how properties and methods are under different pieces of equipment during campaign levels. Sections could be easier to read than a long list.
Using getPos would be different from the direct access to x and y. xy – I would expect an array or a tuple from that. My point to use vec to show it’s a vector. We won’t use pos for sure (lets think it’s a keyword). maybe position. I’m not sure it’s a big deal as a small percentage of players use this even.
Will recheck their API
I know. Currently – no. We need to update our UI for that as it was made for CodeCombat levels and doesn’t work well when you need create own sections.
Whilst playing as blue (my colossus are on the right, I’m sure you knew that, but just for ease), my colossuses move to their right, rather than to their left.
This would be fine if the x values went from right to left while playing as blue (if a little bit odd), but they don’t, they go from left to right as usual, so this makes playing as blue very difficult because you have to mirror the coordinates yourself to make them work.
I’m afraid I don’t have any clever suggestions for fixing this, but I thought I should point it out.
Danny
Sorry, i didnt get it. So as you subtract X then a red colossus move to the left and a blue one moves to the right. Is it so or both move in the same direction?