Stuck on loading items tables

[botje]

no it didnt...

try closing rom and then try again.

also, a error occures now with opening giftbags when yout leveling from 1 to 10.

Botje

[jduartedj]

(r548) solved this problem =)
Now can go farming 5k x Unknown Gift's

BTW what exactly is the bonus you get from Unknown gifts? I've picked a load of them but i don't see what it's for other that getting 1 goody-cert a day and a good buff from the tree in varanas.

[ezgitaran]

BTW what exactly is the bonus you get from Unknown gifts? I've picked a load of them but i don't see what it's for other that getting 1 goody-cert a day and a good buff from the tree in varanas.

It's for "decorating that tree 500 times" title.. The ultimate grind >_>

And yes, it seems I spoke too early, bot is now giving this error;
classes/inventory.lua:799: bad argument #1 to 'lower' <string expected, got nil>

[jduartedj]

It's the same I posted in the r544 update announcement, read that pls.
you must add a second argument to totalitemcount and change a line in inventory:useitem for now. Later an update will be sent to SVN, I can't do that because i'm not a commiter.

[rock5]

(r548) solved this problem =)
Now can go farming 5k x Unknown Gift's

Just so there is no confusion r548 is not a fix for the 67% problem. I released r548 and I was still getting the 67% problem at the time. You must have just been lucky.

On another note, I started my computer today and was able to start the bot but I got some 'wrong value returned' errors.

Code: Select all

Loading items tables.
100% [**************************************************]

Wrong value returned in update of item id: 200272
Wrong value returned in update of item id: 206893
Wrong value returned in update of item id: 202916
Wrong value returned in update of item id: 200424
Waypoint files from C:/Program Files/micromacro/scripts/brom:
  0: wander                 10: 1-10Pi../l4t_logar.xm  20: demo1.xml

BTW I don't have any of these values in my inventory.

Edit: After restarting the game it got stuck at 67% again. Grrr... Maybe it's a anti-botting security feature?

[botje]

if thats so, they didnt do their best, if you disable inventory features, you can still bot xd

Botje

[raff]

I have no problems, when I start the bot on windows xp 32bit with vmware, I have just restarted rom 3 times, and everytime I was able to start the bot.

I am using Windows 7 Home 64bit and with that I get stuck at 67%. I have also tried to start rom/micromacro with different compatibilty modes, but without success. Also deactivating anti virus didn't help.

I have enabled

Code: Select all

debugTableIndexes
debugTableRanges

in memorytable.lua

and it's spamming:

Code: Select all

Received: 11D60000      Returning: 11D60020
Readed from 11D60000     at 0x4 11D60020        Original pointer: 11D60000
Returning: 11D60020

when it reached 67%, dunno if this can help you

Code: Select all

Received: 11D18D80      Returning: 0
Name: QuestNPCObjectDB
067% [*********************************-----------------]Table starts with id: 1
10000            Dir: 11D18D20
Adding range. Start: 110000     End: 111129     Address: 11D18D20       Table#:
18
Readed from 11D10000     at 0x4 11D10040        Original pointer: 11D10000
4Readed at 11D10000      in 0x8 11D6FFE0        ID: 111130
Returning: 11D6FFE0
Received: 11D10000      Returning: 11D6FFE0
Adding range. Start: 111130     End: 113176     Address: 11D6FFE0       Table#:
18
Readed from 11D60000     at 0x4 11D60020        Original pointer: 11D60000
Returning: 11D60020
Received: 11D60000      Returning: 11D60020
Readed from 11D60000     at 0x4 11D60020        Original pointer: 11D60000
Returning: 11D60020
Received: 11D60000      Returning: 11D60020
Readed from 11D60000     at 0x4 11D60020        Original pointer: 11D60000
Returning: 11D60020
Received: 11D60000      Returning: 11D60020
Readed from 11D60000     at 0x4 11D60020        Original pointer: 11D60000
Returning: 11D60020
Received: 11D60000      Returning: 11D60020
Readed from 11D60000     at 0x4 11D60020        Original pointer: 11D60000
Returning: 11D60020
Received: 11D60000      Returning: 11D60020
Readed from 11D60000     at 0x4 11D60020        Original pointer: 11D60000
Returning: 11D60020

[botje]

seems to me its windows 7 related then, because i have also windows 7, but mine is 32bit

weird O.o

Botje

[rock5]

seems to me its windows 7 related then, because i have also windows 7, but mine is 32bit

Maybe it is. Mine is a Win7 system too.

I have no problems, when I start the bot on windows xp 32bit with vmware, I have just restarted rom 3 times, and everytime I was able to start the bot.

Could you elaborate a bit on how you used vmware to do this? I might look into it.

[botje]

perhaps its rights related?

maybe bot tries to write something it doesnt allows it?

Botje

[raff]

Could you elaborate a bit on how you used vmware to do this? I might look into it.

I am using VMware Workstation 7.0.0.

Install Windows XP with it, copy the rom and bot folders over there or make a shared folder (I had problems with starting rom through shared folders) and start it with the usual way, it's just a virtual windows xp.

I have uploaded a video, where you can see it in action:
http://u0d.de/bf740e/untitled_12.rar

[rock5]

Could you elaborate a bit on how you used vmware to do this? I might look into it.

I am using VMware Workstation 7.0.0.

Install Windows XP with it, copy the rom and bot folders over there or make a shared folder (I had problems with starting rom through shared folders) and start it with the usual way, it's just a virtual windows xp.

I have uploaded a video, where you can see it in action:
http://u0d.de/bf740e/untitled_12.rar

Actually I'm surprised you could run rom inside a virtual machine. How powerful is your machine if you don't mind me asking.

[botje]

yeah, vmware does have a bit of a overhead on its own xd

Botje

[Sumdumguy]

I get the 67% error on 64 bit windows 7 professional,

Loaded it up on my work-laptop, Win 7 ultimate 32 bit, runs fine, several accounts, several characters. Maybe that helps.

[jduartedj]

for the record I got Win7 x64 Ultimate, and got no problems.

[Uglich]

I got the same problem allways at 67 %.
Windows 7 64bit Ultimate.

But, editting addres.lua it fixed.

If the latest revision (r547) didn't help, try editing your addresses.lua. Change inventoryBagIds to 0x9CD908 and see if that helps at all.

[jduartedj]

I got the same problem allways at 67 %.
Windows 7 64bit Ultimate.

But, editting addres.lua it fixed.

If the latest revision (r547) didn't help, try editing your addresses.lua. Change inventoryBagIds to 0x9CD908 and see if that helps at all.

I posted that to ADMIN, but it was ruled out as having nothing to do with the stuck problem! and also with the later updates I figure that that address wasn't correct anyway because it excludes the AT and itemshop bag that are now in use.

EDIT: Maybe an update could be pushed to optionally disable AT and itemshop bags, including adding adifferent address variable for them to see if isolating these from the normal bags helps the stuck problem, given that it helped Uglich.

[rock5]

Loaded it up on my work-laptop, Win 7 ultimate 32 bit, runs fine, several accounts, several characters. Maybe that helps.

Not really, I also have Win 7 Ultimate 32 bit and get the error.

So far it looks like the only thing we can say for sure is that it is Windows 7 related as everyone who has the error has reported a version of win 7 or another.

Just to make sure, is there anyone out there that gets this error on a Windows XP system?

[atroxa]

Hey,
just wanted to comment:

1. Win 7 Buisness 64bit
2. Rom installed @ Chapter 3 (full client!), manually patched
3. Svn Updated, newest micromacro

Don't suffer at any point

running like 7 clients at once without any problems.

So far....

Good luck

[ratzuk]

I think it might be how the game is loaded into the memory of the machine depending on the available RAM rather than an OS issue

Example: My machines

Desktop - Core 2 Quad Q6850 8GB Win 7 x64 - Stuck 67% most of the time
Laptop - Core 2 Duo T9550 4GB Win 7 x64 - Never stuck on loading items tables

Perhaps we need to compare the specs of the machines where the 67% issue occurs to see if there is something in common?