SolarStrike Software

lisa wrote:local swimfunction_ptr = 0x44ABF0
local staticcharbase_address = 0x9C57EC;
local wallhack_addr = 0x97326C;

rev 609 has latest addresses and works, just do a svn update.

i'll try i have 606 now...

interesting, it seems to me you are using ublaziPad() and it is constantly turning fly on and off with different timers. I don't know why though Lisa, i'll look into it, don't have time for testing right now, and my bot is not working so i just changed the addresses for the swim value, and nop the ...

CHAPTER IV HACKS

Swim Speed Wall Happy botting

I'll test keypress possibility when i get time, in the meanwhile i'm working on a new hack for RomBot.
Btw any1 knows why rompros.com is not available (offline)?
I have 1 important message there and can't get to it :/ i ca still see i have 1 unread message.

I think you are right they multiply it by 0.25 or do some more arithmetics on that value.
So any value between tohose could be usable

Okay i have nothing to do so i'll explain it better for you just in case u need. Game stores the variable in address that we reach from 0x9BC394; by offsets 0x598 and 0x40 It's 4 byte variable but game only uses a byte at offset 0x42 so i don't change other bytes 0x40, 0x41 and 0x43 as i don't know ...

I don't think it'll work that way. Try this: local staticcharbase_address = 0x9BC394; offsetsx = {0x598, 0x42}; local curspeed = memoryReadBytePtr(getProc(), staticcharbase_address, offsetsx); printf("Speed: %d\n", curspeed); This works with int values made from those tables i gave you. Us...

thx will try it asap

That's just what i was getting, find my post or just overwrite this file in your classes folder:

It may be that it's going with 3 steps up :/
Like: 46,4A,4E,52,56,5A,5E,62,66,6A,6E - i think it's actually like this
as i wrot prrevious much too quickly.
Just test if value 5E or 5F works good or breaks the client or stops your char disables moving and you'll know which is good table.

Sometimes my RoM client bugs and those messages appear along with some other simptoms, it's fairly unimportant, just restart windows and surely all will be gone. For this particular warning/error restarting client works for me.

the flaw to that is that mobs may return -> stop following after a while if he doesn't get more than 8 mobs.

I think that my suggestion is much better than making all points travel. You'll just need a bit of planning while making a waypoint file but pays off in the end as you'll get what you need. For example in KS are mostly 3 mobs in stack. You could take first three, second threee and on third waypoint ...

I don't think you can do it without coding new functions in rombot. What i'd suggest that you pick the points for firing purgatory. For ex. waypoint 1,2,3 you go by with travel mode, then on 4 you change to normal. Then, bot will kill all enemies that follow him. But you will have to plan it all whi...

No other way then CE - Cheat Engine, but you can't actually read 50 - 59 there as they didn't store it like that, you need to read it in HEX sry. You have in my addon file addresses so get to the address and use this: HEX : VALUE 6F : 60 (you'll have pullbacks if you go higher than 59 most likely) 6...

I think it's good idea, specify a value to wait.

Yup, tested and working

@Rock5, No my computer is pretty new, Phenom II x4, 2GiB of ram, always working good, never have low fps or high CPU consumption with my set-ups. @Lisa, No it's not the aggro issue i think, what used to happen is that he picks up aggro starts casting purgatory without stopping, continuing towards ne...

This has solved my issues: (i also kept the one in the CPlayer:fight() function if it is needed sometimes because we're not finding enemies just precaution) if( bestEnemy == nil ) then bestEnemy = obj; bestScore = currentScore; elseif( currentScore > bestScore ) then bestEnemy = obj; bestScore = cur...

I have put this in CPlayer:fight() keyboardRelease( key.VK_W ); keyboardRelease( key.VK_A ); keyboardRelease( key.VK_S ); keyboardRelease( key.VK_D ); and it works, stopping the character, but only too late, like half a second later than it should be. He sometimes even goes to next waypoint :/ picki...