This is a wiki for a reason. Anyone can contribute. If you see something that is inaccurate or can be improved, don't ask that it be fixed--just improve it.
[ Disclaimer, Create new user --- Wiki markup help, Install P99 ]

Difference between revisions of "Talk:A shady goblin/Player Agreement"

From Project 1999 Wiki
Jump to: navigation, search
({{talk}})
 
(Variance respawn data (archive): new section)
 
(2 intermediate revisions by one user not shown)
Line 1: Line 1:
 
{{talk}}
 
{{talk}}
 +
== Time limit to roll ==
 +
Some people are upset with the 5 seconds and wish to see it raised to 10s, 15s or 30s.<br>
 +
Seems like a reasonable request and it won't throw the respawn off by more than a few more seconds.<br>
 +
--[[User:Baler|Baler]] ([[User talk:Baler|talk]]) 21:30, 27 February 2019 (UTC)
 +
 +
== Variance respawn data (archive) ==
 +
 +
===Respawn data (P99 Blue)===
 +
 +
<br>
 +
[[File:Shady_Goblin_Trend_-_Mar_10.PNG|frame|[https://www.project1999.com/forums/private.php?do=newpm&u=151386 PM Daily ToD/Winner to keep this graphic/data updated]]]
 +
 +
* 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 <span style="color:red;">(Siryado) [broke Player Agreement]</span>
 +
* Period 9 (2/19/19) - 27 hours 24 minutes (Obrez)
 +
** <small>*past midnight (UTC -5 time)</small>
 +
* Period 10 (2/21/19) - 25 hours 35 minutes (Arvan)
 +
* Period 11 (2/22/19) - 24 hours 10 minutes (Kunio)
 +
* Period 12 (2/23/19) - 24 hours 55 minutes (Ecaroh)
 +
* Period 13 (2/24/19) - 24 hours 34 minutes (Cartel)
 +
* Period 14 (2/25/19) - 24 hours 16 minutes (Kelzaraz)
 +
* Period 15 (2/26/19) - 27 hours 20 minutes <span style="color:red;">(Farellron) [friendly dispute open]</span>
 +
* Period 16 (2/27/19) - 25 hours 15 minutes (Ausar)
 +
* Period 17 (2/28/19) - 26 hours 19 minutes (Samaranth)
 +
* Period 18 (3/01/19) - 27 hours 10 minutes (Gynette)
 +
* Period 19 (3/02/19) - 27 hours 38 minutes (Clurp)
 +
* Period 20 (3/03/19) - 24 hours 48 minutes (Mily)
 +
* [[Simulated Respawn]] (3/03/19) - (Narshe)
 +
* Period 21 (3/05/19*) - 27 hours 48 minutes (Chunkerz)
 +
** <small>*past midnight (UTC -5 time)</small>
 +
* Period 22 (3/06/19) - Need ToD (Need winner)
 +
* Period 23 (3/07/19) - 27 hours 6 minutes (temporal ToD) (Neezy)
 +
* Period 24 (3/08/19) - 24 hours 58 minutes (Kelza)
 +
* Period 24 (3/09/19) - 24 hours 31 minutes (Fistofflurry)
 +
* Period 25 (3/10/19) - 27 hours 6 minutes (Firenze)
 +
<br>
 +
====Longest variance of the window====
 +
 +
* 3 hours 40 minutes
 +
 +
====Theorycrafting into repawn timer and window====
 +
 +
* Given the facts of no repop prior 24:08 hours, no repop past 27:48, we are so far into a 3hours 40minutes maximun window, within a 20+ sample size timers.
 +
* The common knowledge about respawn windows would make us think that a mob with a 24 hours window, who could respawn at +3:30 hours after last spawn could also respawn at -3:30 hours from last spawn.
 +
* In this particular case, we have so far a consecutive 20+ 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,00002%, which seems fair enough to certify, his respawn time is not based into a 24 hour time.
 +
* With the current data info recolected so far, rounding up and down, the estimated guess for "a shady goblin" respawn and window would be of 25:50 hours +-1hour 50minutes.
 +
* That estimation would cover from the 24:00 mark (8 minutes less than the shortest window so far) and 27:40 mark (current longest window so far).
 +
* The estimation though, is getting close to a point on which it, following a round numbers logic, the 26 +-2 hours window starts to get weight.
 +
* The slightly over 24 hours window creates a situation and a window which keeps moving daily through the time, allowing roll to happen in good time frame for all time zones through the days.
 +
 +
 +
* ''As the simple size increases, the spawn data will be more accurate''
 +
 +
[[User:Maximum|Maximum]] ([[User talk:Maximum|talk]]) 17:08, 7 April 2019 (UTC)

Latest revision as of 17:08, 7 April 2019

Spellicon H.png This is a Discussion/Talk Area for a page


Create a ==New Section== for each topic

Sign each comment by using 4x tildes (~~~~)

Contents

Time limit to roll

Some people are upset with the 5 seconds and wish to see it raised to 10s, 15s or 30s.
Seems like a reasonable request and it won't throw the respawn off by more than a few more seconds.
--Baler (talk) 21:30, 27 February 2019 (UTC)

Variance respawn data (archive)

Respawn data (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)
    • *past midnight (UTC -5 time)
  • Period 10 (2/21/19) - 25 hours 35 minutes (Arvan)
  • Period 11 (2/22/19) - 24 hours 10 minutes (Kunio)
  • Period 12 (2/23/19) - 24 hours 55 minutes (Ecaroh)
  • Period 13 (2/24/19) - 24 hours 34 minutes (Cartel)
  • Period 14 (2/25/19) - 24 hours 16 minutes (Kelzaraz)
  • Period 15 (2/26/19) - 27 hours 20 minutes (Farellron) [friendly dispute open]
  • Period 16 (2/27/19) - 25 hours 15 minutes (Ausar)
  • Period 17 (2/28/19) - 26 hours 19 minutes (Samaranth)
  • Period 18 (3/01/19) - 27 hours 10 minutes (Gynette)
  • Period 19 (3/02/19) - 27 hours 38 minutes (Clurp)
  • Period 20 (3/03/19) - 24 hours 48 minutes (Mily)
  • Simulated Respawn (3/03/19) - (Narshe)
  • Period 21 (3/05/19*) - 27 hours 48 minutes (Chunkerz)
    • *past midnight (UTC -5 time)
  • Period 22 (3/06/19) - Need ToD (Need winner)
  • Period 23 (3/07/19) - 27 hours 6 minutes (temporal ToD) (Neezy)
  • Period 24 (3/08/19) - 24 hours 58 minutes (Kelza)
  • Period 24 (3/09/19) - 24 hours 31 minutes (Fistofflurry)
  • Period 25 (3/10/19) - 27 hours 6 minutes (Firenze)


Longest variance of the window

  • 3 hours 40 minutes

Theorycrafting into repawn timer and window

  • Given the facts of no repop prior 24:08 hours, no repop past 27:48, we are so far into a 3hours 40minutes maximun window, within a 20+ sample size timers.
  • The common knowledge about respawn windows would make us think that a mob with a 24 hours window, who could respawn at +3:30 hours after last spawn could also respawn at -3:30 hours from last spawn.
  • In this particular case, we have so far a consecutive 20+ 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,00002%, which seems fair enough to certify, his respawn time is not based into a 24 hour time.
  • With the current data info recolected so far, rounding up and down, the estimated guess for "a shady goblin" respawn and window would be of 25:50 hours +-1hour 50minutes.
  • That estimation would cover from the 24:00 mark (8 minutes less than the shortest window so far) and 27:40 mark (current longest window so far).
  • The estimation though, is getting close to a point on which it, following a round numbers logic, the 26 +-2 hours window starts to get weight.
  • The slightly over 24 hours window creates a situation and a window which keeps moving daily through the time, allowing roll to happen in good time frame for all time zones through the days.


  • As the simple size increases, the spawn data will be more accurate

Maximum (talk) 17:08, 7 April 2019 (UTC)