just changing the base FPSWeapon scripts will not make this a mod. You will need to setup your own mod script and then listen/call the fpsweapon script and its objects to do what you want. That then is compiled into the mod file. If you change a base script file, you have to release it as its own stand alone build separate from the dev version; This is what I did for my combat overhaul project, before I got it moved to a mod file.
There is two ways to do this, and I did them both.
The first way is to rebuild the fps render system using the fpsweapon script public objects as a base and recreating what is private but needed. I did this by either directly calling the objects from the FPSweapon script I could, and the non-public ones, I rebuilt from the FPSWeapon script using copy/paste and some tiny edits. You can see my ambidexterity mod and the weapon script files to see what I mean. However, you will need to learn how to use the custom texture import option in the Atlast import object. The benefit of this approach though is it should be more compatible with other mods since it uses the atlas import. The draw back is it requires more work because it is relying on using both base script objects and creating your own where needed.
The second way is to create a custom texture importer and build the rect and render code from scratch yourself. I did this in my shield module, since shield textures were never part of the original game. This is the easiest one since your completely removing the original atlas texture system. First, you need to see if you can hide the original texture without breaking anything. I don't think you can false out the weapon show object, as it will then cause the weapon scripts to stop updating. The update cycles are directly tied to the weapon showing or not if my memory is correct. Once you hide those, you will need to replicate the fps render system. Just create the directories to store the textures, setup the code to pull the texture you need, and then trigger it. It is harder with weapons because you have 5 sprites to load based on the render frame. My shield is a single texture I move around using the built in rect vars.
Also, I believe all you did with those changes was double the texture size itself.
One thing to understand when working on this. There are multiple things that control how a texture is rendered and its size. Just multiplying them by 2 might not actually be giving you higher res textures or texture render room. It could just be doubling the image, so if you put a larger texture in, it would be even bigger.
Code: Select all
public static Rect shieldPos = new Rect(0, Screen.height - 400, 850, 850);
GUI.DrawTextureWithTexCoords(shieldPos, shieldTex, new Rect(0.0f, 0.0f, .99f, .99f));
As you see in this code, the shield position rec has its own size controllers to increase and decrease the shield texture size. Then there is the rect texture coordinates, which is the new Rect() in the GUI.DrawTexture object, which affects how the texture is rendered on the rect object itself. Don't confuse the two, as I did.
)
