One of the "frustrating" things about being a monk, is that you need to develop separate katas for everything. One set for each step in momentum. Another set for each step in momentum with razing. Another set of raze/non-raze that target alternating limbs to avoid stance/parry. Now multiply that by the number of "progressions" you plan to use. The learning curve is a challenge, especially effectively tracking momentum, stance/parry, rebounding in combat. Not to mention all of the aliases/keybindings needed to orchestrate monk combat can be overwhelming.

Thanks to the comprehensive M&M system, extensive documentation, and willing support from Vadi, I've managed to eek together a simple monk momentum tracker. The main benefit is that I can compact my combat actions to a single alias/keybinding and allow the system to think through my moves on momentum building progressions. I know this might be a simple bit of code for some... but it represents a major step forward in terms of combat potential and coding ability for me.



Looking to tweak this in two ways. FIRST, I want to hardcode an ectoplasm warning that would disable a combat attack and echo a message. Does this seem correct?



Also, I want to randomize limbs for the out-of-form spronghai kicks. Something where Mudlet will decide between the limbs I provide (i.e. rleg, lleg, rarm, llarm). Can anyone help with this bit of code?

That's correct.



Maybe this: http://forums.lusternia.com/index.php?show...st&p=778708 can help?

Thanks! I had seen this before, but couldn't remember where to locate the post. To take a snippet of my code, would the following work:

Almost:

And, you could replace 4 with #commands to avoid changing two things for any future changes made to the list of commands.

Not sure that I understand the application of this. Meaning that lleg wouldn't be randomly picked back-to-back? Is this better syntax:

Meaning you can add to the list of commands without having to change the number in the code.

Getting an error message on the following code:



This is what Mudlet tells me:



Halp???

Take away the send before cecho. It's a function of it's own.

Alright... I used Vadi's awesome documentation with the M&M system to respond to personal afflictions sending out my offense:



Now I want to start tracking my opponent's status. Namely shielding/rebounding/prone (more so for my nekai/angknek momentum building progression). I already have echoes set to follow my combat target only. For example:



Now I want to use that information to set values AND then place into my offensive listed above. This is a huge leap, and will greatly help me condense a ton of katas into a few keybindings. Suggestions?

The first script could be condensed a bit by declaring the commands (since it seems to be the same thing) table once before you get into the ifs:




As for tracking - to begin with simply, you could use a boolean variable to track whenever they have rebounding - true if they do, false if they don't.



... and set to false when you see them lose it. Just like mm.affl variables, 'if janalon_pvptar_hasrebounding' would check if they have it, and 'if not janalon_pvptar_hasrebounding' would check if they don't have it.

Do remember that you'll want to account for cases when they get rebounding up, leave the room and lose it, or leave the room without it, get it, and come back in... you won't see the lines for that.

Hrm... so this looks easy on the code side of things, though the logic of changing variables due to someone (either them or me) boggles my mind. Is there a quick and easy way to detect rebounding & shielding (such as a general room "look" description)?

Do you have psymet? If so, you could use read aura in psionics to check. It's not perfect but it helps.

Come to think about it... the idea might be better suited for mudlet side bar rather than automation.

OK... new avenue of thought. I want to create a set of forms that will shift offense to one arm when the opposing arm is incapacitated due to any number of afflictions: brokenleftwrist, mangledleftarm, fracturedleftarm, hemiphlegyleft, crippledleftarm, missingleftarm.

These forms will be integrated into my IF, ELSEIF keybinding progression.



First, can I use OR statements? For example:



What's the syntax on this one?

Yes, though you don't want it to be ambiguous, better to do:

Here's my beast of a keybinding so far:





I won't attack if sapped/aeon/ecto so I can prioritize curing. Attacking in a choke is paired down to eliminate envenom/wipe and out of form kicks. Also handling for one-armed and no-armed combat so I can make the most of a form and still gain momentum even under afflicted circumstances. I also have some degree of randomization on my 4mo and 5mo forms to chase stancing.

Now I am looking to set definitions for envenom based on my opponents archetype. For example, I want to first alias xpoison (i.e. xpoison wiccan) and have upwards of 4 poisons set (janalon_archetype_poison1 etc...) defined. This way I can swing dulak/mantakaya on newbs, and then switch on the fly to hadrudin for a more class-specific offense.

I understand how I can capture a variable for the archetype. Not sure how the archetype would then define four poison combination. Something like:

if janalon_pvptar_archetype == wiccan then
janalon_pvptar_poison1 == hadrudin
janalon_pvptar_poison2 == ezcozul

And then place " .. janalon_pvptar_poison1 .. " into the above bit where my poisons should be named.

Does any of that make sense? Am I overthinking this?

Since all you want to do is change what venoms are used depending on the archetype... what you could do is instead of evaluating what you venoms you should be using on each attack, evaluate once when you set it and then simply use the available venoms.

So, you could have two tables - one defines what poisons should be used for a particular archetype, and one that knows which venoms should you be using right now.

Because tables in Lua can point to other tables, all you'd need to do is change to which set of venoms the 'current' table is pointing to and that's it. Here's an example to start with...



And this could go into your archetype switching alias... current_venoms is a table that points to, and thus contains, what poisons should we be using atm


To use a random venom from the current archetype that's selected, you'd get it with:



That'd be all. I hope you'll see the cleanliness in this data / logic separation . You might want to set a default archetype as well in the data definition script so your combos won't break with current_venoms not defined yet.

For those who were asking, my most recent application of my monk grapple keybinding for M&M. This includes a momentum tracker, and also will prohibit actions if you under certain afflictions.