Placing pistol in backpack and then attempting to add it to handgun slot causes reset of attachments.
Description
Details
- Legacy ID
- 2949164297
- Severity
- None
- Resolution
- Fixed
- Reproducibility
- Always
- Category
- Inventory
player addbackpack "B_FieldPack_blk";
player addmagazine "30Rnd_9x21_Mag";
player addweapon "hgun_Rook40_snds_F";
Remove suppressor then move pistol to backpack and attempt to then add it back your your handgun slot.
As soon as you do this the pistol will stay in the backpack but will now have a suppressor again.
Now move the pistol from the backpack to the ground and back to your handgun slot and loaded ammo will be gone.
Event Timeline
hgun_Rook40_snds_F class name suggest that the model has default supressor [snds] so this is likely reason. I don't know if the model of the pistol should change from hgun_Rook40_snds_F to hgun_Rook40_F when you remove suppressor, but it doesnt at the moment. But if this is design decision not to change model I suggest using plain gun and separate suppressor instead.
player addweapon "hgun_Rook40_F";
player addHandgunItem "muzzle_snds_L";
Thanks KK, the plan is actually to use all base weapons. However, the same problem exists for that weapon+attachment. You lose the silencer when moving it to your backpack and back to the handgun slot.
If you move the weapon to the backpack then to the ground no problem, its just the failed move from the backpack to the handgun slot.
It seems to be some general inventory issue. Are you reading japapatramtara? Dunno if it has been reported, but if you open inventory and drag weapons to backpack you cannot drag them back to their respective slot. For example add backpack to basic unit as OP suggested
player addbackpack "B_FieldPack_blk";
Open inventory and drag your assault rifle to backpack. Now drag it back. You can't.
sry I was off for the most of January due of a personal reasons. That's why I didn't react.
Anyway this issue should be fixed in DEV. 114805(will be distributed tomorrow).
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.