/reset or /resetinfo or something

[Bargeld]

How about a typed command that will report the last time the server was reset and when the next reset is scheduled. Perhaps a set time in GMT or maybe X minutes/hours.

[Lokey]

Timely suggestion, we need to write a new method for server resets anyway.

[Daral0085]

Another similar idea, if it's easy to do, how about an automatic message when you log in when the next reset will be? This can help people from accidentally trying to mule stuff if they log in right before the reset. I wouldn't consider this high priority, but if it's easy to do then I think it could be nice.

[Shadowalker]

good points both.. I like the notice on login.. I offten find myself sending tells that reset is upon us when i see a player login for what appears first time in a while. and when ever I login to do anything akin to tranasfer, if I havent been online, im buggin others to find out when last was.

auto notice would benifit all.. not just the old and crusty vagrants we have lurking here. (<-this means YOU )

[Amoenotep]

if the resets are at a certain time i think we should all have clocks...so that we could look at them and see how long till the reset.

I haz edjukashun!

[mining]

if the resets are at a certain time i think we should all have clocks...so that we could look at them and see how long till the reset.

I haz edjukashun!

Ah, but what happens when DST hits

[Bargeld]

if the resets are at a certain time i think we should all have clocks...so that we could look at them and see how long till the reset.

I haz edjukashun!

Actually, thats one of the biggest problems... say i know a reset is coming in 4 minutes. I log out to do some stuff and login right about when I think the reset had just occurred. Would be nice to know if I'm 10 seconds from getting kicked or if it just happened 10 seconds ago. Current resets occur at like :58 or :59 minutes according to Windows time... maybe if the resets occured synched to Windows time server we could rely on it, but having to wait till :00 'just to be sure' is where I'm at right now.

And I agree that an autolgin message that tells server time would be helpful... but as an admin for a previous game, I know that there are alot of things that are useful information at could be presented to users at login. Personally, I made it a habit to not add login notices for anything a long time ago. Give the tools to the player and let them use them.

Next thing you know people will want to know where there relic is being held on login... there's a diviner for that. Then they would want to know how long ago it happened... and by whom, and then they would want to see... blah blah.

[Lokey]

Did the following for notice at login:
- Reset coming in a few minutes (anytime past 10 minute warning)
- Message if a dm disabled the auto-reset.
- If neither of the above, the approximate time (server local...can change that to zulu) of the next reset.

Reset is approximate, only bother to check every other server heartbeat which could be 10 seconds or 30 (granted that may be on a higher priority than other game objects). Currently I set it up for time server goes up + 6 hours. Oh and in 40 years that'll crash the server because unix timestamp won't fit in an int field

[Bargeld]

Awesome, thanx from me and I'm sure many others

[Shadowalker]

thanks... a certain enhasment

[cely]

Did the following for notice at login:
- Reset coming in a few minutes (anytime past 10 minute warning)
- Message if a dm disabled the auto-reset.
- If neither of the above, the approximate time (server local...can change that to zulu) of the next reset.

It might be more user friendly to have the next reset displayed like, "Next reset in 4 hours, 15 minutes" rather than a time stamp if it's more than 10 minutes out. That way no one has to do any timezone conversions.

[Lokey]

It just reads a local, I can certainly do that if someone would make a nice sql query

I think it's something like select time_diff(<stored reset time>, now(), minute?) Not sure if anything outputs a nice readable message or whether concat(above hour, above) would do weird rounding. http://dev.mysql.com/doc/refman/5.1/en/ ... tions.html

Mining was bribed to take some pics:

[Daral0085]

Oh and in 40 years that'll crash the server because unix timestamp won't fit in an int field

Not a big deal. If you're using unix, then our server is going down in 2038 anyway.

[mining]

In 2038, I want to still be playing NS4

[Lokey]

Was easy enough to give a time in hours/minutes. Looks like it's doing what it's supposed to.