SolarStrike Software

When trying to use certain waypoint files I get error messages after the program turns a quest in. At this point rombot crashes and gives me an error mesage. I'm using micromacro beta at the moment, but the same thing has happened with the stable version. To the best of my knowledge I have all userfunctions updated and installed. They work fine for minigame waypoint files.
The files I'm trying to run are:
4ustart.xml posted by lisa on the rom4u private server thread
20elfs0.45.xml posted by langelot133 here

I'm not sure how standard my version of rombot is. When I download a clean copy, use svn.update.bat (with svntortise installed) and try to run rombot I get this error. (pic posted in attachments) I've tried copying new copies of ingamefunctions to the addons folder each time with no sucess. To get it working I had to right click the rombot folder, select Revert, and select all files. I'm not sure what it reverted to since this is a new download/copy, but it works after I do this.

My friend sent me his working copy of the micromacro folder/rombot and I get this error message instead when trying to run the waypoint files listed above.
Oh and just to be clear I've been using rombot for my minigames this past week and it works wonderfully. No issues at all until I try to use these waypoints. I've tried redownloading and installing micromacro, rombot, and userfunctions a few times each and its done me no good.

MrFox wrote:I'm not sure how standard my version of rombot is. When I download a clean copy, use svn.update.bat (with svntortise installed)

I'm not sure I understand this. svn.update.bat is part of the bot. So you would already have had to download the bot to get it. Are you saying you copy svn.update.bat and svnupdate.lua from another location into the new folder and then run it? Where did you get it from? It would still have to do the svn checkout. Do you get a message saying "TortoiseSVN has not been configured for this path yet" and the 'Checkout' pop up dialog?

Normally, I would just right click the new folder and select 'SVN Checkout' and then select the url from the drop down. As simple as that.

MrFox wrote:I've tried copying new copies of ingamefunctions to the addons folder each time with no sucess. To get it working I had to right click the rombot folder, select Revert, and select all files. I'm not sure what it reverted to since this is a new download/copy, but it works after I do this.

If it's saying that it thinks it's current version of igf is 6 then it's probably an old version. When you revert it reverts to the version that it thinks it is. For revert to change something there would have had to be red and/or yellow icons next to some of the files. After the revert it should all be green. The only way I know of to know what version the bot thinks it's up to is to select "TortoiseSVN/Show Log" and see which entry at the top is highlighted.

As to the problems with the waypoint files, which file does it crash on and at which point in the file? But the problem seems to be with the QuestLog userfunction. Make sure it's up to date or. As far as I know the Questlog userfunction still works but, if you are not using it, you could also delete it.

Thank you for the quick reply. Thanks to you I realized I was making some severe instillation mistakes. I have that working now and everything has the green checkmark.

Unfortunately the errors haven't stopped. The script seems to crash right after turning a quest in. I posted a screenshot below, it crashed right after turning in the very first elf quest. If I start it up again, it goes as normal and runs to the next npc with a quest, but only crashes once more after turning in. The odd thing is it doesn't crash every single time after turning in a quest. If I had to guess I'd say it crashes 75% of the time however.

The error code with a correct copy of the rom bot folder is (or just look at the screenshot) The waypoint file I was testing with is lisa's which I link in my first post. I've redownloaded and installed the Questlog userfunction that you have posted as well.

Try changing line 1995 of functions.lua to

Oh wow, you're amazing rock. It works perfectly now! Thank you so much, I was pulling my hair out trying to get this to work.

It never ceases to amaze me how a single part of a single line of code can make such a difference, and how you can diagnose the problem so quickly as well.

Thank you again, this will make my life muuuch easier.