topaz-next-bot
commented
3 years ago 
Good point, I can take a look at this.
Open topaz-next-bot opened 3 years ago
topaz-next-bot
commented
3 years ago
Good point, I can take a look at this.
topaz-next-bot
commented
3 years ago
Related: It looks like DSP is treating resist[status] the same as resist[element] which is wrong.
When a resist[status] "procs" its an entirely different chatlog message (its not messageBasic like the existing resist message, its right between cover and magic burst messages in the client) than if you just resist from magic evasion (which is a messageBasic type).
Edit: actually looks like its just an additional short text preceding the usual message, is how the client has it done. Resist! <usual resist message here> like when PLD's cover goes off, rather the 2 fully different messages. In order to have 2 differing messages that way, it seems likely that status resist are checked separately form the meva calculations, in addition to any duration reductions they provide. Wiki's description of Resist Sleep supports this.
https://www.bg-wiki.com/bg/Resist_Sleep
Causes the Sleep status effect to be fully resisted a certain percentage of the time, regardless of how it is being inflicted. http://ffxiclopedia.wikia.com/wiki/Resist_Sleep
This trait greatly shortens the duration of sleep type status effects by increasing the chance of half duration resists.
Gives a small chance to completely resist the effect of sleep status. When it procs the text will be preceeded by "Resist!" in a similar fashion to Cover.
Okay so there are actually 3 types of resist sleep.
Type one is what BG explains, which is similar to what you would get from a trait. It provides a flat dice roll change to resist the spell and gives a resist! message when it does.
Type two is what ffxiclopedia explains. This is the type of res sleep you get from the resist sleep barspell. I have seen it have absolutely no effect on sleep landing rate, but it does decrease duration of the effect once it has landed.
Type three is mobs only, and functions identical to meva (but only for that particular enfeeble). Some debuff resistances are coded this way currently in dsp. It is important that the individual debuff meva be able to accept a negative value. For instance Fafnir is susceptible to paralyze, but not ice nukes. There is currently no way to replicate this behavior because a mod paralyzeres of -100 will cause fafnir's every hit to be paralyzed (even without casting the enfeeble).
topaz-next-bot
commented
3 years ago
The ffxiclopedia page is trying to cover everything not any one type, and then their general resistance page pretty much ignores all of it to focus on meva. Makes it a little difficult to sort out exactly what we should be doing when combined with retails low rates on the traits and gear bonuses. Retail has those gradually build resistance and lose resistance thing as well (immunobreaks). But I think I got us to far off your curse topic.
Pretty much the situation on mobs should be random vs mod_curseres, and if mod_curseres number wins..no curse at all.
I have:
Client Version (type
/verin game) not a client issueServer Version (type
revisionin game) f8175463415d4964d3deb2492d73a1bd03b548c6Source Branch (master/stable) master
Additional Information (Steps to reproduce/Expected behavior) :
DSP currently has no is no form of curse immunity, which is a big deal for high HP HNM which should not be receiving the curse spikes effect of igqira/genie gear.
Furthermore MOD_CURSERES was exhibiting unexpected behavior. When given a value of 100, curse effect from misery staff appeared to be a 100% proc rate. When given a value of -100 the proc rate seemed low, but it still proc'd.