![]() |
|
AttackSpeed Fix Problem (nov files) - Printable Version +- LCKB (https://lckb.dev/forum) +-- Forum: ** OLD LCKB DATABASE ** (https://lckb.dev/forum/forumdisplay.php?fid=109) +--- Forum: Guides & Help Section (https://lckb.dev/forum/forumdisplay.php?fid=193) +---- Forum: Help & Support (https://lckb.dev/forum/forumdisplay.php?fid=157) +----- Forum: Ep4 Support (https://lckb.dev/forum/forumdisplay.php?fid=128) +----- Thread: AttackSpeed Fix Problem (nov files) (/showthread.php?tid=4159) |
- Matt Hias - 12-08-2021 after inserting the fix other characters get display errors or sent errors. if they are in the radius of the characters where attack speed 1 is playing. Ad looks like the character is just twitching. does anyone know the problem? I used this fix int m_attackSpeedlimit = 1; if (packet->attackSpeed <= m_attackSpeedlimit) //rondo157 packet->attackSpeed = m_attackSpeedlimit; packet->attackSpeedOrg = ch->m_attackSpeed_org; - rondo157 - 12-09-2021 Video? - Matt Hias - 12-09-2021 I hope everything works. here is a video that shows when you use -3 attackspeed when filled. and a little later it is at attackspeed +6. At some point the char gets a sent error where watching. But with the other char everything looks normal like when you play with attackspeed 1 2 /monthly_2021_12/screen.png.bf7affed3b71c1972f0128037b63005a.png" /> - dethunter12 - 12-09-2021 i assume you have a reference in character.cpp and PC.cpp correct? - zuendschnurx - 12-09-2021 I don't think anything changed about these files Or do I still have to change something? Sorry for other names on mobile phone I somehow can't get in with my FB. - dethunter12 - 12-09-2021 have you tried to read the error log with the client source? file->openfile: select .dmp ->debug with native code read the callstack - Matt Hias - 12-09-2021 he cannot find the PDB file. /monthly_2021_12/1.png.34e4dfff9f1093869cb9694d8cf474a0.png" /> that comes up in a window when I click on Yes Unhandled exception at 0x00ca9d14 in 2021-11-18 11_44_18.dmp: 0xC0000005: Access violation writing location 0x00000280. 2 |