Commit Graph

11 Commits

Author SHA1 Message Date
74ffc20767 Update upstream B/CB 2017-06-02 23:41:05 -05:00
9534f437f4 Add more info, triggers to watchdog velocity warn
Adds entity name to exception message
Checks that the velocity to be set is NaN
2017-05-28 00:06:26 -05:00
16113437c6 Update upstream B/S 2017-05-23 17:11:28 -05:00
f7d8aa4188 Update upstream B/CB/S 2017-05-15 11:25:20 -05:00
ab4ae72fd5 Update to MC 1.12-pre2 2017-05-14 13:05:01 -05:00
22e2858fee Update bStats implementation 2017-04-22 01:16:45 -05:00
4340ef97ca Switch to a bStats based Metrics system 2017-03-25 00:22:02 -05:00
eccac70eac Compromise on warning of excessive velocity sets
We have long been receiving feedback about our warning messages when
excessive velocities are set on entities. We have, for the most part,
ignored much of this feedback because these warnings can be vital in
identifying the cause of a watchdog crash. These crashes would otherwise
be more difficult to identify without this information.

However, in many cases these warnings are unnecessarily verbose as the
server handles these excessive sets itself without user intervention.

As a compromise, we will only warn the user as part of a watchdog crash
log, and we will only include the most recent occurrence. This commit
represents a first effort on this front. It may need to be tweaked later
to provide more relevant information, such as the time it occurred,
and/or not printing the warning at all if the occurrence was a certain
time period ago.
2017-01-08 16:43:08 -06:00
f44524249f Don't check velocities on Projectiles
Closes GH-217
2016-04-17 13:32:19 -05:00
26eb457a39 Paper 1.9 2016-02-29 17:09:49 -06:00
21591b3dbd Add velocity warnings
Issues #12 & #18
2016-02-22 21:31:24 -06:00