Hey Ive got SVOf in mudlet and my custom prompt is messing up, here is the code I use.
This is the code:
vconfig customprompt ^1@healthh, ^2@manam, ^5@endurancee, ^4@willpowerw EXP
@%xp%, ^y[
@gametarget] - [
@gametargethp]This is what it should look like:
2481h, 2768m, 12600e, 13500w EXP 77%, [] - []
This is what it actually looks like:
2481h, 2768m, 12600e, 13515w EXP 77%, [] - []2481h, 2768m, 12600e, 13515w EXP 77%, [] - []
It does everything double, does anyone know why this is happening? please help this is getting really annoying.
Comments
@Woulfen: Click on 'Package Manager' and see how many items there are saying "X svo". Having more than one isn't a problem, since the main system is one then the numerous add-ons (the number of which will likely depend on which class version you installed) are also an entry each; personally I have 7 entries. However, if you have more than say 12+ then you likely have more than one version of Svof installed.
Alternatively, you can click on Triggers, enter "svo hidden aff (evileye)" into the search box at the bottom of the Triggers window, and see how many results you get. There should only be one result of type Trigger with that name (though also another result with the name "Evileye"); if you have more than one then you definitely have more than one version of Svof installed.
Results of disembowel testing | Knight limb counter | GMCP AB files
Edit: Doesn't replace it, just puts the line into the prompt for some reason
Edit2: On a second note, and something not concerning the prompt, but something that I've been wanting to ask. Obviously I use the in game map rather than using the mudlet map or anything. This is just what I prefer. Unfortunately, some rooms, like the room I'm in in the picture below don't capture. Could anyone assist with making the capture work for that as well?
It's a bug that should probably be fixed asap, but temporary fix ftw.
EDIT: Obviously not a fix for it happening on one line every now and then. That's usually something to do with a custom echo or deleteLine breaking things, but there's a bug where it happens on every line, for which this is an easy fix.
And @Tolan, it'd probably be an issue with the patterns on your capture script.
In curing status you'll see the option to use clot next to a green o. Click the green o.