NOTE: If you supply copies of your .yml or console log files, please use pastebin, dropbox, or other service and provide link, instead of copy/paste of the file into this report. Thanks!
What Version of OnTime and Bukkit are you using?OnTime: 3.13.3Bukkit: Spigot 1.7.9 b#1543
What storage option are you using? (YML or MYSQL) ? MySQL
What permissions plugin are you using? (Groupmanager, PEX,bPermissions, etc.) PEX
Please provide a link to a copy of your plugins/OnTime/config.yml: http://pastebin.com/jnBWaSeE
What steps will reproduce the problem?1. Login2. +Sprint down stairs
What is the expected output? What do you see instead?Expected, nothing. Instead, damage when sprinting down stairs + extreme lag + errors.
Do you have an console log of what happened? http://pastebin.com/H4RHCFBu
Are you having a "rewards" problem? Please provide a link to a copy of your /plugins/OnTime/rewards.yml : No rewards configured
Did you turn on OnTime logging (/ontime logfile enable 1)? If so, provide a link to that file too. http://pastebin.com/BiMjEmif
Please provide any additional information below. I have noticed the error (http://pastebin.com/B02CL0x6) happens when sprinting down stairs. the player also takes damage when sprinting down stairs. Don't see how it could be related but the error happens every time someone sprints down stairs.
I don't see how there can be any relationship between the console error you posted and the action of running down stairs. The console error is something about which I am already aware, and it is based on a timed event that happens every 10 minutes. So you should see such an error every now and then, even when people are not running down stairs. I have not issued a fix to this problem yet, because it actually has no adverse effects on your server other than a console error log now and then. (see this ticket for more info: http://dev.bukkit.org/bukkit-plugins/ontime/tickets/473-file-reloaded-automatically-to-this-error/)
The 'lag' problem may be related to the SQL errors you are seeing. I will have to investigate this some, but if you are NOT using the 'online table' to support a web page or something, I recommend that you disable (set to false) that function until I identify the issue:
# Enable if Online player status should be tracked in MYSQL Table
Yeah looking through my server log it doesn't throw the error as frequently as it first appeared. I will disable the online tracking and see if that helps. Thanks for your prompt reply.
To post a comment, please
or register a new account.