A shady goblin/Player Agreement

This is a sub-article on a shady goblin NPC and the daily contested turn-in.

On "A shady goblin" spawn, players will /random 1000
Time limit to roll is 5 seconds from the first roll
Players must stay away from spawn point, to avoid disputes about if Rolling or Clicking
Players must honor their roll and turn in themselves
Attacking, casting or aggroing the "a shady goblin", turning in if not roll winner will be petitioned as per the current player agreement, to be handled as GMs consider.

Period 1 (2/11/19) - 24 hours 8 minutes (Diamondfist)
Period 2 (2/12/19) - 26 hours 46 minutes (Bbeta)
Period 3 (2/13/19) - 25 hours 44 minutes (Murobb)
Period 4 (2/14/19) - 26 hours 41 minutes (Valewind)
Period 5 (2/15/19) - 25 hours 44 minutes (Henrique)
Period 6 (2/16/19) - 26 hours 38 minutes (Phatboil)
Period 7 (2/17/19) - 24 hours 32 minutes (Woton)
Period 8 (2/18/19) - 26 hours 43 minutes (Siryado) [broke Player Agreement]
Period 9 (2/19/19) - 27 hours 24 minutes (Obrez)
Period 10 (2/21/19*) - 25 hours 35 minutes (Arvan)
- *past midnight (US time)
Period 11 (2/22/19) - 24 hours 10 minutes (Kunio)

Given the facts of no repop prior 24:08 hours, no repop past 27:24 hours and a longest window variance of 3:16 hours, with a 11 sample size timers.
The common knowledge about respawn windows would make us think that a mob who can respawn +3:16 hours after last spawn could also respawn at -3:16 hours from last spawn.
In this particular case, we have so far a consecutive 11 size sample on which there are 0 negative windows based on the 24 hours mark. The chance, under normal conditions, for this streak would be lower than 0,05%
While it has no precedent, it sounds reasonable to believe the respawn time chance for this particular mob happens to be between the 24 hours and 27+ hours, without a negative portion on its window as its usual (which is
As the simple size increases, the spawn data will be more accurate

Contents