Okay, so I let the rat only make its noise when sitting on the mark. Now the second noise distracts both skeletons, but still one turns around to kill me.
Maybe your hero is tooo slow, maybe something else. I need more information to understand whatâs wrong with your code. Could you say your nickname in the game and I will check it?
Oh, I see the problem.You are using the minimum possible hero speed. So when you are trying to pass two skeletons the second time try to add a point and move along right walls (closer to skeletons). If you are trying to move right to the exit you donât have enough speed to sneak because the hero move by straight line. Be sneaky, move along walls, be ninja Or use a faster hero (or a Speed Ring at least)
You mean the slowest available hero? Or is it possible to make a hero faster?
It works with Hattori, without making any changes to the rest of the code.
Last question, which I already asked, but was ignored:
e.g. 72, 28 instead of 64, 28. Why does it have to sit on the spot marked with X?
This, and the thing with heroâs speed: I feel this should really either
a) not make a difference for the outcome of the level or
b) be mentioned at least in the hints section, or in the comments.
This kind of obstacles is simply not instructional: I fail to see how it helps me learn to code, plus itâs annoying.
It makes a difference because the mouses squeak has a range. Iâm not sure exactly what it is but you canât hear it from wherever. Just like in real life, or with the other abilities in the game like warcry.
I donât really see your problem here, canât you just make the mouse move a little closer?
I already solved the problem: mouse needs to sit on the spot marked X (while slightly more distant will also work, but not too distant).
But wouldnât it be awesome to know the exact range of that squeak (how did you find out about it, btw)? Wouldnât it be great if that information was present in the level description in the first place, instead having to play frustrating guessing games? Yet another unnecessary secret obstacle.
I would say itâs a lot easier to just put the mouse on the x both times, as, I think, you are expected to do. Thereâs no guessing involved, it was (to me at least) quite obvious that you had to put the rat on the x. Now I see you donât have to, but it makes things simpler. After your comment I experimented to see how far away the rat could go before it didnât work.
I think youâre right that it might be a good idea to add some documentation about this, but I wouldnât call it a problem.