You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may only apply to shops with a lot of items in the storage, but I've noticed that with some shops (that have 50+ pages of inventory) if I scroll through the pages rapidly it can severely affect the TPS of my server. I've seen the TPS drop as low as 10 when this happens.
This only seems to happen when spamming the next/previous page button. If I wait about 1 second between each press, there is no TPS drop.
Perhaps there's a way to put a cooldown on the scrolling buttons to reduce the impact on server performance.
*While on the subject:
This is also true for when players rapidly click on items to buy them. I recall that once upon a time this plugin had a delay/cooldown for how quickly you could click on an item to purchase it. It would be great if such a cooldown could be re-introduced, but made a part of the config.yml so Server Owners could decide on whether or not to utilize the delay, and how long the delay should be.
Thank you!
The text was updated successfully, but these errors were encountered:
This may only apply to shops with a lot of items in the storage, but I've noticed that with some shops (that have 50+ pages of inventory) if I scroll through the pages rapidly it can severely affect the TPS of my server. I've seen the TPS drop as low as 10 when this happens.
This only seems to happen when spamming the next/previous page button. If I wait about 1 second between each press, there is no TPS drop.
Perhaps there's a way to put a cooldown on the scrolling buttons to reduce the impact on server performance.
*While on the subject:
This is also true for when players rapidly click on items to buy them. I recall that once upon a time this plugin had a delay/cooldown for how quickly you could click on an item to purchase it. It would be great if such a cooldown could be re-introduced, but made a part of the config.yml so Server Owners could decide on whether or not to utilize the delay, and how long the delay should be.
Thank you!
The text was updated successfully, but these errors were encountered: