I did my coding in pycharm, and each test case gave the correct answer. When I pasted it into the site, it gave a wrong answer to three test cases. No errors. Iām stumped.
Okay, I goofed. I managed to include all the maps into each grid N times, instead of a separate map in each grid N times. I love how something so simple can throw it all off. Asking me to check the row and column inputs got me looking at it. Thank you.
The instructions do not explain what to do with an empty square ("."). A reasonable interpretation is that the player can move in any direction from an empty square, whereas they can only move in one direction from a square containing an arrow. This makes the problem more interesting, requiring a flooding algorithm. I solved it this way and was disappointed to find that an empty square is treated exactly like a wall. At a minimum, please make the instructions more clear.
Hi, the idea is that you start on a square with an arrow and you must follow the arrows to arrive save/alive to the treasure. The empty squares may be filled with nasty surprises.
If the path of the arrows (><^v) doesnāt lead you to a treasure cell, mark with āTā the path is invalid which means that this map will lead you to a āTRAPā.
Interesting parsing problem, I thought I had it figured out then I kept go around and around till I timed out - and then I ended up over-running the edge of the boundary Thanks for making this!
Hey, Iām having trouble near the end. My code works on all test cases except for the hidden ā2 mapsā one. Since I canāt see the failure, Iām having trouble figuring out how to fix it. Is there something different about this example specifically, or is my code just messing up in a weird spot?