SolarStrike Software

Ah sry, i guessed this value would be overwritten during an update.

Hmmm,
the SVN addresses.lua is not OK, looks like there is no auto-update has been made.
I'll post mine, changes to previous version:
- run update.lua
-tablesBase = 0x9FF4C4, (got a problem with 0x9FF4C8 on a different PC)
-partyMemberList_address = 0x9FE238,

BillDoorNZ wrote:lol...surely you can just try both???

but:

tablesBase = 0x9FF4C8,

is the right one

Both are correct, so the first one is mine and the second one yours

edit addresses.lua
tablesBase = 0x9FF4C4,
Thanks to Lisa for her howto ^^
http://www.solarstrike.net/phpBB3/viewt ... 490#p24490

memoryReadIntPtr( getProc(), address , offsets )
So it starts at

0x932123 which points to 0x1243211
then do first offset 0x32
0x1243243

which points to 0x1031301
then do next offset 0x8
0x1031309

which points to 0x11929200
then do offset 0x61
0x11929261


So final address is 0x11929261

But ...

No many of us use win64 without any problems.
The error says there is something wrong with your ingame keyboard settings.

I think it's a bot-related problem, the distance is greater if the mob is greater, so distance + mob-size, but the size is not known atm.
The melee distance is located in the settings.lua
change it manually in WP

settings.options.MELEE_DISTANCE = 70
...
settings.options.MELEE_DISTANCE = 50

Next ...

partyMemberList_address = 0x9EDBC0,
tried works

tablesBase = 0x9EEE4C,
http://www.solarstrike.net/phpBB3/viewt ... 490#p24490

/run DEFAULT_CHAT_FRAME:AddMessage(TEXT("Sys533025_name")) I didn't think of that. Of course the ids might not have names. Not all ids do. Although I'm not sure of the normal behaviour for that command is, when using valid ids with no name.

Hm well then there is no other possibility unless you ...

How are we to see if the client displays the name if we don't know what the ids are?
/run DEFAULT_CHAT_FRAME:AddMessage(TEXT("Sys533025_name"))
I've tested a few of those ids, no translations, so I guess memorytable.lua is not the problem here.
I suspect it's a new range and the way memorytables ...

First memorytable.lua works since a couple of client-patches so i'm really happy about
Maybe these IDs are some old event items and they don't exist in the current Id table?
if so does the client display the item name?

nerdyone255 wrote: where is that getpartymembername function? i have my dps/healers all logged and ready to test

.functions.lua 1268

urgs some bugfixing here Lisa

function GetPartyMemberName(_number)

if type(_number) ~= "number" or _number < 1 then
print("GetPartyMemberName(number): incorrect value for 'number'.")
return
end

if partymembers == nil or _lastupdated == nil or (os.time() - _lastupdated) >= 60 then ...

I've checked memorytable.lua and it works but the static addresses/offsets seems to be broken so i can't find them because of too many indirect pointers.

Not easy to follow, but one question wouldn't be easier to load the right file directly?

addresses.lua 83

partyMemberList_address = 0x9E8F90,

-> http://www.solarstrike.net/phpBB3/viewtopic.php?p=26308#p26308

partyMemberList_address = 0x9E8FA0,

skills.xml 113

<skill name="PRIEST_FROST_SCARS" id="495563" rage="200" mana="180" cooldown="4" type="damage" target="enemy ...

tablesBase = 0x9EA22C, -- it moved from 1C to 2C
castingBarPtr = 0xA1BC10,
editBoxHasFocus_address = 0xA18FEC,
skillsTableBase = 0xA1E71C,

The skills table is something new to me. Combat skills will not be used when you run the bot. If you want to get it working immediately, do the above changes ...

I think the event-monitor version is the better choice but I'm not happy about how it is called.
a real timer is probably the better choice
<onLoad>
function runaway()
-- look in the middle of the room before
local angle = math.atan2(2407 - player.Z, 2292 - player.X)
local yangle = 0
player ...

Hm looks like this part of skill.lua 193 subtracts the rebuffcut from the skillcooldown instead of the buffcooldown.

if( deltaTime(getTime(), self.LastCastTime) <
(self.Cooldown*1000 - self.rebuffcut*1000 - prior) ) then -- Cooldown is in sec
debug_skilluse("ONCOOLDOWN", self.Cooldown*1000-self ...