Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Timings Issue - "Timings are off" #32

Closed
MrCaedes opened this issue Jul 10, 2016 · 3 comments
Closed

Timings Issue - "Timings are off" #32

MrCaedes opened this issue Jul 10, 2016 · 3 comments
Assignees
Labels
Bug This is a problem

Comments

@MrCaedes
Copy link

MrCaedes commented Jul 10, 2016

Recently installed this on a server running PaperSpigot, configuring it as needed. When attempting to use any of the commands related to plugin timings, or timings, from the React plugin - It states that timings are off in chat; providing no hint as to what I've done wrong.

Whilst I may be being dull, we've enabled timings under the reactions folder - And I can't find any command to turn timings on.

Any ideas?

Edit: Assuming this support question should be here, considering the large bolded text at the top of the plugin page - I would have posted on the Spigot forum, but this felt like a better place.

@cyberpwnn
Copy link
Contributor

I think its because you used it from the console. Here is the work around for the time being

  1. If timings are on, turn them off in the console
  2. use /timings on (INGAME)

That should work.

@cyberpwnn cyberpwnn added the Bug This is a problem label Jul 12, 2016
@cyberpwnn cyberpwnn self-assigned this Jul 12, 2016
@MrCaedes
Copy link
Author

Oh, thank you. That fixed it.

However, to clarify, timings are started when the server starts up - We're using PaperSpigot. Though, I do suppose that counts as a the console.

Fair enough. Thank you for your time - It just kind of threw me, considering timings was on and such.

@cyberpwnn
Copy link
Contributor

React is compatible with both, but both of them had the same issue. However this has now been fixed. Thanks for reporting it :P

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug This is a problem
Projects
None yet
Development

No branches or pull requests

2 participants