I have a need for two new if_checks, so that I can run a certain obj program, which I feel is pretty nice. Anyways, the ifchecks would be in_container, and num_in_container, the in_container would search for a specific vnum, in a specific container, and if it were set on a container, it would search inside itself for a specific vnum. num_in_container would just see how many objs are in a container, and would turn with the number. Also, now that I think of it, how would someone stop somebody from putting something in a container if the num_in_container returned 1 (as in 1 object in the container)?

in_container is a little hard because of the fact that it requires two arguments. mudprog ifchecks, at least the last time I looked at them, only take a single argument. Note that that might have changed in more recent versions like FUSS.

num_in_container is much easier in this respect because you only need one argument: the container to search. But it's a little unclear how to go about specifying the container itself.

I'm not sure if there is a mechanism to stop a command in progress. For starters, it would depend on when the trigger is, well, triggered. If the command has already taken place, then obviously you won't be able to stop it. If the trigger happens when the command is about to be processed, you would in principle be able to stop it. But like I said, I'm not sure if there is any such mechanism in place.

To be frank, issues like these are rather central to my very high frustration with mudprog, and my move toward other languages. I started my own several years ago that helped a lot, and now I'm in the process of moving that to Lua. Even though I am far from finished, things are much better already.

The stopping thing is for a specific instance, the object I want to make will be a container, and will have random stats, based on the SINGLE item inside of it, but it won't be the item's stats etc. Since it would have to be a single item, all other items would have to have uniform weight, or the 'num_in_container' ifcheck would have to be working, and the stopping thing would work when someone tried 'put obj container' and a message would say 'You can't do that!' or something, and then no item will have been placed inside of the container.