They look good, nice work

@Sir Walross
I’ve finally gotten around to retexturing the AK handguard that had been left unfinished. I kept telling myself I’d do it later, but ended up forgetting about it until now.

@Peter McFondle
Delete the installed_mods.json and mods_enabled.json files located in
C:\Users\[[YourName]]\AppData\Local\ZERO_Sievert,
then try running the game again.

Mod is not showing up in the mod list so the guns aren't renamed. Anyone else having that issue?

quick question, could you shorten the AKS74Us barrel so that the front sight sits flush to the wooden handguard? would look more realistic

@Spyyre
Fixed a bug where mods were not applying to magazines.

FYI the item name for the AUG FDE 30-round mag is "mod_aug_magazine_30_desert"

Updoot from my previous comment, I just ended up copying all the code from init.script from that mod and pasting it at the bottom of init.script in this one to get the names I wanted. And then I subsequently ended up preferring these and removed my changes anyways lmfao. Still would like to know if there is a way to change mod load orders though

Is there a way to change mod load order? I prefer the simplified names from Original Gun Names over the more detailed weapon names youve included in this, but I like using this mod.

I've never experienced anything like this on my Deck before and it's so weird that things I already tried fixed it, but only after a hard crash into a reset. I'm now playing with the stack mods, real weapon names and weightless ammo and it's all working just fine. I'd do some more experiments with this mod but I'm honestly terrified to try again, as I wasn't sure it was going to recover from the black screen boot loop

Only happened once I installed this mod specifically, with all the stack mods, real weapon name mod and weightless ammo mods working fine.

All that you suggest was done already, I put the game back to a vanilla state and reinstalled it with no change. It would still crash Steam any time I tried to open it. I deleted the mod .json files and still no change. Validated cache and no change. It ended up hard crashing my Deck and getting it stuck in a black screen boot loop for 20 minutes or so before it finally booted back up. Tried to launch the game again with an immediate CTD, but Steam was no longer crashing with it. I validated the game files one last time and it started working again.

@Chotato
If you installed my mod for the first time, there shouldn’t be any issues. The crash problem I anticipated only happens to players who were already using the previous version — since some parts were removed when the mod was “split,” the game can no longer find the old code, which leads to errors. So if that problem occurs, it means the game crashes when you interact with those “missing parts.”

Here’s what I suggest:

1. Unsubscribe from every mod, completely remove the game, and reinstall it from scratch.

2. Also back up your save files and delete them from the game folder.

If you’ve done all that, the game should launch normally. After you confirm a clean launch, try installing a very simple mod first and test again.

My guess is there’s a compatibility issue between the Steam Deck and the Zero Sievert Workshop. My mod itself is very simple in structure and can’t affect Steam as a platform.

Alright, I installed that other mod you pinned and now the game crashes on launch, but Steam just kinda restarts itself really quickly. Might be Steam Deck/Linux related, either way I'm not able to get this mod working on Steam Deck :(

However, now my game doesn't launch at all even with no mods installed. It closes on startup along with Steam restarting itself every time I try to launch it. I have no idea what's going on, but since installing this mod my game no longer functions, even back in a vanilla state.

I've even reinstalled the game and it's still not working. This mod totally broke my entire game and I've been trying to fix it for the last 40 minutes...

So this is before attempting to sub to that other mod you pinned, but I thought this was interesting enough to share. First time playing Zero Sievert, got the stack mods and real weapon name mods, worked fine. I installed this one after seeing how plain the normal AK sprite was in the loadout selector. The game crashed on launch, but not only that, it actually took Steam with it somehow?? I've literally never seen a mod take down Steam with the game it's installed in before and I have no idea how that's even possible.

I'm playing on a docked Steam Deck with monitor, keyboard and mouse in desktop mode btw

August 12, 2025 Notice

If the game crashes after the update, please subscribe to this mod.

https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?edit=true&id=3547455240

This issue occurs because the code disappears due to the separation of the mod, and it can be resolved by subscribing to this mod.

Okay, I really like the idea of registering as co-authors, I've send you a friend request, maybe we can talk about the details in our dm?

Or, I think this issue could be resolved by registering me as a co-producer. As far as I know, for a jointly produced work, it is sufficient for one of the producers to obtain the permission.

@Falselight
The sprites for the better scope are mine, but most of the sprites in this mod were taken—with permission—from other modders and partially modified.

@Falselight
You can go ahead and submit it yourself. Just make sure to credit the source.
In particular, some of the sprites weren’t made by me but by other talented mod creators, so you’ll need to get their permission yourself.

I tried and reworked your mods locally for another time, removed the extra features, combined the better scope mod together, renamed every attachment to make it look better, I also refactored the code. Do I need to send you a copy so you can upload it to the workshop? Or I can just go ahead and submit it on my own?

Yeah, these look way better

@Mk Ⅳ: GIRZU Thanks for your reply, I managed to remove the extra features locally. However an extra version of the mod is always great.

@Falselight
Replacing only the sprites proved technically difficult. For certain components, swapping out the sprite would alter their coordinates, and correcting those changes demanded significant effort. To address these issues more efficiently, I ultimately had to add new parts instead.

If what you're asking for is the restoration of the medium-range scope functionality, that can be handled by creating a separate mod.

Is it possible to have a sprite-only version? The sprites are really great, but I also wanna have the vanilla features back.

Wow, I love seeing the great detail that each of the weapons has. It even works for me with some weapons introduced with mods. Great job, one of my favorite mods.

@Kolkoplays
Important note: to edit a save file correctly, you need to start the game before editing files, then edit the save file and save it, go back to the game menu and load or resume the game. Hope this helps.

@Mk Ⅳ: GIRZU no idea I tried modding the slot it's in nothing I can do but kill the save thx for trying to help.

@Kolkoplays
Search for mod_dummy_stock in your save file and replace it with mod_ak74_stock_2. Then, launch the game and remove the problematic weapon.

My save seems to have issues it seems to be caused by your mod this happens even after I tried editing the save with the solution you told the other two had.

My problem was similiar.

Now after trying to launch I get this error code:
############################################################################################
ERROR in action number 1
of Step Event0 for object obj_player:
Item "mod_dummy_stock" not recognised

at gml_Script_trace_error
############################################################################################
gml_Script_trace_error (line -1)
gml_Script_item_mod_get_recoil
gml_Script_loot_mod_cont_get_stats
gml_Script_item_weapon_get_modded_stats
gml_Script_player_step_update_weapon_stats
gml_Object_obj_player_Step_0

Thanks in advance!

@Mk Ⅳ: GIRZU
Got it. I will wait fix by releasing your update.

Thank you so much!! It was Vector .45 in my case (and svd, but it didn't crash game, as I had it like that for quite a while). I can't get it off Vector tho XD I have now handguard flying in the top left of the weapon

@Mk Ⅳ: GIRZU

I just checked, it works.
Thank you very much, you are life saver! )

@GanaHrHr
@joyfuldirge

This issue appears to be caused by a randomly generated weapon equipped with a handguard. Search for mod_dummy_handguard in your save file and replace it with mod_ak74_handguard_3. Then, launch the game and remove the problematic weapon.

Same issue here, backup saves are also corrupted somehow, so it'd be great if there was any solution.

___________________________________________
############################################################################################
ERROR in action number 1
of Step Event0 for object obj_player:
Item "mod_dummy_handguard" has no .weapon_mod.handguard.att_2 data

at gml_Script_trace_error
############################################################################################
gml_Script_trace_error (line -1)
gml_Script_item_mod_get_handguard_x
gml_Script_player_update_weapon_laser_specific
gml_Script_player_update_weapon_laser
gml_Script_scr_player_state_move
gml_Script_player_execute_state (line -1)
gml_Object_obj_player_Step_0

eyo, I'm 99% sure, that it is caused by this mod (or Better Scope, still your mod tho). Is there a possibility you could fix it or something (or tell me how I can fix that), it corrupted my late game file :c

############################################################################################
ERROR in action number 1
of Step Event0 for object obj_player:
Item "mod_dummy_handguard" has no .weapon_mod.handguard.att_2 data

at gml_Script_trace_error
############################################################################################
gml_Script_trace_error (line -1)
gml_Script_item_mod_get_handguard_x
gml_Script_player_update_weapon_laser_specific
gml_Script_player_update_weapon_laser
gml_Script_scr_player_state_move
gml_Script_player_execute_state (line -1)
gml_Object_obj_player_Step_0

@Jay Minー26億の男ー
That's an item generation issue. Originally, the AS VAL isn't supposed to have a muzzle attachment, but when the item is generated, it randomly includes attachable parts. As a result, an undeletable dummy muzzle gets attached to the AS VAL, and since there's no coordinate value set for the muzzle, a muzzle dot appears at the (0,0) position. That's what makes it look like a 1 dot.

There’s no way to remove it, but if you purchase the weapon (it won’t have any attachments) or spawn it through debug mode, you should be able to get a version without the dot.

【Report】.50 pistol and AsVall have 1 dot on texture's top left

LOVE ITTTTTTT

NICE AND HOOAH!

Finally this mod comes to the steam workshop, thank you very much!