SolarStrike Software

I've been getting some errors at totally different times and have been saving the logs, now to try and get some answers I'll post them so that they might be relevant:

1.I've been getting (probably) random memory errors like such:
...te/Desktop/micromacro/scripts/rom/classes/player.lua:2079: bad argument #1 to
'memoryReadIntPtr' ((null))


2. What about this error? was it ever fixed? (I commented this line out)
While updating addresses something like: Pawn_PetPtr error

3. And lastly updating bag error:(im gonna activate Debug vars so i get more info)
BAG:
Wrong value returned in update of item id: 520023
Wrong value returned in update of item id: 201060
Wrong value returned in update of item id: 222174
Wrong value returned in update of item id: 520103
Wrong value returned in update of item id: 520203
Wrong value returned in update of item id: 520123
Wrong value returned in update of item id: 221096
Wrong value returned in update of item id: 207200
Wrong value returned in update of item id: 200192
Wrong value returned in update of item id: 207210
Wrong value returned in update of item id: 207209
Wrong value returned in update of item id: 203238
Wrong value returned in update of item id: 203495
Wrong value returned in update of item id: 203014
Wrong value returned in update of item id: 203012
Wrong value returned in update of item id: 203009
Wrong value returned in update of item id: 202987
Wrong value returned in update of item id: 202986
Wrong value returned in update of item id: 203011
Wrong value returned in update of item id: 203011
Wrong value returned in update of item id: 202989
Wrong value returned in update of item id: 202988
Wrong value returned in update of item id: 203008
Wrong value returned in update of item id: 203008
Wrong value returned in update of item id: 204482
Wrong value returned in update of item id: 204489
Wrong value returned in update of item id: 204493
Wrong value returned in update of item id: 203010
Wrong value returned in update of item id: 203010
Wrong value returned in update of item id: 204491
Wrong value returned in update of item id: 204479
Wrong value returned in update of item id: 204485
Wrong value returned in update of item id: 204485
Wrong value returned in update of item id: 203010

yeah, that pwnpet thingy is still there :/

rest i have on occasion, just restart bot and its gone though.

Botje

botje wrote:yeah, that pwnpet thingy is still there :/

rest i have on occasion, just restart bot and its gone though.

Botje

In my case i'm pretty sure every time I runned the script it got stuck there.... Until I move on to using pets in my bots I think i'm good -- but at least the Devs are aware of it!

As far as I know the pet offset is still correct. You get that error only because the pattern and/or mask for it in update.lua is wrong.

By the way I'm pretty sure all the addresses in the last revision are correct so it is best not to run update.lua because not all the patterns and masks in it have been updated. So if you comment out the pawnPet offset and run update.lua you will likely screw up the addresses.

For future reference, when there is a minor update and bot.lua tells you to run update.lua, do so. When there is a major update and update.lua doesn't work then wait till someone updates it manually and don't run update.lua.

Yes, I know the bot is saying to run update.lua but that is because the patterns haven't been updated yet since the large patch so ignore it for now.

So, jduartedj, try doing a "Tortoise/Revert" on the addresses.lua file and see if it works.

rock5 wrote:As far as I know the pet offset is still correct. You get that error only because the pattern and/or mask for it in update.lua is wrong.

By the way I'm pretty sure all the addresses in the last revision are correct so it is best not to run update.lua because not all the patterns and masks in it have been updated. So if you comment out the pawnPet offset and run update.lua you will likely screw up the addresses.

For future reference, when there is a minor update and bot.lua tells you to run update.lua, do so. When there is a major update and update.lua doesn't work then wait till someone updates it manually and don't run update.lua.

Yes, I know the bot is saying to run update.lua but that is because the patterns haven't been updated yet since the large patch so ignore it for now.

So, jduartedj, try doing a "Tortoise/Revert" on the addresses.lua file and see if it works.

But to What revision should I revert to? it is the one b4 the current revision of
addresses file?

I mean if you ran update.lua and it changed the addresses.lua file and you are getting errors then revert to the current revision, to undo the changes.