int timenow=0;
// Reduce cooldown for this slot?
bool lock_slot[]={
// Sword slots
1,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, // 0..15
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0, // 16..31
// Magic slots
0,0,0,1,0,0,0,0,0,0,0,0,0,0,0,0, // 0..15
0,0,1,0,1,0,0,0,0,0,0,0,0,0,0,0 // 16..31
};
// Reduce cooldown time by 'cd_reduce' seconds (one for each slot)
float cd_reduce[]= {
// sword
0.5, 0.5, 0.5, 0.5, //0..3
0.5, 0.5, 0.5, 0.5, //4..7
0.5, 0.5, 0.5, 0.5, //8..11
0.5, 0.5, 0.5, 0.5, //12..15
0.5, 0.5, 0.5, 0.5, //16..19
0.5, 0.5, 0.5, 0.5, //20..23
0.5, 0.5, 0.5, 0.5, //24..27
0.5, 0.5, 0.5, 0.5, //28..31
// magic
0.5, 0.5, 0.5, 1.5, //0..3
0.5, 0.5, 0.5, 0.5, //4..7
0.5, 0.5, 0.5, 0.5, //8..11
0.5, 0.5, 0.5, 0.5, //12..15
0.5, 0.5, 1.0, 0.5, //16..19
100.5, 0.5, 0.5, 0.5, //20..23
0.5, 0.5, 0.5, 0.5, //24..27
0.5, 0.5, 0.5, 0.5, //28..31
};
float lastused[]={
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0};
VOID Lock(MHS_ADDRESS address, INT ItemID) {
extern UINT_PTR slotsptr={"",address};
int time=Time();
int i=0;
if (time - timenow > 250) { // limit the rate to save CPU cycles
timenow=time;
for (i=0;i<64;i++) {
if (lock_slot[i]) {
lockSlotById(slotsptr,i);
}
}
}
}
VOID lockSlotById(UINT_PTR address, INT sid) {
extern UINT_PTR slotptr={"",address+(sid*4)};
UINT_PTR test;
//if (IsBadReadPtr((void *)slotptr, sizeof(DWORD))) return;
if (!slotptr) {
PrintF("ERROR: coulnd't get a pointer to the desired skill slot!");
return;
}
test=slotptr;
extern float cdvalue={"",slotptr+0x20};
extern float cdvaltwo={"",slotptr+0x28};
// Avoid catching multiple keypresses on one by waiting 250ms between triggers for a single cooldown
if (cdvalue-lastused[sid] > 0.250) {
lastused[sid]=cdvalue;
cdvalue-=cd_reduce[sid];
cdvaltwo=cdvalue;
PrintF("Applying lowCoolDown to %s skill on slot %i. Time reduced by %f secs.",(sid>31)?"magic":"sword",(sid>31)?sid-31:sid+1,cd_reduce[sid]);
} else if(cdvalue < lastused[sid])
lastused[sid]=cdvalue;
}
// [[05A9B924]+(i*4)]+0x20
You are wrong, it matters how fast you spam it.Quote:
I noticed that it doesn't matter how fast you use it..once you started you have exactly 1 min to spam the shizz of bm2 and then you get DC. xD
I managed so far to do solo IC2 , EoDB2f,FT B1F,AOS1,IC1. FI for some reason is still a pain in the ass. xD
yes sir zeke you are correct, removing the dc flags for wearing a ring or bracelet or weapon is easy, but my great frustration is removing the dc flags of Attack speed, spamming, walk speed etc.. I'm still thinking of an idea that there is that 1 set of asm code that controls all that check, that, i cant find..Quote:
I've seen your release trainer thread so I assume you must have obtained base addresses for certain functions like aoe ect and made the into trainer for newer clients on cabal ph or whatever version that is. The reason I bothered mention olly was because of hell spiders threads about unpacking the client - and also the fact you could attach to cabal and get d/c then try to trace back to that function, maybe it would be easier to find the flags if you could do that I'd imagine. I'm not sure how your currently looking for the flags but I guess its possible you already are trying this?
Quote:
anyway about that 20 times, i set the no delay to 1 and freeze it, for example, the real cooldown of a burning hand is 1.3 sec, i created a lock script that would allow me to use that skill every 1 sec, Result: DC! does'nt matter if i press it slow or fast, its the same 20 times! i also got a skill counter that checks how many skill packets the client sends to the server, it is 20times, sometimes it goes 22.. after using the skill 20 times, then repeat, then same result over and over again.. i changed my lock script to 1.2sec just for a trial, result: DC..
with my debugger i still can't figure what really triggers that check, or is it server side? not the same as the accessory slot dc flags?
Hmm.. i think i need to dig deeper =)
Yes i thinks it's the same type of flag, but i would take the no skill cooldown for example; each skills have their "own" designated address and points to a pointer and another pointer.. and the potion cooldown is a defferent story, but there is this one address that when you change it to "1", it activates the GM command no cooldown, and disables all cooldown including potions.. the bottomline is that i wan't to find that one address or a line in asm code to disables all check.. and you are right, the structure isn't really that hard to understandQuote:
I guess its possible since its having to do with attacking mobs/interacting with other players/objects and such there could be distinct differences in the flags, however I wouldn't know. I don't know ASM at all, nor do I have any abstract knowledge of exploits in disassembling .exes, trying to understand ASM is like learning a new language, and it never seems to make sense. The formula/structure isn't really that hard to understand, just the logic in the functions being executed.