Allows scaling of player damage per weapon/ammo/skin/prefab
Supported Games
Weapon Damage Scaler is a plugin that allows you to scale a player's damage per weapon, and/or ammo type. The plugin itself is pretty simple, here's how to scale damages.
Note: When scaling shotguns, remember that it is scaled for each pellet if buckshot ammo is used.
Permissions
- Both commands require the permission
weapondamagescaler.setscale - Scaling body part damage requires permission
weapondamagescaler.setscalebp weapondamagescaler.allowed-- Allows player to use weapon damage scaling
Chat Commands
Chat command works the same way: /setscale
Setting ammo is just as easy: /setscale "HV 5.56 Rifle Ammo" 1.2
To scale a body part, use: /scalebp weapon
Example: /scalebp weapon "Custom SMG" neck 1.1- This will scale the weapon's damage to the neck by 1.1.
Console Commands
Example of console command usage: weapon.setscale "Assault Rifle" "0.923". This will scale the damage of the Assault Rifle to 0.923.
Configuration
{
"GlobalDamageScaler": 1.0,
}
Localization
{
"noPerms": "You do not have permission to use this command!",
"invalidSyntax": "Invalid Syntax, usage example: setscale <weaponname> <x.x>",
"itemNotFound": "Item: \"{item}\" does not exist, syntax example: setscale <weaponname> <x.x>",
"alreadySameValue": "This is already the value for the selected item!",
"scaledItem": "Scaled \"{engName}\" ({shortName}) to: {scaledValue}"
}
</x.x></weaponname></x.x></weaponname>
This plugin is unlicensed and the original author reserves all rights to it.
The original author may request that this plugin be removed and there is a risk that the plugin may be unavailable in the future.
Note that the current maintainer may not have permission to assign a license to the plugin if they are not the original author, so explicit permission would need to be obtained from the original author in order for the plugin to remain openly available and guarantee that it will be around for all to enjoy going forward.
The original author may request that this plugin be removed and there is a risk that the plugin may be unavailable in the future.
Note that the current maintainer may not have permission to assign a license to the plugin if they are not the original author, so explicit permission would need to be obtained from the original author in order for the plugin to remain openly available and guarantee that it will be around for all to enjoy going forward.

