So I went to set up m&m for Iosen, since he's been lacking for so long, and encountered a problem trying to install. Mudlet attempts to ask me where the m&m file is located.
And if I just 'select folder' it gives this error. Anyone know what I'm doing wrong? (Yes, gmcp is enabled and I've got the latest version of m&m [should have Mudlet too, but it's 2.1 so *shrug])
I downloaded the zip to the computer's downloads, and then selected that one as the one to be installed from the package manager. It's worked on mine and Pectus' laptops, respectively, and this is the first time it's had this problem. When I tried to find it in the downloads folder, it was missing. Let me try again, though...
Okay, so the ur'guard m&m folder just vanishes entirely.
How can I make MM try to cure paralysis with wafer before using focus body? Focus body cure has a delay, so it's annoying being paralysed for several seconds at a time when I can just wafer it.
Wafer also has a delay. The delay in curing paralysis has always been the case here. (I can't remember if we're planning to change that in the future, though.)
Couple of important points - Things may still be a bit buggy. It's a new mechanic so there will probably be some bumps. If you run into this, the best thing to do is send me a log and I will get it fixed as soon as I can.
Ice priorities may not be set correctly - I tried to set up a generic order to get everyone started, but you'll likely have to fiddle with it
Ice affs are probably at the end of your slowcuring queues so you'll want to adjust those.
Stance/parry will automatically convert to account for the new wound threshold (it basically integer divides by 100). These new values may not be want you want, you'll have to adjust them to the new system
You can switch between old warrior and new warrior curing using 'mmsp convert.' This will toggle between the two and will revert your stance/parry configuration, overhaul affs and how it tracks and cures wounds (with healing/ice). This should allow you to update prior to the actual release (if it still hasn't happened) and be fine until it is released, when you can just switch back. Fair warning, it'll load ready to handle the warrior overhaul.
Again, this wasn't an easy thing to add. Thanks to @Vadi for his patience with me and answering my questions about things regarding the system. There are some general things I need to adjust/add, but it should work for everyone. If you have issues, let me know, provide logs, and I'll fix it when I can.
Lastly, I hear some people are charging people for warrior overhaul updates to their systems. I'm not asking for that, I've updated it for the general public that uses m&mf, and I'm most certainly not trying to be shady or anything that I've already been accused of at least once since it went open-source. There may be issues and if there are, I'll do my best to fix them. There is certainly a possibility that I missed something and as a result, you're going to die bashing/fighting/debating/rping whatever. I'll tell you right now, it's not intentional unless your @Davos (I kid I kid), but let me know and it'll get fixed.
One thing I just realized that I missed is monks no longer wounding.
Monk wounding probably will use the old stuff and add wounds like they used to. System will think you have wounds, apply ice, realize you don't and that'll be the end of it. It's going to be spammy and waste a lot of ice.
Mine spams me out when I try to log in by trying to keepup everything (did they change a line in the login screen perhaps?). Also, not curing the new affs despite updating [yay me and my tendency to break code ]
Aaaand it's started gagging ii. No idea why. It's very, very odd.
I have determined that this is incredibly annoying, and I can't seem to isolate the issue, which resolves when I hit the button to emergency stop all timers and triggers, but does NOT resolve when I deactivate each thing manually.
I'm Lucidian. If I don't get pedantic every so often, I might explode.
@Tridemon - check errors and stuff, also show a log though nothing I've done should gag 'ii' or cause aethersight/geburah not to work. I tested those defs and they are working fine for me
@Raeri/@Rolsand - check errors and let me see the logs. It's working fine for me (I just tested with Lothringen a bit ago) and it's working for other people as well
Hey. After downloading the update, my mmf is trying to cure damagedlimbs with apply mending to legs/arms. I'm pretty sure it's registering as unknowncrippled, and I have no idea why. Also, when I install mmf vers 4 through the package manager in zip form, it looks like this:
and in the package manager:
If I uninstall one, it uninstalls them all. I don't think it's supposed to be like this as it wasn't the case for mmf vers 3, and frankly, I have no idea why it's doing that. It's probably related to the problem I'm having, so I felt it was useful to know.
Anyways, here's the log so you can see what I mean:
A female aslaran bites down on your arm, her massive jaws splintering bone with a sickening cracking
You may drink another health, mana, or bromide potion.
7097h, 4410m, 4850e, 10p, 18600en, 18600w Belrx-
Here's what I've tried (might be lengthy, just want to be clear in case anyone else is having this issue):
1) Totally deleting every instance of mmf from my computer. When I didn't do this, it seemed to be loading the old mmf files (vers 3), despite uninstalling vers 3 and installing vers 4 through the package manager.
- In every instance here on out, I've done the following before proceeding to the next step:
a) Deleted all mmf files from my computer
b) Redownloaded Templar.m-mf.v4
c) Installed mmf, went through the config startup options and restarted mudlet
*Installation was done through the package manager (in .zip form)
d) Tested getting damagedleftarm and damagedrightarm from an NPC.
2) Used 'mmsp convert'.
3) Reinstalled Mudlet
4) Restarted my computer
5) Ran Mudlet in administrator mode
The variables 'damagedleftarm' and 'damagedrightarm' are being set to true when I receive the afflictions, but the system is still trying to cure that affliction line with mending; and it is not responding whatsoever to the diagnose lines. It's probably a super simple fix but I can't really figure it out.
Any help would be appreciated. Thank you! I'm a total and complete Mudlet newbie, having been using z/cmud/mushclient for over a decade.
edit: Also, a separate issue is that the system is trying to stance legs before logging in; meaning I have to hard disable triggers before connecting.
edi2: I've also tried installing through importing the (import me).xml. This way doesn't cause the multiple instances of the Templar m&mf package to appear, but it still doesn't cure damagedleftarm or damagedrightarm with ice.
The multiple instances are normal - they contain additional modules like the harvesting module, etc that used to cost a little more, but are now also free and open source (and thus automatically packaged with every download for free).
Just ignore them (I know, my OCD screams at me too, but I grit my teeth and ignore them).
I haven't tested afflictions yet, so it may be a bug with damagedlimbs per se, you'll want to wait for Sidd to confirm. (Wounds curing worked fine for me, using ice to cure etc)
You can make an automatic trigger to pause the system when it connects to lusternia, and unpause the system when you get logged in. Here's the trigger I use:
Thanks @Salith, @Talan and me discovered this last night as well.
Two issues are cropping up.
1) With aff messages, we know which limb breaks now, so the triggers are outdated
2) there's a bug with the overhaul function that's causing issues. I'll work on a fix tonight.
Until then, for bashing purposes, do 'mmsp convert' to turn off the overhaul stuff, and if you have affmessages brief configured on, it'll cure damaged limbs fine.
Also disable those bashing trigs, so it doesn't apply mending.
@Synkarin: mmsp convert doesn't seem to be doing anything, as in it returns the message that it has updated stance/parry ie:
mmsp convert
(m&mf): stance/parry actionlevels updated for warrior overhaul
mmsp convert
(m&mf): stance/parry actionlevels updated for warrior overhaul
If I manually disable the overhaul stuff and turn off the bashing triggers, it doesn't even try to cure damagedlimb with mending.
It's no problem for me as I've made my own pseudo-system for bashing, but it might be something to look into for others' sake. Thanks for working on this!
Comments
Ixion tells you, "// I don't think anyone else had a clue, amazing form."
Ixion tells you, "// I don't think anyone else had a clue, amazing form."