Member Discussions

I'm running a ROM codebase and this is what I'm wanting to be able to do in my programs:

Basically something like:

if sex $g == 1
say $g is a male!

or

if class $g == 4
mob transfer $g 500


The difference there being the 'g' variable. What I would like something like this to be able to do is in the if checks, take the character who triggered the program and first check him/her against the condition its checking for, and then cycle through their group (if any) and if everyone meets the specific criteria, then continue with the command. With the command, I would like it to be able to basically do the same... affect the character who triggered it plus everyone in his group.

What my question is, for anyone familiar with ROM and the program structure, is there a way to do this within the current way its coded and structured? I could see ways of doing this by basically making copies of all of the checks and commands to account for group (like the 'gtransfer' command), but if possible I would really like to try to make a new character variable that can handle that.

The reason being is that we are going to be implementing a playable storyline, and there seems to be a consensus that being able to group through these quests would be ideal, and since so much of the quests are going to be scripted to where you have to be at a certain point in order to continue, it would be ideal to be able to check for something like '$g' instead of '$n'.

Anyone have any ideas?

Cowbell.

I think you answered yourself. :)

"say $g is a male!"

You can't do that, and wouldn't want to.

Put the choice in the function, perhaps with a switch:

if class/g $n == 4
mob transfer/g $n 500

I was hoping to be able to accomplish this without having to update every check and command within the system, but if I have to do it that way, I guess I'll have to do it that way :p

When I first started tinkering with code, I was very prone to doing things in a much more convoluted and complicated manner than was necessary (but it would usually work with no problems), and as I've gotten better I've gone back through and recoded or simply streamlined many of the things I've added. I was hoping there was a less complicated and more streamlined solution that I simply wasn't able to see yet :p

Thanks for the advice.

You'd have to set up a new variable ($g), then have it do something along the lines of:

// blah of course
CHAR_DATA *rch, *rch_next;

for (rch = ch->in_room->people; rch != NULL; rch = rch_next)
{
rch_next = rch->next_in_room; // no nasty NULLs
if (is_same_group (rch, ch))
return (rch);
}
ANyway, it's blah code but gives the idea.
maybe a switch at teh return part and do a check for the second statement etc (CASE 'class': one_argument(argument, arg); if blah blah blah etc)

One thing though, not sure it's really necessary. A grall prog will hit everyone entering the room (vs a greet prog). Although, yeah, Joe buys a sword, Bob is a cleric, shopkeeper says 'Bob doesn't like it if you cut people Joe'.

That's more or less what I originally tried.

I had defined the $g within the progs, and tried it a couple of different ways... one by using the for loop for everyone in the room that was in the victim's group and setting each of them as lval_char (it generally only returned in the check or command the last character reached), and I also tried to make it loop through the same function again for every person there was, but I didn't really have much luck with that either.