If you don’t know what you are doing, and you give it a vague request hoping it will automatically solve your problem, then you will just have to spend even more time to debug its given code.
However, if you know exactly what needs do do, and give it a good prompt, then it will reward you with a very well written code, clean implementation and comments. Consider it an intern or junior developer.
Example of bad prompt: My code won’t work [paste the code], I keep having this error [paste the error log], please help me
Example of (reasonably) good prompt: This code introduces deep recursion and can sometimes cause a “maximum stack size exceeded” error in certain cases. Please help me convert it to use a while loop instead.
Second this. If I remember correctly, at some points in VLR, you have to enter some certain passwords to deactivate some certain things or something terrible will happen. But if you play this game on 3DS which has an additional touch screen, you can utilize integrated notepad feature of the game to write down what you need to remember ;-) It is crucial to play these kind of games knowing as little as possible, so I won’t disclose any more details.