SolarStrike Software

This seems to work for me:
Change bot.lua ~207:
if( player:haveTarget() ) then
To:
if((player:haveTarget()) or (player.Battling)) then
while (not player:haveTarget()) do
player:update(); -- wait till the player has a target, or exits combat
yrest(100);
end;
It stucks if someone else attacks ...

Wouldn't be better?
bot.lua ~212:
if( player:haveTarget() ) then
Change it to:
if( player:haveTarget() or (player.Battling) ) then
while( player.inBattle and (not player:haveTarget()) ) do
player:update(); -- wait till the player has a target, or exits combat
yrest(10);
end


Update: It ...

Can you share your code?

Administrator wrote:Here's an experimental change to help prevent you from getting gang raped...Need some people to test it out for me.

I tried it. It works good for me, but if I use this, then it doesn't use the target selector (TAB) bind, so only attacks after an aggro mob attacks me (getting in battle).

He uses LootFilter, and if there's something you don't loot, the corpse will stay there in focus till the bot selects the next target. In this case the selection (circle thingy under the mob) stays on the dead corpse, but the bot attacks the new target.
In other words an escape key after looting ...

I think inBattle_offset is not the good one. When you attack something, this offset doesn't changes at all. I don't know exactly what for this offset, but you can check "0x55E".
It changes only when you are in battle (Enter Combat), if you attack, or you have been attacked by an aggro mob, and turns ...

Is it enough to add this line to database.xml, to use the Priest Angel's Carol skill?
<skill name="PRIEST_ANGELS_CAROL" cooldown="180" type="buff" target="self" />
And of course the in profile:
<skill name="PRIEST_ANGELS_CAROL" hotkey="VK_MINUS" modifier="" />

After I tested it, I can answer it ...

viperfx: Do you have a "10" key on your keyboard? I think you have 0-9 but not "10". As you can see, the error describes everything you have to know to fix your problem "profile error: VK_10 does not name a valid hotkey!".

You didn't disturbed at all. I just told you that it's not 2 minutes to change the bot for multiple game, and I don't know anyone who would work out the code for you.

holystrikers : If you really want to use this bot with multiple account, and party game, you have to change several things, and for that you have to know some programming. I think noone will do this for you, except if someone already made it, and shares the code with you, but I doubt that. I would ...

Zilvermoon: Are you confirming that you have that problem where the player address changes to 0?
I have never seen it, myself. It would be nice to know what causes the game to change addresses like that...
My ISP is very lossy. When I run the bot, and a loss packed appears, the game resets the ...

Addresses for v1829: Probably wrong:

• pawnAttackable_offset
  inBattle_offset

Probably right:

• castbar_offset
  camUVec1_offset
  camUVec2_offset

Other offsets are the same as the last release of the bot.

I think this topic is totally useless. You could use the main rombot thread.
Btw there's a new patch released (1829).

Yes. As I mentioned the question marked rows are wrong, these addresses left from the previous release. I didn't find those offsets, so what uses those, that won't work. I tried with createpath.lua, but that fails too, because it uses "charDirVectorPtr_offset" wich is marked, so it fails.

New addresses.lua (for v2.0.4.1828):

staticcharbase_address = 0x8697A4; --0x8697E0; 0x883F00; 0x8A2E48;
charPtr_offset = 0x56C;
castbar_offset = 0x238; -- ?

charX_offset = 0x2C;
charY_offset = 0x30;
charZ_offset = 0x34;
charDirection_offset = 0x38;
charHP_offset = 0x344;
charMaxHP_offset = 0x34C ...

Yeah.
The new patch (1828) always crashes my game, and I can't find the new values before crash, so I wait for a new patch or new server patch or whatever.

Yeah, the offsets are changed too. I try to guess out for what.

Here is the new addresses.lua:
staticcharbase_address = 0x8687A4; --0x8687E0; 0x882F08; 0x8A1E50;
charPtr_offset = 0x56C;
castbar_offset = 0x238; -- ?

charX_offset = 0x2C;
charY_offset = 0x30;
charZ_offset = 0x34;
charDirection ...

I've found 4 addresses:

• 008687A4
  008687E0
  00882F08
  008A1E50

Oh I see now.
The previous address was the 'same', and the commented are the rest 3.
I thought the commented ones are some kind of 'history'

P.S.: You have to change "00" to "0x" to make it work.