I believe your line 26 is now
Code: Select all
tmp = memoryReadRepeat("uint", proc, self.Address + addresses.pawnId_offset) or 0;
Code: Select all
tmp = memoryReadUInt(proc, self.Address + addresses.pawnId_offset) or 0;
Code: Select all
tmp = memoryReadRepeat("uint", proc, self.Address + addresses.pawnId_offset) or 0;
Code: Select all
tmp = memoryReadUInt(proc, self.Address + addresses.pawnId_offset) or 0;
Code: Select all
Did not find any crashed game clients.
0:45am - X:/Programs/micromacro/scripts/rom/classes/pawn.lua:241: Error in memory reading
Code: Select all
tmp = memoryReadUInt(proc, self.Address + addresses.pawnId_offset) or 0;
Code: Select all
tmp = memoryReadRepeat("byteptr",proc, self.Address + addresses.pawnSwim_offset1, addresses.pawnSwim_offset2)
self.Swimming = (tmp == 3 or tmp == 4)
Code: Select all
-- Swimming wont change if it can't be read.
local swimoffset1 = memoryReadRepeat("int",getProc(), self.Address + addresses.pawnSwim_offset1)
if swimoffset1 ~= nil and swimoffset1 ~= 0 then
tmp = memoryReadRepeat("byte",getProc(), swimoffset1 + addresses.pawnSwim_offset2)
self.Swimming = (tmp == 3 or tmp == 4)
end
Code: Select all
10:2am - X:/Programs/micromacro/scripts/rom/classes/pawn.lua:372: Error in memory reading
Code: Select all
Moving in | Suggested range: 50 | Distance: 115
No more usable HP Phirius potsMACRO: Using HP potion 259/764 (33%): Prosta Mikstura Pierws
zej Pomocy (qty 86)
I was hoping we wouldn't get this error anymore. I guess it doesn't hurt to leave those changes in.cufRet8e wrote:Crashes again and again, average time 5 minutes, always same error.
This is the line.cufRet8e wrote:No more usable HP Phirius potsMACRO: Using HP potion 259/764 (33%): Prosta Mikstura Pierws
zej Pomocy (qty 86)
Code: Select all
cprintf(cli.yellow, "No more usable HP Phirius pots", inventory.MaxSlots);
Code: Select all
cprintf(cli.yellow, language[19], inventory.MaxSlots); -- No more (usable) mana potions
Code: Select all
[19] = "No more (usable) Phirius MP potions available at bagslot 1 to %d\n",
Code: Select all
Did not find any crashed game clients.
1:43pm - X:/Programs/micromacro/scripts/rom/classes/pawn.lua:626: Error in memory reading
Code: Select all
local tmpTargetPtr = memoryReadRepeat("int", getProc(), self.Address + addresses.pawnTargetPtr_offset) or 0
So how it should be then?rock5 wrote:By the way this is wrong "No more (usable) Phirius MP potions available at bagslot 1 to %d\n". I check "bestavailablephirius". It doesn't use "maxslot". It searches all slots.
No, I am not, but Google Translate does:) I was thinking only about this particular message. But yeah, I look into language files, and really, some messages are missing. But this is a problem for those, who speak that languages. My native language is polish, but I am very happy using english version of rombot.rock5 wrote:Wow do you speak 6 languages? If so there are probably lots of messages that still need translating
Code: Select all
1:43pm - X:/Programs/micromacro/scripts/rom/classes/pawn.lua:626: Error in memory reading
Code: Select all
2:28pm - ...:/Programs/micromacro/scripts/rom/classes/player.lua:260: Error in memory reading
We can't go around changing all the memoryreadrepeats. I wonder in there is a basic flaw in memoryreadrepeat erroring when it fails. Maybe it should return nil. I'm not sure.cufRet8e wrote:Same problem, isn't? I guess this can be changed to use of memoryReadUInt();?
The way the bot works is it loads the English file first which should have all the messages then loads the local language file which overwrites the English messages. If there are any missing messages then it still has the English version. If you want to do some Polish translation just add the messages missing by looking at the English one and translating it.cufRet8e wrote:I look into language files, and really, some messages are missing.
That might explain why not everyone is having the same issue.rock5 wrote:Bugger, I just had another look at memoryreadrepeat and it only errors if "settings.options.DEBUGGING" is true. Do you have debugging enabled?
Kill me, but yes -_-'rock5 wrote: Bugger, I just had another look at memoryreadrepeat and it only errors if "settings.options.DEBUGGING" is true. Do you have debugging enabled?
Yeah, looks pretty clear now. That's was the reason.lisa wrote:That might explain why not everyone is having the same issue.
That does prove though that the memoryreadrepeat does fail, question is why would it fail?
I'd say it's mostly when things don't exist anymore or it could be anything really. It may be related to certain values, such as the swim value. Important thing is if it works ok with debugging off. I think the reason it might have been set up to error when debugging is on, is to help catch the errors. If you enable debugging to look for errors, you don't want to miss them as they scroll off the top of the screen.lisa wrote:That does prove though that the memoryreadrepeat does fail, question is why would it fail?
Problem is I mainly just do cot and survival. I wouldn't want it to crash in the middle of those. I'll see what I can do tomorrow.cufRet8e wrote:Can you enable it and see what happens to your rombot? This may be source of all those crashes.
Users browsing this forum: No registered users and 0 guests