General Error
Module not accessible
Please notify the board administrator or webmaster: admin@tsugaming.com
^I get that when I try to access the moderator control panel.
April Fools?
Moderator: Tier 1 Mods
Forum rules
Only authorized staff may create new topics in this forum. If you have a news article that you would like displayed to the entire community, please create it in the 'Hangout' and then request that a moderator move it.
Only authorized staff may create new topics in this forum. If you have a news article that you would like displayed to the entire community, please create it in the 'Hangout' and then request that a moderator move it.
- danpaul88
- Bronze Member

- Posts: 1292
- Joined: November 13th, 2007, 7:34 am
- Location: Northampton, England
Re: April Fools?
Which particular forums have you noticed the problem on, and does it ALWAYS happen on those forums, or just sometimes?
Re: April Fools?
That's a rather interesting bug considering nothing that has been done in the last few days during the outage should have affected the forums in that way.
Danpaul, can you stay on top of Medici's bug to verify it exists? And if so: fix it. Thanks.
Danpaul, can you stay on top of Medici's bug to verify it exists? And if so: fix it. Thanks.
Re: April Fools?
I'm not sure it was a bug now, after checking again I think I may have tried to access the panel for a global announcement, which I probably don't have access to. Although it probably shouldn't come up with an error message.
Also, as I was typing this post, this occurred in the AOW server:
NR then reconnected briefly (for about 10 seconds max) and the whole thing happened again.
EDIT: I went into RDP and the error completely closed NR down.
Also, as I was typing this post, this occurred in the AOW server:
Spoiler: show
EDIT: I went into RDP and the error completely closed NR down.

Re: April Fools?
Two things, Medici:
- Problems with the AOW server have nothing to do with the site, so you should keep them in the Renegade server section (or admin forum).
- The error that you got was actually your fault lol. Nightma12 and I are running a special DEBUG version of NightRegulator in a different session. When you opened in it in your session it crashed the other one, thus the errors. As I've messaged you in IRC: do not open NR in your session until we say its OK, so that we can properly debug NR and try to fix some of these problems (finally).



