RoM 2.1.1.1909.en pawn.lua:183: bad argument #1

[TomBowyer]

Hi,
I have just updated to RoM version 2.1.1.1909.en (after todays patch and server maintenance).

The bot was working perfectly last night however now im getting the error:
/MicroMacro/scripts/rom/classes/pawn.lua:183: bad argument #1 to 'bitAnd' ((null))

Ive re-downloaded from SVN, could anyone advise on this problem, does RoM bot need an update or am I doing something wrong?

Regards,
Tom.

[Steinmeier]

Same here.
Before and After SVN-Update

[j_schlott]

im getting the same error, more than likely the game changed somewhat and will need a bot update

Code: Select all

	if( self.Type == PT_MONSTER ) then
		self.Attackable = true;
	else
		if( bitAnd(attackableFlag, ATTACKABLE_MASK_PLAYER) ) then <<<<<<<<---------------
			self.Attackable = true;
		else
			self.Attackable = false;
		end
	end

thats the line in the code thats giving error

[jupister]

likewise, seems like the bot is down..

[FelixTheCatetris]

Ditto. Omg love botting, please update asap. Your program/code saves me the lame-o mmo grind time. Thanks!

[Uniden65]

i agree but its ROM bot version 3.0.

and there very good here so just give them some time .......

[droppen]

hmm, there is some major changes in the game. i cannot fix it with my skill's. we'll have to wait

[Administrator]

I've made an update to SVN that contains new addresses and flags that will fix this problem. It needs to be tested a bit more (as checking every offset manually takes a very long time) but it looks like a majority of the problems should be resolved.

[ToreDeLoro]

i run 'rom/bot.lua update' but i still have this error

thanks

[d003232]

i run 'rom/bot.lua update' but i still have this error

thanks

Read here for a workaround.

[FelixTheCatetris]

I get this error as well, but only after the bot has been running for a little bit, and only if I am running two bots on one pc. If i solo bot it doesn't appear to happen.

[Uniden65]

the Offset must still be off ? about 20 - 30 min into running the bot it does this



hope this helps, i blanked everything else to cover up who iam on line this just shows the error for reference.

Reseting the client will fix it but it happens again and again ...

SVN Version 336 Maybe working correctly Now alot of offsets where changed, if this changes ill come back and report.

[d003232]

SVN Version 336 Maybe working correctly Now alot of offsets where changed, if this changes ill come back and report.

No it is not corrected. You can use the workaround until it is fixed finaly.