Magi limb counting and other minor miracles

edited June 2017 in Magi
As some of you may have noticed, magi combat continues to frustrate me. I know magi isn't impossible. There are a few very good operators out there who make it work in spectacular fashion. However, successful magi combatants are still in a very small club. I'm stubborn, and Ognog hasn't changed race or class in his 400 years of existence.

The first problem I see is that of limb counting. You might think this has been solved with a magi limb counter in svof and others, but I've just learned that the trust I placed in the svof magi limb counter was misplaced. I had assumed it would adjust the ml_break_at as it becomes known for a given target, but it never seems to do this. By default ml_break_at is 5, meaning 5 full hits of staffstrike earth/water/fire to give a level 2 limb break (air counts as only half a full hit). However, the actual ml_break_at depends on the opponent. I've heard that there is a relationship between maximum health of the opponent and ml_break_at, but the exact nature of that relationship is probably only known by those few successful magi combatants. If the relationship could be formulated, then using ASSESS before a fight could set the ml_break_at parameter at the correct number.

Without being able to track when limbs are fully prepped, a magi truly has no hope of success. A big part of the difficulty is that there are no scriptable outward signs that a limb has been given a level 2 break. You'd think we would notice that half your femur is sticking several inches out of your skin and your lower leg is at an awkward angle, but strangely we don't seem to see this. You could look for two salve applications before standing up but that isn't easily scriptable and very easy to miss during combat. I thought the sawbones trait would be useful, but given that it doesn't report anything about limb preparation level and also takes a couple of seconds of balance I think sawbones is fairly useless.

Supposing I can overcome these problems and can then reliably prepare a leg and torso (say), I still have a very narrow window of opportunity with which to stick either hypothermia or dehydration. There's also a good chance my opponent would have succeeded in their kill strategy long before I get to this stage too. Even further complicating matters (and slowing the prep) is dealing with my opponent's parries and rebounding aura.

Any advice?


  • Become a retardation fighter and never fight monks.

     i'm a rebel

  • When I was a monk and couldn't code, I made an excel file that I would reference before and during fights. It told me how many hits it would take to break a limb at as many health points as I could test. I got this information by breaking people at different health values.

    I would suggest you do something similar. 

  • Magi limb damage is, as far as I recall, pretty straight forward: X non-air staffstrikes, plus Y air staffstrikes. For likely ranges of opponent health, X is always the same value, regardless of maximum health (there may be some extreme outliers, but unless you're jumping dragons while they hunt with full death cape stacks, you're probably not going to encounter them). Y is either one or two, depending on the target's maximum health. With the right artefacts, it should be possible to get a very precise max health value for when Y changes from one to two. People who already have this information are usually pretty willing to share it if you ask.

    However, the values do get tweaked occasionally, so you really need to be keeping up with your classleads news (the fact it's now on a separate board should help); I suspect that in the past Svo's limb damage values for Magi were reasonably correct, but they haven't been adjusted to account for subsequent changes.

    As for things being very easy to miss during combat, there are a few methods of making things stand out:

    1. Line formatting. Mudlet supports bold and italics, as well as foreground and background colours. It has a large number of named colours, but also allows specifying RGB values. You can use colour to make lines much easier to pick out when surrounded by regular lines of text. If you use enough distinct colours it should be possible to figure out what's happened just based on the colour of the line. There's no point saying "I'll make everything important yellow", because then you still have to read that text to know which important thing has happened, and sometimes text scrolls too quickly to read in fights.

    2. Echoes. Mudlet has an echo function for echoing text. It also has cecho and decho for echoing coloured lines. Svo has the svo.boxDisplay function if you want something a little more fancy (this is what it uses for the big orange warnings when your own limbs are damaged).

    3. Substitutions. These are basically echoes, but rather than echoing text in addition to the line from the game, you replace the line from the game with your own text instead.

  • Tesha said:
    Become a retardation fighter and never fight monks.
    @Althena Sup.
  • Hey those are about the values I have. Thanks friend!
  • edited June 2017
    Best ever post from @Aegoth. Now I can magi. 
Sign In or Register to comment.