Servers tend to have rules on how many units you can hire, but rules are made to be broken. Would it be possible for a future update to include a config setting that would allow for a hard cap on hired units by player data keep track of the number of units hired? Would it also be possible for a config setting that would disable the hiring mechanism entirely? Thanks.
1,688
pages
ALL POSTSConfig - adding hard unit hiring caps
(edited by administrators)
Why was the first suggestion crossed out? It would be nice to limit hiring rates through a config to prevent potential abuse when admis are offline. Another config change could be to disable/place a cap on player-made waypoints.
(edited by Therearewe123)
This was didcussed several times, and the gired unit cap is not really possible. At first it would work, but sooner or later the actual count of hired units and the count the game has will diverge, because there are several ways hired units can be removed without the game noticing, the prominent ones are world resets or corrupted chunks, eventually glitches and so on. So sooner or later the game thinks the player has more hired units than they actual have.
(edited by A Fandom user)
(This was also me, forgot to login, sorry for the spelling errors)
(edited by The Ranger Malvegil)
2003:E8:8F0F:EE00:5916:89B3:15DB:30F0 wrote:
This was didcussed several times, and the gired unit cap is not really possible. At first it would work, but sooner or later the actual count of hired units and the count the game has will diverge, because there are several ways hired units can be removed without the game noticing, the prominent ones are world resets or corrupted chunks, eventually glitches and so on. So sooner or later the game thinks the player has more hired units than they actual have.
This was didcussed several times, and the gired unit cap is not really possible. At first it would work, but sooner or later the actual count of hired units and the count the game has will diverge, because there are several ways hired units can be removed without the game noticing, the prominent ones are world resets or corrupted chunks, eventually glitches and so on. So sooner or later the game thinks the player has more hired units than they actual have.
Why not just add a menu allowing a player to dismiss troops remotely? Then the next time they are loaded, they could just not load/load as a dismissed troop.
(edited by MindlessReader)
That's an interesting idea. So the game maintains a list of hired units. When the maximum count is reached, none can be hired anymore. If there's now the case that the units got lost somehow, the player is able to remove those from that list. If the units still exist in the world, they're just dismissed (which can determined by just looking at the list when they're loaded the next time), so that the count stays right. Is this what you mean?
For me that sounds like a potential solution, though it can be discussed whether that's worth the effort or if this has any problems, but I like it.
(edited by The Ranger Malvegil)
The Ranger Malvegil wrote: That's an interesting idea. So the game maintains a list of hired units. When the maximum count is reached, none can be hired anymore. If there's now the case that the units got lost somehow, the player is able to remove those from that list. If the units still exist in the world, they're just dismissed (which can determined by just looking at the list when they're loaded the next time), so that the count stays right. Is this what you mean?
For me that sounds like a potential solution, though it can be discussed whether that's worth the effort or if this has any problems, but I like it.
Yeah, that’s exactly what I meant. The only mechanical problem I can see is whether or not the mod can change the data of entities that aren’t loaded, but I assume it can do that. (I only have experience in vanilla datapacks, and we can kind of do it there, so I’d be surprised if a mod couldn’t)
(edited by MindlessReader)
Changing the data when the entities aren't loaded is not necessary. The mod could maintain a global list of the hired units of a player. If an entity is loaded which itself says it's a hired one, but it's not in the global list, this can only mean that the unit was dismissed when not loaded, and in this case, the unit's internal "hired" state can be set to "dismissed".
(edited by The Ranger Malvegil)
In principle, it would not matter if units got lost in ways without the system noticing. Eventually, players with this problem could have their NBT tag associated with troop count reset manually.
Essentially, it is far more favorable to have an overzealous unit cap rather than none at all. It is much harder to check all players for compliance than occassionally edit out those whose unit amount does not match their actual units hired.
(edited by A Fandom user)
This sounds like it could work. We would have to try it and see.
(edited by A Fandom user)
They’d have to account for things where the entity doesn’t die by death. Such as /butcher.
(edited by TheArcReactor)