Question Trapped Items/Disarm Trap

Alright, so I now have the search ability working. If you search for a trap without inputting an exit or choosing one that does not exist, it'll kick back a "Which direction do you want to search?" If you search an exit, it will check your appropriate skill. If you succeed, it will display (by means of a short blurb like, "There's a small gas trap here.") all traps that are attached to that exit. If you fail, it will say you found nothing. If you fail by more than 20, it sets off all traps. If there was a successful skill check and there were no traps, it will say you found nothing; it'll be the exact same message if you failed the check.

Now that I did that, I'm working on being able to use zedit to stick those trap flags on exits. I've tried a little bit, but I'm a little confused by how it chooses to save those flags.

I did a little experimenting (I figured it wouldn't work but I wanted to see how the game would react if I did this), and changed part of zedit.
That displays argument 3 options. So for doors/exits, it would show you the option (normally) to set the door as open, closed, or locked. Here is where your input is saved, and I'll mark where I made a change.
Here is where I am confused. How are these values saved? I set up an exit to be closed, locked, trapped, and have a trap on it (this time the poison gas trap). Honestly, I expected different flags to be thrown up instead of trapped. In structs.h... I expected to have a Hidden flag set for that exit.

This is probably something else that is simple but eludes me. If someone can please explain how this is all saved to file (I tried reading the wld file that has that room, not familiar with the method it records flags on there), I think it would clear up a lot for me.

Overall this is coming out pretty good; I'm looking forward to sharing the results of this work once it's complete!

Edit:
I forgot to show what I see when using zedit, redit, etc. Also, it is behaving a little differently than I experienced last night.

So, here is what the zedit looks like after I try having a door set as closed, locked, trapped, and dart trapped.

I know why #2 says locked, not trapped: there's that strange if statement in a different function...
Note, this is in the zedit_disp_menu function, which displays the main menu.
It will only display closed, locked, or open. Not any other flags. So if I am going to change this, I am going to have to rewrite it (I'm sorry, that is just so hard for me to read).

Back on topic; we know what the zedit looks like. Closed, locked, trapped, dart trapped. However, when you look at the exit itself, after a zone reset, in redit...

Only the locked and closed flags have been toggled on (the door one I set on that exit before messing with zedit).

So, it is behaving differently than I thought: it doesn't even set the exit as Trapped. I actually toggled that on myself earlier. I will keep looking this over, but I don't really see how to make this work atm.

I hope people don't see this as being spammy; I wanted to post some of the progress I wanted to make, as it resolves (sort of) one of the issues I was having.

Before, in zedit, it would only show doors as "locked," "closed," or "opened." Setting any other values in zedit won't work, and will just show up as "locked." I've rewritten it so it will display more options than those three!

Now what is interesting is, looking back at my attempt to set an exit as closed, locked, trapped, and dart trapped, it now displays this in the zedit, even after rebooting the mud and the zone reseting, etc.

Now it still doesn't set the exit as trapped or dart trapped yet... but this is progress. I'm still trying to see how this is all saved and read, as it doesn't look like the options you're given in zedit ("0 for open, 1 for closed, 2 for locked") do not match up with the exit_flag numbers in structs.h. Will tell you more when I find something out.

Got it.

In db.c, I found where the state of a door, that you set via zedit, is used. Now it makes sense the way they did it!

And the best part is... it works. Zedit now properly loads/sets those extra trap flags.

I've been writing all of these changes and mods down in a txt file I can upload... I should update it now before it looks like a headache to write up.

So it's been a while since I last gave an update; I had other things to take care of and got distracted on top of that. Here's where I'm at so far:

Exits have traps that you can detect and disarm. You can set them to go off repeatedly, block an exit, or both. If you accidentally set one off, roll a saving throw to take less damage. If you're trying to disarm the trap and fail badly enough, it blows up in your face and you take the brunt of the damage. Also, if you use a key on a trapped door, it automatically disarms all of the traps. Note: if you disarm the trap by using the skill, you gain XP.

Containers also have traps, though I did a lot less just to save myself some headache atm. The traps tend to be a little more dangerous than exit traps, but I've made them so that they only go off once. If you use a key on the container, it will automatically disarm all traps (just like exits above).

Another note: you can stack multiple traps on exits and containers. So if you wanted to be really mean, you can flag an exit with 8 different traps.

Next, I will be working on the "check" skill for searching for traps on containers and "defuse" to disable a trap in a container. After that, it will be a matter of putting it into a txt file for others to read and destr-- err enjoy.

I found that trying to use flags for traps seems to work pretty well so far. Likely someone else will find a better way to do it. These traps also only do damage, so for those wanting to throw on affects like poison you're better off using DG Scripts in game for that!

I've added traps to containers and am in the process of putting all of this into a txt file for others to take a look. I've done SOME testing, to make sure the basics work (mostly with my Admin character; there shouldn't be any crashes).

I'll edit this post and attach the txt file once I'm done.

Edit: Done!

If you notice any bugs or have done any fixes, let me know so I can do them on my copy! And I'll post anything else that comes up as I continue to test this out more with actual PCs (gotta do some building first).

Not sure why I named it Emeril's Tricks and Traps snippet... probably because one day I was thinking, "BAM! Yer hit by a trap! BAM BAM BAM!"

Another edit: I found a small bug. Simple fix. Head to exittraps and make the following addition.

I essentially forgot to have it remove the TRAPPED flag on an exit. This would result in getting a message "You set off a trap!" on an exit when there's no real traps on it.

I think it looks good.

One thing - I'd probably try to avoid the magic numbers in the calls to the exittrap and objtrap functions. I suggest adding them to structs.h as Note that because we use these everywhere, it doesn't matter that the numbers aren't the ones you wrote