Navigation
 
Server Status
 
Current Time
@104
 
Event Data

Event:
PSO 20th Anniversary

Start:
2020-12-21 22:00:00 UTC
End:
2021-01-18 22:00:00 UTC

Ranking for BP

  1. AzurBlu - 839404
  2. Sydney Beans - 725061
  3. Oof - 578421
  4. Wirk - 479133
  5. Rhinox - 476122
  6. Blst - 412619
  7. ncc1701p - 355090
  8. wally - 353228
  9. nucleardoom - 294512
  10. Gen6Gamer - 283587

Last Updated:
2021-01-18 22:00:00 UTC

 
Donations
Become a Patron!


 
Twitter
  • Apr 12, 2021 14:41:16 UTC:
    @ONESTARv2 Just normal maintenance. Mainly an upgrade of the OS installed on the server. As for PSOX, everything is currently in a holding pattern. Insignia is still not open to the public, and we will not be able to open Sylverant for PSOX connections until then.
  • Apr 12, 2021 14:39:50 UTC:
    Sylverant maintenance completed ahead of schedule. The server should be back to normal operating conditions. Please let me know if anything is broken.
  • Apr 11, 2021 20:48:33 UTC:
    The maintenance window may be shortened (that is to say the server may reopen earlier than the schedule above says), if conditions dictate that it can be.
  • Apr 11, 2021 20:47:39 UTC:
    Sylverant will have a scheduled maintenance period tomorrow, Monday, April 12, 2021 from 09:00 to 12:00 EDT (13:00 - 16:00 UTC). During this time the PSO server and website will both be inaccessible.
  • Feb 08, 2021 04:22:45 UTC:
    @dragonminded @BobbyDilleyUK I'm just an old-school Dreamcast homebrewer (since 2001 or so), that someone gave a slight push to start looking at the Naomi too.
 
 
 
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 - 2020 Lawrence Sebald | Site design by Jean-Paul Van Gorder