totemo Posted June 29, 2013 Report Share Posted June 29, 2013 On all servers, you can see the approximate time before the next restart with /nextrestart On PVE, you can see who owns a pet. Aim your crosshairs at the block where the pet is sitting (or very close) and type /petowner. (The requirement to look at a block and not the pet itself comes from limitations of the APIs.) One further thing to mention, /nextrestart is based on the time when CommandHelper scripts are loaded. As such, if a tech admin happens to be modifying commands written in CommandHelper (and there are a lot of them) and reloads the scripts, /nextrestart will give inaccurate results. There are no plans at this time to make this work perfectly under those circumstances. Quote Link to comment Share on other sites More sharing options...
Ozomahtlii Posted June 29, 2013 Report Share Posted June 29, 2013 This is awesome! Thanks a lot for this totemo! Quote Link to comment Share on other sites More sharing options...
Trooprm32 Posted June 29, 2013 Report Share Posted June 29, 2013 Totemo is GOD. Good work! :D Quote Link to comment Share on other sites More sharing options...
buzzinbee Posted June 29, 2013 Report Share Posted June 29, 2013 Excellent additions! thanks :D Quote Link to comment Share on other sites More sharing options...
GMMan Posted June 29, 2013 Report Share Posted June 29, 2013 Two more commands noted from sources: /armor up/down: Gives or takes away chain armor (C only, obviously) /drama: Just type it. Quote Link to comment Share on other sites More sharing options...
buzzie71 Posted June 30, 2013 Report Share Posted June 30, 2013 Just a reminder that even though you can now see pet owners, this still does not give you the right to kill pets of inactive players. We, the staff, consider any unwanted pet killing to be grief, regardless of how active the pet's owner has been at the time. On another note, if you find pets purring or barking obnoxiously in public places, I highly encourage you to use /petowner to contact the pet's owner and ask the player to move them. Quote Link to comment Share on other sites More sharing options...
Herbrin3 Posted July 9, 2013 Report Share Posted July 9, 2013 Very useful, thank you. '/nextrestart' can be a bit misleading; I've seen it be 10 mins out. Perhaps you could put a caveat into the message, saying it is a rough estimate or someting. ie I've seen "next restart in 8 mins", then the restart hit 30 seconds after. Quote Link to comment Share on other sites More sharing options...
Mrloud15 Posted July 9, 2013 Report Share Posted July 9, 2013 Very useful, thank you. '/nextrestart' can be a bit misleading; I've seen it be 10 mins out. Perhaps you could put a caveat into the message, saying it is a rough estimate or someting. ie I've seen "next restart in 8 mins", then the restart hit 30 seconds after. After you run the command it says " The server will restart in about X minutes." It does not say the server will restart in X minutes but rather gives you a rough idea of how long untill the server will restart. Quote Link to comment Share on other sites More sharing options...
Diznatch52 Posted July 9, 2013 Report Share Posted July 9, 2013 After you run the command it says " The server will restart in about X minutes." It does not say the server will restart in X minutes but rather gives you a rough idea of how long untill the server will restart. I can't comment on the accuracy of Herbrine's statements, but I personally would not consider an 8 minute inaccuracy within a maximum starting time of 2 hours (because you will never be farther than 2 hours from a restart) to be within reasonable accuracy of a plugin such as this. If it was 2 minutes off, that's one thing, but to be 10 minutes off, that can hardly even be called "about." Quote Link to comment Share on other sites More sharing options...
GMMan Posted July 9, 2013 Report Share Posted July 9, 2013 I just noticed the new code for /pl. So now we can't be honest about what plugins we used? If the output isn't going to truthfully reflect what's actually running, why have the command in the first place? Quote Link to comment Share on other sites More sharing options...
totemo Posted July 13, 2013 Author Report Share Posted July 13, 2013 I can't comment on the accuracy of Herbrine's statements, but I personally would not consider an 8 minute inaccuracy within a maximum starting time of 2 hours (because you will never be farther than 2 hours from a restart) to be within reasonable accuracy of a plugin such as this. If it was 2 minutes off, that's one thing, but to be 10 minutes off, that can hardly even be called "about." The command is implemented in terms of the load time of CommandHelper scripts. No other easy options for implementing it come to mind. If they are scripts are changed and reloaded, the results will be inaccurate until the next restart. 3 Quote Link to comment Share on other sites More sharing options...
Diznatch52 Posted July 14, 2013 Report Share Posted July 14, 2013 The command is implemented in terms of the load time of CommandHelper scripts. No other easy options for implementing it come to mind. If they are scripts are changed and reloaded, the results will be inaccurate until the next restart. So in a case where it's off by 8 minutes, that's simply because commandhelper was edited 8 minutes after the previous restart? Quote Link to comment Share on other sites More sharing options...
totemo Posted July 14, 2013 Author Report Share Posted July 14, 2013 Yep. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.