Spawning anti-exploit.

[drunkenboastor]

There is an anti-exploit in game that if a spawn that was triggered by a party with "X" demi count, and if any creatures from the spawn are later killed by a party with a much greater or lesser demi count then no xp or loot will be received.

I can understand an anti-exploit is needed to prevent players from spawning an entire map with a not demi character then bringing in an high demi count group to quickly clear the map.

I do not understand why is there no loot or experience received when a creature that was spawned by a party with a higher demi count is later killed by a party with a lower demi count. This obviously can be a problem if players crash, or have characters that are resting or get sent to the bad limbo while the the rest of the party is fighting.

[chirality]

it does feel strange that it's a thing, given that (at least in "modern" hg) no one would ever intentionally trigger the higher demi spawn -> lower demi kill mechanism.

have you tested under exactly which circumstances the rest of the party killing mobs that were spawned by the full party, when members are in limbo or in ppd, triggers this anti-exploit? i don't normally notice this in any scenario of significance such as during a boss fight.

in my experience, this anti-exploit triggers mostly in pop--constantly--which is really annoying but insignificant, and very rarely in hell/abyss runs where someone has done something unexpected or improper like spawned while the rest of the party was on a different map, or someone left party completely and then returned, causing the "lower to higher" version to fire.

the "higher to lower" seems irrelevant as an anti "exploit" due there is nothing really to be gained other than more xp and gems in practice. it's possible that this could be still deemed abuse as technically the party spawned harder mobs with greater rewards and then killed them with a party that would have been unable to spawn those mobs in the first place. even after considering theoretical "meaningful" rewards like canos, it still seems punitive to have "higher to lower" demi block those rewards, as again, spawning harder mobs and then using lower demi count to kill them is not something anyone would ever do intentionally (or perhaps it was at one time or perhaps there's an unforeseen angle or abuse that isn't immediately obvious).

the check for whether the spawn killed is at higher demi than the party killing should be removed if it's causing issues for people. i would also recommend editing the check for the opposite as well in pop, to only trigger if the demi difference is greater than (say) 10ish, to prevent it from triggering from 1-2 people "missing." it's just obnoxious, and there's nothing relevant to be gained by spawning pop at lower demi count and then killing at higher demi count unless the spawning demi count is far below the killing demi count, whereas loosening the check to ignore 1-2 toons' worth of demi would feel more forgiving and less punitive.