Results -9 to 0 of 60

Threaded View

  1. #10
    Player
    Jeeqbit's Avatar
    Join Date
    Mar 2016
    Posts
    8,673
    Character
    Oscarlet Oirellain
    World
    Jenova
    Main Class
    Paladin Lv 100
    Quote Originally Posted by VeyaAkemi View Post
    This quirk also exists for damage, it is visible if check damage log open after an enrage, the damage seem to radiate from the boss as a wave and whoever is close will die first, and there have actually been recorded instances of the boss being so low that some people die to the enrage, but the people who are furthest still manage to clutch the kill.
    It's pretty logical to get a list of users by proximity (and it is easy to prove they do this with hunts where mechanics hit the closest 32 players). It's also pretty logical to iterate through them in a loop.

    Should this occur in a separate thread while another thread processes the damage to the boss and its subsequent death, you get a situation where half the party die to enrage but the others don't.

    What doesn't make much sense is just how slow that is. A server machine capable of billions of iterations per second, per core, having for/while loops that are this slow.

    It's either precautionary to space out CPU load in case of busy combat scenarios with thousands of players and enemies across different zones on the same machine, or they just are afraid to touch the code for it despite 13 years of hardware upgrades and technology advancements that should make this concern increasingly redundant.
    (2)
    Last edited by Jeeqbit; 11-08-2026 at 02:45 PM.