Can you make limits.
Example 1 player can only claim 1 of each or something?
Example 1 player can only claim 1 of each or something?
Option to limit claims per playerSuggestion
My recommendation is to try out cooldowns if you haven't already and see how well that works.
I'm hesitant to implement limits because I'm not sure it's the best mechanism for what people are usually after. It requires significantly more code to track the lifecycle of the tracked vehicles, including across server restarts. It also does not prevent abuse depending on which plugins the server is running. For example, Portable Vehicles allows the player to pick up vehicles they own. This would kill the vehicle entity and therefore deallocate the vehicle from the player's limit, allowing them to own and pickup as many as they want. Cooldowns solve that case better.
I understand not every server has plugins like Portable Vehicles, so it wouldn't be fair to constrain the features of the plugin based on a balance issue with a single plugin. That is, there's no reason limits can't be an option. However, it's also my opinion that cooldowns are more realistic and vanilla-friendly. For example, there's nothing usually stopping a player from amassing as many vehicles at their base as they want, but it takes time to acquire them. If they can acquire them, why shouldn't they also be able to own them all?
I'm not completely opposed to adding limits. I just want to make sure it's solving a valid problem that cooldowns don't already solve just as well or better. Can you tell me more about which plugins you are running on your server and why you think limits are a better solution for your use case than cooldowns?
I'm hesitant to implement limits because I'm not sure it's the best mechanism for what people are usually after. It requires significantly more code to track the lifecycle of the tracked vehicles, including across server restarts. It also does not prevent abuse depending on which plugins the server is running. For example, Portable Vehicles allows the player to pick up vehicles they own. This would kill the vehicle entity and therefore deallocate the vehicle from the player's limit, allowing them to own and pickup as many as they want. Cooldowns solve that case better.
I understand not every server has plugins like Portable Vehicles, so it wouldn't be fair to constrain the features of the plugin based on a balance issue with a single plugin. That is, there's no reason limits can't be an option. However, it's also my opinion that cooldowns are more realistic and vanilla-friendly. For example, there's nothing usually stopping a player from amassing as many vehicles at their base as they want, but it takes time to acquire them. If they can acquire them, why shouldn't they also be able to own them all?
I'm not completely opposed to adding limits. I just want to make sure it's solving a valid problem that cooldowns don't already solve just as well or better. Can you tell me more about which plugins you are running on your server and why you think limits are a better solution for your use case than cooldowns?
Thats for the information.
I'm Running
ClaimVehicle
VehicleAirdrops == All Vehicle can come from AirDrops or NPC at the bases. Fishing/Bandit.
VehicleDecayProtection == Set to no decay near cupboard.
VehicleDeployedLocks == Lock there vehicle for only them.
Don't care about being able to pick the vehicle up and i guess my only worry is the hordin as well being able to set a flag for vip players to have more then one maybe only 2.
The limit would be per vehicle so a player could have 2 minicopters, 2 scrapheli etc. Claimed with locks.
Also think there should be some kind of gui or display when looking at vehicle and its not your saying this is owned by or something along that line.
I'm Running
ClaimVehicle
VehicleAirdrops == All Vehicle can come from AirDrops or NPC at the bases. Fishing/Bandit.
VehicleDecayProtection == Set to no decay near cupboard.
VehicleDeployedLocks == Lock there vehicle for only them.
Don't care about being able to pick the vehicle up and i guess my only worry is the hordin as well being able to set a flag for vip players to have more then one maybe only 2.
The limit would be per vehicle so a player could have 2 minicopters, 2 scrapheli etc. Claimed with locks.
Also think there should be some kind of gui or display when looking at vehicle and its not your saying this is owned by or something along that line.
It sounds like the main problem you are trying to solve is hoarding. However, adding limits to this plugin won't prevent players from hoarding unlimited vehicles at their base. From your plugin list above, ownership will only affect which vehicles they can deploy locks to.
It sounds like there may be several ways players can purchase vehicles on your server. Is it really a problem that they can lock all vehicles they purchase? It doesnt sound like obtaining vehicles that way prevents other players from getting their own so it's not particularly disruptive.
Which vehicles are you intending for players to claim with this plugin? Ideally Vehicle Airdrops will have an optional feature to automatically assign ownership to the player that threw the signal. If that's not the case, suggesting that might be a better solution than requiring players to claim them after the fact, which takes running a command, and some mechanism to make the player aware of the command.
It sounds like there may be several ways players can purchase vehicles on your server. Is it really a problem that they can lock all vehicles they purchase? It doesnt sound like obtaining vehicles that way prevents other players from getting their own so it's not particularly disruptive.
Which vehicles are you intending for players to claim with this plugin? Ideally Vehicle Airdrops will have an optional feature to automatically assign ownership to the player that threw the signal. If that's not the case, suggesting that might be a better solution than requiring players to claim them after the fact, which takes running a command, and some mechanism to make the player aware of the command.