Also what API (methods, properties) you would to add to the game? The main rule – if I can see it, I can read it.
Maybe the type of the item, like green or blue
Hi, sorry to interrupt the conversation (if there was one), but I noticed that the simple CPU runs into the lava at the sides of the map, and stays there, not allowing the player to defeat the AI themself. I’m not sure if this is intentional, but I just wanted to point it out.
They should have type: heal cooldown and speed. Will add a page of docs about items today.
What do you mean “defeat CPU”? if it’s dead then you won. However I agree need something better than suicidal CPU ![]()
I meant that the player can’t… Doesn’t get a chance to kill the AI themself, using code. The player could win without code.
Got it. Agree. The good point.
Also, I think to add some global objects with all game parameters as I change the balance from time to time and sometimes (ok, ok, often) forget to update docs about that. What the API would be better for that? some global game object or a method as hero.getGameParameter('itemSpeedRatio') ?
ability or sbility - who cares? ![]()
What’s the code that causes this error?
hero.isReady(fire):
hero.fire()
where are the quotes? .-.
Got it. Fixed that typo. Need to add a better error message. Thanks!
sugestion i am think you need to be able to know which direction the bug is going
You can implement it yourself .-.
what do you mean (20 chars)
It is hard to explain. But yes @moonwatcher348 is right
He means you can find which direction the snail is going by writing code yourself
It’s not a problem to add direction. Can do it and it doesn’t contradict with the principle of “see -read”. What’s I better direction as a string “up/down/right/left” or an angle (0 to 360) or (0 to 2Pi) ???
Is possible to clear the cache so i can actual load it up again? There is an infinite loop on my code
