Getting this error when doing essentially anything, after exiting Eros Gym after updating to 597c (save is from 596a originally, I think)
RPGM Pokémon 'H' Version [v0.625 B] [Sintax Error]
- Thread starter SINtax EroRR
- Start date
Getting this error when doing essentially anything, after exiting Eros Gym after updating to 597c (save is from 596a originally, I think)
Thats the error message you get when you didnt follow instructions and didnt delete your save files and start a new game when updating from a version before 0.524.
So yeah, delete your saves and start a new game.
seems fun, except the inability to heal your pokemon in the beginning using the pc is annoying. and every 5 mins i get a syntax error now and it crashes.
- Mar 10, 2019
- 143
- 178
what do you mean by "inability to heal your pokemon in the beginning using the pc"
i never had an issue healing my Pokemon, ever
what's your question
- Mar 10, 2019
- 143
- 178
it sounds like you're already getting a solution, but for anyone else who has this issue and can't load a previous save, here's an easy fix: open up the game's folder to \Graphics\Pictures and rename Viruark_AnalProbe_02.png to something else, then go do another event that displays a special cg, then rename the file back to the original name.
basically, the game is trying to display Viruark_AnalProbe_02.png over top of everything but dialog boxes, so by renaming it you make the game unable to find that image. this results in the game playing normally, so you can go about your business, except that Viruark2 will be missing a cg in the event viewer. but if you save it like that and rename the image to its original name, the game is still trying to display it, so you'll get your screen blocked again. if you do another event that displays a cg, though, then the game will replace the Viruark one with the one appropriate for the new event, and it'll stop displaying when the event ends as normal. if you save and revert Viruark_AnalProbe_02.png to its original name after that, then you'll be able to play the game normally and still be able to view Viruark2 in the event viewer.
edit: it seems that some events won't fix it, at least Sonia's has been reported to not do so. the event that i tried was the repeatable Viruark event at the bed in your house in Eclipse City, so it's possible that only other Viruark events will work, or maybe even only that event specifically will work. either way, leaving the image renamed will still allow the game to be played normally, and the bug is scheduled to be fixed with the next update anyway.
Last edited:
I need a handholding guide for ranger quest #4. I can't get all the clues in the guy's house. There is no one to interact with in his house.
Talk to your pokemon. See how they react to you. Viruarks event only starts after she runs off.
i caught a houndour to be able to put my starter in the pc to heal it and restore its PP but it did neither when i put it in
- Aug 16, 2020
- 305
- 259
is there a way to still get the fly tm? im at the door of the 4 gym and dindt knew asha should give you the fly tm by gym 2. I only got the dragon harness but its not useable becuase i cant find the flying mon
No. Currently, you can only fly using Drakaiden + Dragon Harness. Note, Currently.
- Aug 16, 2020
- 305
- 259
Tried that, but it didn't work for me (used the Sonia fingering scene, if that matters). Viruark2 scene appears over the top again whenever I rename it back and load the game back up.
Is there a guide to show how to get all events with the good ending cause its really hard doing retries over and over again to find the right combo especially for the first tsarenviya event
hi! i need some help .. i've finished the 2nd gym but i haven't been able to find seras in the beachside cafe .. i've roamed around the map and she's still standing outside the ship .. i've tried choosing all of her dialogues but she's still there .. what should i do?
- Aug 16, 2020
- 305
- 259
Game works fine with that pic renamed so it doesn't show. It's only 1 pic, so it doesn't matter that it's missing. Next update was fixing it anyway, wasn't it?