4.0.0 any issues/solutions (CHAPTER IV)

[Chemico]

Interesting. Yours works like a charm, but my folder updated and files replaced with your provided ones following your instructions did not. There is also no problem with the old profiles, they work. Thank you very much!

[brujilla]

JO JO Jo THANKS Rock5 ahora SIIIIIIIIIIIIII GRACIASSSSSSSSSSSSSSSSSSSSSS

[degoulina]

rock5 you rock!!

thank you

[cheater]

i downloaded rocks micromacro
i dont need to put profile:name behind the bot.lua

but now it stops @

Code: Select all

RoM windows size is 1280x720, upperleft corner at 8,30
Loading profile profile.xml

nothing happens after that.. :-/

[rock5]

Maybe it was a micromacro version problem. What versions of micromacro were you guys using?

[cheater]

1.01 Beta

[lisa]

the macro is still being set to the wrong place if it's a new character. hotbar has issues with the new code.

[emmanuel04]

now i cant add this

-- after 1x unsuccesfull unsticks try to reach nearest waypoint
if( self.Unstick_counter == 2 ) then
__WPL:setWaypointIndex(__WPL:getNearestWaypoint(player.X, player.Z, player.Y));
end;

[brujilla]

OH NO NO NO! This messae scripts/rom/item.lua:211 attempt to perform arithmetic on global `itemInfoAddress` <a nil value>

[Reymauro]

Rock & Lisa Thank you very much, I got to say that your patience is amazing.

Great work !!

[cheater]

he doesn't use "0" for macrokey.. he used 8, now tries 7.. but he still is endless at

Code: Select all

Loading profile ....

even if i put an empty macro to every slot it says:

Code: Select all

Loading profile ....

[rock5]

1.01 Beta

I'm using beta 2 but I believe the latest is beta 4. It could be that the original beta is a bit dated. I wouldn't be using anything older than 1.01 beta 2 but it could also be the other files in the micromacro folder that are newer. Unfortunately updating the micromacro folder using TortiseSVN doesn't update the micromacro executable. That needs to be manually downloded and updated.

[cheater]

1.01 Beta

I'm using beta 2 but I believe the latest is beta 4. It could be that the original beta is a bit dated. I wouldn't be using anything older than 1.01 beta 2 but it could also be the other files in the micromacro folder that are newer. Unfortunately updating the micromacro folder using TortiseSVN doesn't update the micromacro executable. That needs to be manually downloded and updated.

updated micromacro now.
Stillt stop at

Code: Select all

Loading profile ....

#
and ingame i can see that he put key "7"... but even if the macro is on key "7" the bot doesn't continue...

[rock5]

the macro is still being set to the wrong place if it's a new character. hotbar has issues with the new code.

I'm not having any problem at all. I just created a new character, started the bot and it placed the macro in '0'. Started the Pioneers 'l1t_start' waypoint file and had no problems.

[brujilla]

OOOOHH no NO NO! this error micromacro/scripts/rom/classes/item.lua:211: attempt to performarthmetic on global <a nil value> ¿why?

[cheater]

works now, ty so far!

[DrunkTiger]

also got an error while botting. ItemInfoAddress a nil value. I turned off auto-loot just to see if that solves the problem since I won't pick up items the bot would not know about.

[irenepappel]

How does the updated MicroMacro relate to the non-working RomBot with Chapter 4?
After having patched to RoM Chapter 4 I updated the RoMBot to Build 606.
--> Bot did not work anymore
Then I read here that one should also update the main MicroMacro to the latest version.
I have then overwritten my existing MicroMacro folder with the latest version.
Now everything is up-to-date.
Nevertheless I still get the following error in the shell:

Code: Select all

Resumed.
OPENING LOCAL SKILLS DB!
!! Notice: !!
The game may have been updated or altered.
 It is recommended that you run rom/update.lua
5:25pm - Error while reading memory address for 'playerAddress'. Game seems to b
e changed!!! Please run 'rom/bot.lua update' AND install the new RoM Bot version
!
Please enter the script name to run.
Type in 'exit' (without quotes) to exit.
Script>

[lisa]

also got an error while botting. ItemInfoAddress a nil value. I turned off auto-loot just to see if that solves the problem since I won't pick up items the bot would not know about.

this is a known problem for some people and there has already been posts for it, actually I've posted several times now with the temp solution.

Well here it is again..

rom/classes/item.lua

line 201

Code: Select all

		if ( self.Id >= 770000 and self.Id <= 771000 ) then
			-- We need to get info from NPC...
			tmp = memoryReadInt( proc, self.BaseItemAddress + addresses.idCardNPCOffset );
			npcInfoAddress = GetItemAddress( tmp );
			nameAddress = memoryReadInt( proc, npcInfoAddress + addresses.nameOffset );
			self.Name = "Card - "; -- We should add a string so we can localize this
		elseif ( self.Id >= 550000 and self.Id <=552000 ) then
			-- We need to get info from item...
			tmp = memoryReadInt( proc, self.BaseItemAddress + addresses.idRecipeItemOffset );
			itemInfoAddress = GetItemAddress( tmp );
			nameAddress = memoryReadInt( proc, itemInfoAddress + addresses.nameOffset );
			self.Name = "Recipe - "; -- We should add a string so we can localize this
		else

change to

Code: Select all

		if ( self.Id >= 770000 and self.Id <= 771000 ) then
			-- We need to get info from NPC...
			--tmp = memoryReadInt( proc, self.BaseItemAddress + addresses.idCardNPCOffset );
			--npcInfoAddress = GetItemAddress( tmp );
			--nameAddress = memoryReadInt( proc, npcInfoAddress + addresses.nameOffset );
			--self.Name = "Card - "; -- We should add a string so we can localize this
		elseif ( self.Id >= 550000 and self.Id <=552000 ) then
			-- We need to get info from item...
			--tmp = memoryReadInt( proc, self.BaseItemAddress + addresses.idRecipeItemOffset );
			--itemInfoAddress = GetItemAddress( tmp );
			--nameAddress = memoryReadInt( proc, itemInfoAddress + addresses.nameOffset );
			--self.Name = "Recipe - "; -- We should add a string so we can localize this
		else

[DrunkTiger]

Really sorry! I was sure I read it all.