Downtimes: June 24 - July 2nd

We've got another batch of shutdowns coming in late June and early July, so that the machines can be repaired for the newest bug, the ZombieLoad CPU bug.

In general, the Genesis games (Grendel, TEC, TEC-Test) all have reboots scheduled for the absolute middle of the night, so I'll be taking each down the previous evening at midnight and bringing them back up the next morning at 9am.

The SkotOS games have always been more robust about reboots, so we'll let them reboot on their own, though there's some chance for an ~2 hour data loss. In any case, I'll be checking them after the 2-hour window when I can, though Marrach has a middle-of-the-night reboot, so that'll be the next morning.

The UserDB and Web reboots will cause some downtime for the entire site, but again they will hopefully come up cleanly.


- Shutdown Grendel (late Sunday 6/23)

- Startup Grendel (early Monday 6/24)

- Shutdown TEC (late Monday 6/24)

- Startup TEC (early Tuesday 6/25)

- Check TEC Client (9pm Tuesday 6/25)

- Shutdown TEC-Test (late Thursday 6/27)

- Startup TEC-Test (Friday 6/28)


- Marrach (Monday early morning 6/24)

- Ironclaw (Monday 10pm-midnight 6/24)

- Lovecraft, Lazarus (Monday 8pm-10pm 7/2)


- UserDB (Monday 10pm-midnight 6/24)

- Web (Sunday 9pm-11pm 6/30)
See more
See less

Reporting Bugs

This topic is closed.
This is a sticky topic.
  • Filter
  • Time
  • Show
Clear All
new posts

  • Reporting Bugs

    Castle Marrach has two ways that you can report bug or ... um ... "undocumented system features" ... to the game staff.

    The first, and preferred method, is the @bug system command. This command places your report directly into a queue that is reviewed religiously by the Lead StoryCoder and assigned to the appropriate staff member or forwarded on to Skotos depending on the nature of the problem. This is the most direct path to getting your problem in front of someone who can fix it. It is also the best route for when you are certain you have a reproducable bug. If you are uncertain, or have a question about whether or not something is a bug, you are free to post to this forum.

    This forum is monitored by both Castle Marrach and Skotos staff, who will step in to help when they can. This forum is also a great place to get information and opinions from your fellow players about whether or not something is a bug, if it can be reproduced in other ways, manifests in other circumstances, and so on.

    But how do you report a bug? Whenever you report a bug, we'd like you to include the following information in as much detail as you can -

    What did you do?: describe precisely what you did - what actions, what commands, what process. Be specific. If it involved particular characters, rooms, or objects, tell us. Describe every step of what you did before the bug appeared. Exactly what you typed in is very helpful information.

    What did you expect to have happen?: Simply put, if what you were doing had worked properly what should have happened? (We ask this because sometime the game works exactly like it is supposed to but the bug reporter wasn't aware of a change, had been misinformed about a feature, etc.)

    What did happen? Again, explicitely what happened. Did you receive an error message? If so, include it. Exact output of the parser is, again, very helpful.

    Additional Information: If it seemed to be associated with your browser, or with TWiki, we need to know the following:
    • What browser (version number)?
    • What operating system (verion number)?
    • When did you first see this problem?
    • Can you see it with other browsers? If so, which ones can you see it with and which one's can't you?
    Providing us this information is an enormous help to our efforts to track down the sneakiest of bugs. Some are obvious, but some are very particular about when they crawl out into the light. The more information you can give us the easier our job in squishing them,

    StoryPlotter Geist