-
Notifications
You must be signed in to change notification settings - Fork 53
Description
What are you trying to do?
Replace MP5K_mp base weapon def with a MP5K_mp.iw4x.json weapon def. Changes include all entires; Stats, anims, model, fx, etc.
What problem are you having?
When building a MP5K_mp.iw4x.json into a fastfile with zonebuilder, loading the mod, and calling it in game either thru give or selecting it thru the menu. The weapon file built into the game in common_mp takes priority and your mod loaded .json weapon def cannot be loaded at all unless the name doesn't match a base game weapon.
Please walk us through the steps you have taken when you encountered this problem.
I have to rename the weapon to a non base weapon name, and use give commands or custom menu functions which we don't want modders who don't have menu knowledge to have to do this much work to replace a base weapon if the weapon is more complex then just a stat change aka whole weapon change. i created a tool that takes some data from a .json and throws it data into relevant calls but .json files would be much easier to work with if we could load them on the fly to replace any loaded in common_mp.
What have you tried so far?
I've tried to load a weapon raw thru weapons/MP, double checked naming and references for name match the base weapon file.
What version of IW4x are you using?
R4930
Anything else we should know?
i don't think so but feel free to reach out if u have anymore questions regarding the issue.
Expected behavior
When building a mp5k_mp.iw4x.json in a specific mod and loading that mod, I expect it to replace the mp5k_mp that may be built into an already loaded file.
Steps to reproduce the behavior
dump common_mp, grab a base game weapon of your choice, change some stats, model, or anims, and build it into a mod. Go in game and call the weapon with give or use a menu selection to get the weapon. See that stats, model, or anim will not be updated with your new created .json weapon def but that the common_mp weapon def takes priority or .json isn't recognized fully in some way to.