Page 1 of 1

ROM NEED UPDATE

Posted: Thu Jan 19, 2023 8:41 am
by Sasuke
hi all. i think rom need to be update ....rom/update work but when you check on char with rom/addrtest it has a problems.someone or admin can help pls ?

Re: ROM NEED UPDATE

Posted: Thu Jan 19, 2023 11:28 am
by Andre235
hi, i had no time for more, but it starts simple scripts without crashes.

Re: ROM NEED UPDATE

Posted: Thu Jan 19, 2023 1:11 pm
by YetAnotherUser
bot not working anymore for me either since today's update:
Loading text cache...
Collecting and caching game texts... Please be patient.
Progress: [ ] 0%The game client did not crash.
2023-01-19 19:06:41 - .../micromacro/scripts/rom/functions.lua:2621: attempt to get length of local 'key' (a nil value)
I already tried addrupdate, but I got
Could not find pattern for {actionbar_base}
And also:
Not all updatable addresses could be found.
Do you want to continue and update found information? y/n:
-----
Edit: downloaded your file and it works!
Though I have a bunch of errors like:
Wrong value returned in update of CItem id: 1
stack traceback:
.../micromacro/scripts/rom/classes/item.lua:88: in function 'update'
.../micromacro/scripts/rom/classes/bankitem.lua:42: in function 'update'
.../micromacro/scripts/rom/classes/bankitem.lua:11: in function 'constructor'
.../micromacro/lib/mods/classes.lua:54: in function 'CBankItem'
.../micromacro/scripts/rom/classes/bank.lua:16: in function 'constructor'
.../micromacro/lib/mods/classes.lua:56: in function 'CBank'
scripts\rom/bot.lua:322: in function 'foo'
...\micromacro\lib\lib.lua:570: in function <...\micromacro\lib\lib.lua:568>

Re: ROM NEED UPDATE

Posted: Thu Jan 19, 2023 7:26 pm
by Sasuke
i will check if it works.ty for now

Re: ROM NEED UPDATE

Posted: Fri Jan 20, 2023 3:42 pm
by Administrator
Just merged address fixes for compatibility with client version 7.4.0.2980: https://github.com/SolarStrike-Software ... t/releases

You may update your scripts as you normally do. Easiest way is to just run the
rombot_updater
from your rom-bot folder.

Re: ROM NEED UPDATE

Posted: Fri Jan 20, 2023 4:17 pm
by ThulsaDoom
Thanks for updating;

One problem appears when call:

Code: Select all

player:target_NPC("Snoop the Stubborn"); yrest(2000);
ChoiceOptionByName("Transport to: Silverspring")
Rombot crash:

Code: Select all

We try to find NPC Snoop the Stubborn:
We successfully target NPC Snoop the Stubborn and try to open the dialog window.
Loading text cache...
The game client did not crash.
Character: xxxx
2023-01-20 22:15:47 - D:/Runes of magic/micromacro/scripts/rom/functions.lua:2224: bad argument #1 to 'lower' (string expected, got nil)
Before new version the function worked well.

Rgds

Re: ROM NEED UPDATE

Posted: Fri Jan 20, 2023 4:35 pm
by ThulsaDoom
There is also a problem already corrected in the past:
Some characters (not all) carry out the waypoint route by tumbling (wandering).

Thank you very much for your help.

Re: ROM NEED UPDATE

Posted: Fri Jan 20, 2023 6:09 pm
by Sasuke
Administrator wrote: Fri Jan 20, 2023 3:42 pm Just merged address fixes for compatibility with client version 7.4.0.2980: https://github.com/SolarStrike-Software ... t/releases

You may update your scripts as you normally do. Easiest way is to just run the
rombot_updater
from your rom-bot folder.
ty as always admin.really ty:)

Re: ROM NEED UPDATE

Posted: Sat Jan 21, 2023 12:37 am
by Tuedennuegel
Ich schieße mich an und sage besten Dank

Re: ROM NEED UPDATE

Posted: Sat Jan 21, 2023 9:51 am
by Administrator
ThulsaDoom wrote: Fri Jan 20, 2023 4:17 pm Thanks for updating;

One problem appears when call:

Code: Select all

player:target_NPC("Snoop the Stubborn"); yrest(2000);
ChoiceOptionByName("Transport to: Silverspring")
Rombot crash:

Code: Select all

We try to find NPC Snoop the Stubborn:
We successfully target NPC Snoop the Stubborn and try to open the dialog window.
Loading text cache...
The game client did not crash.
Character: xxxx
2023-01-20 22:15:47 - D:/Runes of magic/micromacro/scripts/rom/functions.lua:2224: bad argument #1 to 'lower' (string expected, got nil)
Before new version the function worked well.

Rgds
I'm not able to reproduce this, but it looks like the bot isn't able to read text strings from the game client. Please try deleting the
rom-bot/cache/texts.lua
.
Next time you start the bot, it should read and cache all of the text strings again; this might solve the problem for you. If not, please upload a copy of the
texts.lua
file for me to take a peek at.

ThulsaDoom wrote: Fri Jan 20, 2023 4:35 pm There is also a problem already corrected in the past:
Some characters (not all) carry out the waypoint route by tumbling (wandering).

Thank you very much for your help.
This is probably again related to an issue reading text strings. I think every time the bot tries to read some item or skill information, it tries to pull text strings from the game client and do a database lookup; if it's not easily cached, then the bot has to scan a huge chunk of memory, which is slow. It likely tried to do this over and over for every string, leaving the bot stuck almost entirely just scanning memory and not focusing on controlling your character.

Re: ROM NEED UPDATE

Posted: Sat Jan 21, 2023 11:04 am
by ThulsaDoom
You are right, the Texts.lua was not updated.
Now seems to work well.

Thanks a lot

Re: ROM NEED UPDATE

Posted: Wed Mar 08, 2023 1:06 pm
by xrozhija
I have recently returned to this game, and wanted to try out the bot again.

But whenever I try to start it, with a waypoint that requires speedhack, it gives the following error and stops.

[string "..."]:13: bad argument #2 to 'memoryReadIntPtr' (number expected, got nil)

Re: ROM NEED UPDATE

Posted: Wed Mar 08, 2023 5:36 pm
by Administrator
xrozhija wrote: Wed Mar 08, 2023 1:06 pm I have recently returned to this game, and wanted to try out the bot again.

But whenever I try to start it, with a waypoint that requires speedhack, it gives the following error and stops.

[string "..."]:13: bad argument #2 to 'memoryReadIntPtr' (number expected, got nil)
Please create a new topic for these things in the future instead of attaching it to a thread that has nothing to do with what you need. This is so other people will be able to find it if they have the same issue.

With that out of the way, can you attach the waypoint? It'll be needed to determine what is failing.