Database variables (aka data records, though that name is even more confusing and inaccurate) and the actual database are entirely different critters. Database variables are very, very useful things even when you're not using the database (they're essentially mini-database lookup tables you can build and maintain dynamically). In fact, the only relationship between them, apart from the name, is there's one place in using the database that you use a database-variable to update a database record.

They're really just hashtables or maps, but they are very handy. Lua is based on these sorts of tables, which is one reason I love it so much.

The main problem I had with the text file importing is that some of the trigger lines don't make sense. They appear as gibberish. And the other main thing is that instead of putting in actual line breaks it puts in ; For example, instead of looking like

#VAR rightlegmend 0
#IF (@prone AND @balance AND @equilibrium) {stand}

it imports as
#VAR rightlegmend 0;#IF (@prone AND @balance AND @equilibrium) {stand}

so I spent over an hour going through trying to remove those and insert line breaks and still didn't finish it.

The semicolon isn't a problem -- in fact, you removing them probably is.

The semicolon would only be a problem for someone who changed that special character for the command separation to something else, which is another issue with zMUD import.

The semicolon has proved a problem for me. Which is why I started taking them out. But that still doesn't fix some of the weird trigger lines. (?head|leg|arm) or something like that as just a trigger line makes no sense.

That should probably be (?:head|leg|arm), it's a regEx trigger. <,<

It might help if you provided context for these "errant" triggers, too, as it's likely that you've misunderstood how the code works. I used to use triggers with just body parts for tracking warrior afflictions, pre-wrapwidth 0, but they were toggled on and off as needed.

Eh, I've about given up. I'm going to just start writing my own system. I know enough about coding that I can do it if I get the aff lines. Yay spars.

If you're not afraid of regex and/or XML, you can get a lot of lines from Treant. If you are, well, have fun sparring!

Should be able to pull most of afflines out of mine, unless none of those are importing properly.

I'm done with finals now, and packing up to go home, so should have plenty of time to try to get this thing sorted out starting tomorrow.

And another system plug... If you're interested in Mudlet, you can always build off of Mantis or Stygian, since both are still being built and Mantis is open-source, so if you come up with a new idea or a change for the script, you can just send it in and it'll be made part of the system!

Plus, Mudlet's Trigger system is hella lots easier and more organized than MUSH, and it's faster too

"Hella lots easier" is definitely an individual thing. I much prefer MUSHclient's XML over Mudlet's XML, and I'm not a fan of Mudlet's settings editor, either. Personal preference.

Ditto that. As much as I like the idea of Mudlet... look at MUSH's settings options then look at Mudlet's. Something's missing. Lots of somethings.

Thirded..

I've tried mudlet...personally...I think it sucks hardcore. And I'd just upgrade to cmud if I had the money for a license key, but I don't. I have a key for zmud though so I stick with it. Hence my steady search for a curing system that works on zmud >_<

If you want a good system, you could easily spend 1000 hours writing it yourself. A system is WAYYYYY more than just putting in all the affliction triggers (which takes a long time by itself since there must be 1500-2000 of them). So how much do you value your time?

Quoted For Truth.

MUSHclient's XML is EONS ahead of Mudlet's as far as readability goes. There are also TONS more settings within MUSH to truly customize your experience.

However, this goes back to a similar argument: Apple vs. Windows. Apple is simple in the extreme, though doesn't allow for all of the customization and expandability that Windows does (this can be debated, though with my uses of each, I find that statement to be true... but I digress)

However, -I- personally find Mudlet's coding interface to be much easier to look at and to understand what's going on. Also, the fact that Mudlet doesn't require me to SetVariable() stuff is a bonus for me, but again, that's a personal preference!

For all the MUSH and Mudlet may or may not do, MUSH's interface is horrible and ugly.

I know a system is more than aff lines. I wrote one for Aetolia once upon a time. So I know the amount of time it takes. I value my time, yes. But at present I've got no job so time is all I have.

I'd buy a system off some one if I could afford to, but the whole no job thing puts a hold on that. So unless I can get one for free, back to coding for me!