Navigation
 
Server Status
 
Current Time
@807
 
Leaderboard

Event:
Wondrous Winter

Start: 2018-12-21 23:00:00
End: 2019-01-21 23:00:00

  1. NecroRevolver - 73109
  2. Modesty - 72034
  3. zakmat - 43302
  4. natural585 - 20920
  5. Jaxxer - 17898
  6. ChuChuFlamingo - 14766
  7. KPG - 13855
  8. Aleron Ives - 11031
  9. Lutz - 10785
  10. Chuck Norris - 7317

Last updated:
2019-01-16 18:09:18

 
Much Donate.


 
Twitter
  • Jan 15, 2019 00:06:43 UTC:
    There's less than a week left to gather tokens and place on the leaderboard on the Sylverant event "Wondrous Winter". Get out there with your highest leveled characters and face higher difficulties to gather tokens and leaderboard ranks most efficiently! #PSO #Dreamcast #Gamecube
  • Dec 26, 2018 04:36:16 UTC:
    @Tulio2Dream It doesn't appear that Palmacosta has support for scripting built in though, so the event still won't work. You need to run the configure script with "--enable-scripting" with Lua 5.3 installed to make it work.
  • Dec 23, 2018 15:00:42 UTC:
    @pcwzrd13 Glad to see people enjoying the event. That said, it only promises in-game prizes, no real ones. ;-)
  • Dec 21, 2018 23:10:29 UTC:
    New server event on Sylverant: Wondrous Winter -- https://t.co/YNL6Oj3Rjr
  • Nov 18, 2018 06:57:49 UTC:
    @pcwzrd13 Sorry, but that's too long. There's a limit of 16 unicode characters (spaces are allowed too, just not at the beginning or end of the name). ;-)
 
 
 
News

Server Event Results: Easter Egg Hunter Hunting

The second server event has been concluded for about 12 hours now (as of the time of this post), so here’s the results:

  1. Tangier – 10046
  2. Fallingferret – 3624
  3. KuromoriYu – 2302
  4. Crossi – 1416
  5. R422 – 673
  6. FaithY – 286
  7. bluecrab – 191
  8. treamcaster – 162
  9. aleronives – 138
  10. hawkzer0 – 129

I’m glad to see that even on shorter events we get a bunch of participants. Thanks to everyone who participated!

8 Responses to “Server Event Results: Easter Egg Hunter Hunting”

  1. Treamcaster says:

    Oleeee—-
    > aleronives

  2. 68kdude says:

    Well done Tangier, another mammoth effort.

  3. Tangier says:

    Thank you so very much..*Roxx_Gang*………..

  4. Treamcaster says:

    Off-topic: I just want to say this – Sylverant is on fire! Just look at the player numbers on a daily basis. Woot 😀

    • 68kdude says:

      Is there A population log somewhere? The “Other Place” had one I recall.

      • BlueCrab says:

        I have been keeping some sort of statistics in the database for a while now, but I’ve never gotten around to making them publicly available. It’s on the list of things to do, though.

        • K_I_R_E_E_K says:

          I remember doing something a few years ago where i would send lines of text to create an html file, it autoupdated by saving a portion of the html, we used divs i believe to save the lines (not sure if there was a better way) and then we would create a new file with:
          – the head portion
          – the saved divs
          – the new entry (in a div so it could be saved)
          – end portion

          We would repeat this as many times as we wanted, i’m not sure if it’s the best way because it added content without having a concern about the time scale, so for sylverant i’m not sure if you have another method in mind that makes data easy to read, having logged data every hour of every day for 6 months might be overwelming i’m sure 😛

          • BlueCrab says:

            Actually, the way I do it is to save a new row to the database any time the count of players on the server changes. Each row contains only two columns: the timestamp (in UNIX timestamp terms, so with one-second precision), and the number of players currently on the server. Any time more than one update comes in during a given second, only the most recent is kept (so if 5 people all connect to an empty server at the exact same second, the two entries in the database will be ([some date/time in the past], 0) -> ([that exact second], 5).

            In this way, I get up to single-second precision with the data without having to store the number at every single second the server is up. Of course, this has a few problems if the server is down for an extended period of time, but hopefully we won’t have that problem too often. 😉

 
Copyright © 2009 - 2018 Lawrence Sebald | Site design by Jean-Paul Van Gorder