Right now they start with one, and can buy an additional one.(for a total of 2) I don't want to remove the buying capability but i want the one they start with to count as the 1 per team.
The only difference is the addition of vehicleListAdd() when the vehicle is set to deploy, i.e. an MPB already in the mission. It does not make any changes to other vehicles. This will, however, affect missions that only allow one MPB to be purchased and there is already one deployed by the mission.
is more stable, and easier, you just call that to the MPB block on match startup for your specific game mode, and that will do it without modifying and scripts.
By doing so the vehicleCheck() function will disallow purchases since $VehicleTotalCount may be at the maximum or over. Unless you increase the number of MPBs in the $VehicleMax variable.
Right now they start with one, and can buy an additional one.(for a total of 2) I don't want to remove the buying capability but i want the one they start with to count as the 1 per team.
Comments
Right now they start with one, and can buy an additional one.(for a total of 2) I don't want to remove the buying capability but i want the one they start with to count as the 1 per team.
$VehicleTotalCount[%team, %blockName]
The only difference is the addition of vehicleListAdd() when the vehicle is set to deploy, i.e. an MPB already in the mission. It does not make any changes to other vehicles. This will, however, affect missions that only allow one MPB to be purchased and there is already one deployed by the mission.
$VehicleTotalCount[%team, %blockName]
is more stable, and easier, you just call that to the MPB block on match startup for your specific game mode, and that will do it without modifying and scripts.
Calling $VehicleTotalCount[1, MobileBaseVehicle]++; would increase Only the MPB's Count. Try it sometime.
I believe he made that clear enough too.