^ This. I'd put up more logs too, but either it's me losing horribly, so I'm ashamed to post them, or it's me winning, so I feel bad for my opponent when posting them. Plus, many of them are just too ridiculously long. If there are any specific requests, I'll be happy to oblige though. I do log every single fight (although not in HTML).
^ This. I'd put up more logs too, but either it's me losing horribly, so I'm ashamed to post them, or it's me winning, so I feel bad for my opponent when posting them. Plus, many of them are just too ridiculously long. If there are any specific requests, I'll be happy to oblige though. I do log every single fight (although not in HTML).
^ This. I'd put up more logs too, but either it's me losing horribly, so I'm ashamed to post them, or it's me winning, so I feel bad for my opponent when posting them. Plus, many of them are just too ridiculously long. If there are any specific requests, I'll be happy to oblige though. I do log every single fight (although not in HTML).
Didn't share that one because I thought you didn't post your logs.
Although personally I pretty much learned most of what I know about blademaster from reading full combat logs.
Although I have no idea how to log in mudlet other than just copying everything and hitting copy as html
Looks like you the new illusions buff got you killed. You might want to swap paralysis priorities down next time, as he was often illusioning it instead of giving it... (pva is a built-in alias, you can make many more). That and enable vconfig waitparalysisai on to wait for a paralysis confirmation before curing it, just to mess with him until he realizes you're waiting and starts hammering you with real paralysis.
A lot of serpent combat does involve looking at what your opponent is doing and adjusting your curing appropriately. At one point you could've done stabs on and ignored all of his illusions.
b) enable color logging in mudlet prefs and press the folder button that's bottom-right. It'll pretty much permalog then, as the button always stays on unless you turn it off.
That and enable vconfig waitparalysisai on to wait for a paralysis confirmation before curing it, just to mess with him until he realizes you're waiting and starts hammering you with real paralysis.
That isn't really such a huge concern, though. Any two-venom doublestab containing paralysis will be obviously real anyways (and so will be single curare jabs, due to damage checks), so it would only affect single curare dstabs and curare bites, and neither of those are fast enough to be particularly threatening, considering that even if you assume them to be illusions until you get confirmation, you well get such confirmation really soon, at least for most classes. (The only exception might be classes with rather long attacks, such as magi.)
I might capitalise a bit more on it if I get a torc, but as it is, I can't really abuse people waiting for paralysis confirmation all that much, particularly against fast attack classes (which BMs are).
It still is a small benefit for curare bites, but not quite as much as one would think.
Having willpower to focus would have helped the most. :P
And having said willpower would be a lot easier if one didn't spam focus so often when one doesn't have anything focusable or is off focus balance! Only like half of the focuses in there actually did something.
That and enable vconfig waitparalysisai on to wait for a paralysis confirmation before curing it, just to mess with him until he realizes you're waiting and starts hammering you with real paralysis.
That isn't really such a huge concern, though. Any two-venom doublestab containing paralysis will be obviously real anyways (and so will be single curare jabs, due to damage checks), so it would only affect single curare dstabs and curare bites, and neither of those are fast enough to be particularly threatening, considering that even if you assume them to be illusions until you get confirmation, you well get such confirmation really soon, at least for most classes. (The only exception might be classes with rather long attacks, such as magi.)
That's why I mentioned the option to ignore single-aff dstabs as well, though. It's a combination of things.
Not quite sure what I mean. What I was saying was: yes, waiting for paralysis confirmation until accepting it would have been good, and wouldn't actually have come with many downsides. It generally tends to be the smart thing to do against serpents.
Ignoring single-aff dstabs is potentially much more lethal than that, unless you only ignore single-aff curare dstabs, as it tends to make sticking asthma/weariness extremely easy.
Ignoring single-aff dstabs is potentially much more lethal than that, unless you only ignore single-aff curare dstabs, as it tends to make sticking asthma/weariness extremely easy.
Potentially - but not if you turn it off when you do start using them for real.
That's where the work of observing your opponent comes in.
Now, before everyone goes ahead and lists what I all did wrong there, let me first list the things I know I did horribly wrong, to get those out of the way:
Defensively:
- My curing priorities during the quad-mangle were terrible. Fixed now.
- There's a good number of other things I could have done defensively during the quad mangle, but I won't list those here for the sake of not ruining shaman combat completely. Fixed now.
- Didn't run when the mangling started. I usually do, but I was so exhausted at that point and thought that the mangles were harmless anyways, that I thought they weren't going to be a problem. So I stuck around in the hope that him staying on the offence might give me a chance to later attack him without him leaving the room immediately. Won't make that mistake again.
- Didn't really affect the outcome of this fight, but my system thought I had confusion so many times during that fight when I didn't. That's because I recently added a new confusion detection to my system, but the timers didn't sufficiently account for latency, so they often misfired. Fixed now.
- Also didn't affect the outcome of the fight, but I recently introduced a bug into my system that caused me to double-cure lots of afflictions. My outrifting message cause my cure function to fire and attempt to cure all my afflictions, so if I was, say, afflicted with confusion, I'd outr ash/eat ash, but on the outr message, my system would attempt to cure again and fire focus or tree. Basically, that meant that any time I had a herb affliction and also could focus/tree it, I'd both eat and do that. Fixed now.
Offensively:
- I was absolutely horrid at hindering his movement. Part of the reason was that I felt bad about killing his steed, since it wasn't collared, but I could have gotten rid of it otherwise. I relied way too much on block working, while I should have tried to "killroom". I also should have went for limb breaks, as tedious though it might have gotten.
- Even worse though: I was absolutely repetitive and uninventive in my lock attempts. I grew so frustrated about never getting off more than two dstabs in a row (and sometimes only one), that I just resolved to the mindset "ah, I can't kill him with any sort of plan anyways, I'll just do the same thing over and over again until I get lucky" - which is really a terrible mindset to get into. In retrospect, there are still so many other things I could have tried, even though some of them would be super lame (and even though most of them would still require three dstabs in a row to succeed). In my defence, I'm a bit sick with a fever and it was late at night, so I really didn't want to strain my mind too much :P Also, I'm still a total noob when it comes to fighting shamans.
Nevertheless, huge props to @Xer for killing me (now the second time) with one of the hardest classes to fight with.
Yeah, Xer is great against serpents. I've only gotten three doublestabs off against him once (which was a lock, so that was cool) but never again since then.
I never have to run from Xer. I dont understand why you dont just hit your killXer macro and win
Well, I didn't really have to run anywhere in there either. If I had cured right. But as lousy as my curing was, I should at least have run on that final mangle chain.
Comments
http://ge.tt/1nYZQ8Z/v/0?c
https://www.dropbox.com/s/xq9dn2arm60u12x/Caladbolg vs Sohl2.html
Hopefully that one works. Long fight though.. It started with me going outside of Sohls room evading out sniping then went into more combat stuffs.
Svof
Mudlet Discord join up
→My Mudlet Scripts
Didn't share that one because I thought you didn't post your logs.
Although personally I pretty much learned most of what I know about blademaster from reading full combat logs.
Although I have no idea how to log in mudlet other than just copying everything and hitting copy as html
→My Mudlet Scripts
Svof
Mudlet Discord join up
Svof
Mudlet Discord join up
→My Mudlet Scripts
→My Mudlet Scripts
Svof
Mudlet Discord join up
→My Mudlet Scripts
Svof
Mudlet Discord join up
→My Mudlet Scripts
-
One of the symptoms of an approaching nervous breakdown is the belief that one's work is terribly important
-
One of the symptoms of an approaching nervous breakdown is the belief that one's work is terribly important
→My Mudlet Scripts