[ Disclaimer, Create new user --- Wiki markup help, Install P99 ]
Difference between revisions of "A shady goblin/Player Agreement"
From Project 1999 Wiki
(graph) |
m (br) |
||
Line 16: | Line 16: | ||
===Respawn data & method (P99 Blue)=== | ===Respawn data & method (P99 Blue)=== | ||
− | [[File:Shady goblin respawn trend.png|left| | + | [[File:Shady goblin respawn trend.png|left|400px]] |
* Period 1 (2/11/19) - 24 hours 8 minutes (Diamondfist) | * Period 1 (2/11/19) - 24 hours 8 minutes (Diamondfist) | ||
Line 30: | Line 30: | ||
** <small>*past midnight (US time)</small> | ** <small>*past midnight (US time)</small> | ||
* Period 11 (2/22/19) - 24 hours 10 minutes (Kunio) | * Period 11 (2/22/19) - 24 hours 10 minutes (Kunio) | ||
− | + | <br> | |
====Longest variance of the window==== | ====Longest variance of the window==== | ||
Revision as of 09:37, 22 February 2019
This is a sub-article on a shady goblin NPC and the daily contested turn-in.
Contents |
Player Agreement on P99 Blue
- Refer to P99 forum thread https://www.project1999.com/forums/showthread.php?t=317253
- Upon spawn of "a shady goblin", players will /random 1000
- Time limit to roll is 5 seconds from the first player roll
- Players must maintain a no-trade distance from Goblin spawn, to avoid disputes
- Players must honor their roll and turn in themselves (?)
- Turning in if NOT roll winner will be petitioned, as per the current player agreement (to be handled by GMs)
- Attacking, casting on, or aggroing Goblin spawn will be petitioned, as per the current player agreement (to be handled by GMs)
Respawn data & method (P99 Blue)
- 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)
Longest variance of the window
- 3 hours 16 minutes
Theorycrafting into repawn timer and window
- 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