Andrew Steinborn b0988bc50a Add a hard cap of 200 threads to VelocityScheduler ... This is a more realistic (generalized) solution for #943. Fundamentally, a plugin should not be spawning an unbounded number of asynchronous task execution units on demand from the user - an invariant Velocity itself enforces. However, since this practice is so commonplace, it makes sense that we would need to have some upper cap to at least make the practice safer than it currently is.		2023-02-18 16:20:12 -05:00
..
java/com/velocitypowered/proxy	Add a hard cap of 200 threads to VelocityScheduler	2023-02-18 16:20:12 -05:00
resources	Bump copyright date to 2023	2023-01-01 17:56:00 -05:00