• Unfortunately, we have experienced significant hard drive damage that requires urgent maintenance and rebuilding. The forum will be a state of read only until we install our new drives and rebuild all the configurations needed. Please follow our Facebook page for updates, we will be back up shortly! (The forum could go offline at any given time due to the nature of the failed drives whilst awaiting the upgrades.) When you see an Incapsula error, you know we are in the process of migration.

oldms how to Identification attack whether crit?

Newbie Spellweaver
Joined
Sep 25, 2013
Messages
81
Reaction score
6
I saw a lot of source found that they are not in client packet achieve this
They use own one-sided random calculation
So will cause other people to see with their own crit is not the same
 
Custom Title Activated
Loyal Member
Joined
Jan 18, 2010
Messages
3,109
Reaction score
1,139
After v9x, packets had a boolean for critical display. Before v9x, you had to set it to the highest bit count or w/e, like so:

Code:
for (Pair<Integer, Boolean> eachd : hit.aDamageCli) {
                        if (SystemConstants.Version >= 90) {
                            mplew.write(0);//bCriticalAttack
                        }
                        mplew.writeInt(attack.nSkillID == 3221007 || eachd.getRight() ? eachd.getLeft() | 0x80000000 : eachd.getLeft());//eachd | (eachd << 31)
                    }

Pretty much if you get negative damage it'll be crits. Crit calculations in older versions weren't coded though. They never really were officially on public sources, so a lot of the times crits will be different.
 
Upvote 0
Back
Top