@Aftermath, you’re saying you were able to beat this level and you had never programmed before CodeCombat? If so, that’s… unexpectedly amazing!
this.say() does expect a string, so if you passed it something else, it might have complained. I want to improve this to be able to handle other things, too, or at least complain sensibly.
@Lloyd I have some incredible things in store for viewing the value of all variables in your code whenever you want, oh yes, oh yes. That will make the
this.say() debugging hack much less important. You’ll be able to hover over anything in your code to see its value, and to also scrub through time to see how its value changes, and to step backwards and forwards from one statement to the next.
@vandeput good point about guiding the player where to start. Any ideas on how best to do it? Currently I have an arrow pointing toward the
getNearestEnemy() tab, but perhaps we can add something else to make it more clear.
@F4E Interesting–I hadn’t thought about instrumenting the built-in Math functions to make sure their arguments are correct, but you’re right, that’s a common gotcha and we should protect against that. I have added it to my list.