I haven't been around much to test this myself, but I've been reliably informed that there are a few "bugs" with the Gatling gun mutator used on the Pug server currently, so I'll keep a list here with any status updates, and if you find anything not listed, please post.
- My Minigun bind no longer works - workaround provided
As with any custom/replacement weapon, the class name changes, therefore a bind containing the "getweapon classname" command will not work with the new weapon. You will need to update any bind that has "getweapon minigun2" to "getweapon minigun2|getweapon gatl_minigun2|getweapon gatl_PureMinigun2", or use the more concise bind "switchweapon 7" which will work for any form of Minigun.
- My Weapon priorities are messed up/"switchtobestweapon" doesn't work - fix provided
Same as above, because the minigun holds a new class name then anything that reffers to the old minigun will not work as it's supposed to, therefore all you need to do is open up your User.INI file and under the [Engine.Playerpawn] section, find the WeaponPriority[x]= section and add the classes gatl_minigun2 and gatl_PureMinigun2 wherever your minigun2 is located, e.g. -
...becomes...
... Remember to update any further Weapon Priority indexes to avoid duplicates.
- Kills/deaths are not registering in anyone's HUD & IRC Reporter bot when killed with the gun - confirmed fixed in 0.17.
This is actually an issue with the LeagueAS Enhanced HUD class; where users are able to easily customize their kill messages... LeagueAS did not include any scope for custom weapons with the new HUD, therefore any weapon other than the defaults is ignored, as a result the message passed to the IRC bot is also blank, but will appear as a timestamped "event" entry.
- Using 2d icons in LeagueAS, most/all the new miniguns are displayed as Sniper Rifles - possibly fixed in 0.17 - needs testing & approval.
Along similar lines to the above issue, LeagueAS currently lacks the intelligence to check whether the weapon is of a particular type (in this case it is of a type minigun2), therefore defaults to the last icon, which is a sniper rifle.
- Some miniguns are rotating, others are not - unchecked
Not checked this, but the mutator is programmed so that it *should* take the rotationrate and bIsRotatingPickup variables from the original weapon it replaces, however I noticed this is also an issue with Zeroping (which uses the same replacement mechanism), so I'm assuming it's a bug with the CheckReplacement function... Where some minis have actually taken the correct characteristics, I'm guessing this is where LeagueAS has physically moved/replaced the weapon where it differs from the original map.
- A minigun in map xxx is being displayed/has been spawned further away from its original location - unchecked
Again, could be related with LeagueAS' internal fixes; this needs verification - if people could let me know exactly where in a map this is happening (screenshots welcome) I can check this out and make per map tweaks.
- My Minigun bind no longer works - workaround provided
As with any custom/replacement weapon, the class name changes, therefore a bind containing the "getweapon classname" command will not work with the new weapon. You will need to update any bind that has "getweapon minigun2" to "getweapon minigun2|getweapon gatl_minigun2|getweapon gatl_PureMinigun2", or use the more concise bind "switchweapon 7" which will work for any form of Minigun.
- My Weapon priorities are messed up/"switchtobestweapon" doesn't work - fix provided
Same as above, because the minigun holds a new class name then anything that reffers to the old minigun will not work as it's supposed to, therefore all you need to do is open up your User.INI file and under the [Engine.Playerpawn] section, find the WeaponPriority[x]= section and add the classes gatl_minigun2 and gatl_PureMinigun2 wherever your minigun2 is located, e.g. -
Code:
WeaponPriority[29]=Minigun2TIW
WeaponPriority[30]=minigun2
Code:
WeaponPriority[29]=Minigun2TIW
WeaponPriority[30]=minigun2
[COLOR=lemonchiffon]WeaponPriority[31]=gatl_PureMinigun2[/COLOR]
[COLOR=lemonchiffon]WeaponPriority[32]=gatl_Minigun2[/COLOR]- Kills/deaths are not registering in anyone's HUD & IRC Reporter bot when killed with the gun - confirmed fixed in 0.17.
This is actually an issue with the LeagueAS Enhanced HUD class; where users are able to easily customize their kill messages... LeagueAS did not include any scope for custom weapons with the new HUD, therefore any weapon other than the defaults is ignored, as a result the message passed to the IRC bot is also blank, but will appear as a timestamped "event" entry.
- Using 2d icons in LeagueAS, most/all the new miniguns are displayed as Sniper Rifles - possibly fixed in 0.17 - needs testing & approval.
Along similar lines to the above issue, LeagueAS currently lacks the intelligence to check whether the weapon is of a particular type (in this case it is of a type minigun2), therefore defaults to the last icon, which is a sniper rifle.
- Some miniguns are rotating, others are not - unchecked
Not checked this, but the mutator is programmed so that it *should* take the rotationrate and bIsRotatingPickup variables from the original weapon it replaces, however I noticed this is also an issue with Zeroping (which uses the same replacement mechanism), so I'm assuming it's a bug with the CheckReplacement function... Where some minis have actually taken the correct characteristics, I'm guessing this is where LeagueAS has physically moved/replaced the weapon where it differs from the original map.
- A minigun in map xxx is being displayed/has been spawned further away from its original location - unchecked
Again, could be related with LeagueAS' internal fixes; this needs verification - if people could let me know exactly where in a map this is happening (screenshots welcome) I can check this out and make per map tweaks.
Last edited:
you numpty, It was answered before you even posted the first time
