Clarification:
Most of our event code is unwieldy.
This is how I'd like it to work:

 The Command_processor
should have the following information in it for each valid command:

        Valid Command - "move west"
                Pre Acceptance Checking - "can I 'move west'"
                Event Class - "what kind of event is 'move west'"
                Event Delay - "how long will moving west take?"
                Event - "how do I 'move west'"

The Command_Processor will most likely have CODEREFS for each of the
data types, except for Event Class. For efficiency, Command_Processor
will contain a single hash of hashes... perhaps like the following:

        $self->{matrix}= (
                "move west"=> (
                        "Test"=>\&Player::MoveTest('west'),
                        "Class"=>"Player",
                        "Delay"=>\&Player::MoveDelay('walk'),
                        "Event"=>\&Player::Move('west')
                        ),
                "run west" => (
                        "Test"=>\&Player::MoveTest('west'),
                        "Class"=>"Player",
                        "Delay"=>sub { return int (100/($DEXTERITY /2)
+)} ,
                        # OR ##
                        "Delay"=>\&Player::MoveDelay('run'),
                        "Event"=>\&Player::Move('west')
                        ),
        }

###############################################################
So when the command processor recieves a request, it first checks
for the validity of the command:
        return $INVALID_CMD unless defined ($self->{matrix}->{$NEWCOMM
+AND});

And then:
        return $CMD_FAIL unless &$self->{matrix}->{$NEWCOMMAND}->{'Tes
+t'};

and if everything is okay:
        return $self->{eventqueue}->event_add(
                &$self->{matrix}->{$NEWCOMMAND}->{'Delay'},
                &$self->{matrix}->{$NEWCOMMAND}->{'Event'}
                );

And this is how it should work.

###############################################################
[download]

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.