Max Entity Cap

[Wild1145]

Feature Request

Description

A maximum number of trains able to exist in any given world at any given time. To be defined in the configuration file either on a per-world basis or as a global limit applied to each world. This will enable server owners to minimise the risk of trains being used to lag their servers significantly.

Examples

Servers where players can spawn their own trains at any time.

[bergerkiller]

Traincarts has a GroupCreateEvent, and Id be willing to add some special extra events for when a spawn signs spawns it / player spawns it. Would this be something you could implement yourself with a simple event listener + config and cancelling the event?

This is one of those things which is infinitely customizable, like adding player roles that bypass it or adding exceptions to 'main server spawn signs' or stuff. So I'm hesitant to add something substandard only for requests to come in to turn it into a homer car.

An add-on/custom plugin would fit better here I feel

[Wild1145]

That's fair, I hadn't really thought people would want exceptions to a hard limit cap which is what I was going for here when it comes to a world limit. I'll have to have a look to see if a custom plugin to handle a limit would work for our use-case or not and what we might need to either contribute here or ask to get added.

[Paldiu]

This is something better suited for inclusion. A configurable entity limit per world would be valuable for a majority of consumers, especially those trying to limit the amount of overall entities on their server, alongside those who run servers with minimal memory allocation.

It doesn't seem like that big of a stretch to include a configurable value, and even further, a boolean toggle to determine whether or not to use the field at all (or allow a value of -1 for uncapped entity placement).

A possible better option would be to set the limit for individual users but that would require more effort.

Unfortunately, if you (the plugin author) cannot provide this patch, we will not be able to utilize this plugin as our development force is so thin you could see through it like a pane of glass, and as a result we don't have the time or capacity to make the necessary adjustments ourselves, not to mention our policy has been adjusted to exclude custom maintained projects.

[bbayu123]

Closing issue, not suitable for adding into TrainCarts directly