I can see it appear in Task Manager and then vanish. Right now, whenever I try to run CMUD from the Start Menu shortcut, it simply beeps and closes down without any other action.This is not 100% but is highly repeatable: it seems any trigger in the form stands a good chance of doing it, though if I delete and recreate it sometimes the new one works. Clicking on any of the other tabs on a trigger causes it to lock up.What could possibly be unusual about my system to cause this? Even importing from a very bare-bones zMUD file created for the purpose with nothing in it causes CMUD to lock up, 100% repeatably. And yet I still have some troublingly basic instability issues. All I have is a few triggers (manually made there) and the Rainbow Queue system, which is a few triggers and a few aliases. Just to be clear, at this point, I don't have anything near a system set up in CMUD. More importantly, I just got too frustrated with really basic instability issues. I spent a few hours on it yesterday and didn't quite get it working. I'll probably have it CC-BY, which is to say that it'll require attribution but otherwise you can fold/spindle/mutilate it at will.Ĭan't make any promises about when this'll happen though - Chahiero and I both have pretty demanding day jobs, so we can never really stick to deadlines.The process of trying to get the mapper in CMUD working took far too long, and I don't just mean the couple of months when I had to put the project aside and work on other things. But at the very least the handshakes and sending of the telopt data. ![]() I say that as a backwards way of saying 'I dont know how much of the functionality we'll take the time to make independent of our own codebase'. We'll be releasing our TELOPTs module back to the nakedmud community, though we'll probably have to rewrite large segments of it since it uses a lot of custom code - our mud is based on nakedmud but its been changed drastically. But I don't mean to start a holy war or something saying that. Im not entirely sure why other muds use more complex protocols when a lot of it is unnecessary. We chose MSDP because it was the most straightforward and standardised really. Got a pingback on the MUD news about this discussion. I'm also toying with the idea of adding an xterm 256 colour function - if muds got it "for free" with their protocol snippet they might be more tempted to use it. I've got commented sections showing where you would add support for MCCP, ATCP, ZMP and MSP, so perhaps that's enough. ![]() I'm not sure if I should add any other protocols to it, or keep it simple. MSDP will rely more heavily on the mud, because of the variables, but I'm going to try and keep it as generic as possible. So far I've got it supporting TTYPE and NAWS - I've added the snippet to a copy of GW1 to test it, and it requires only a few simple changes to the mud. I'm planning to release my snippet as PD, so people shouldn't be discouraged by licencing conditions. Nice! I've spoken to a few mud owners who expressed a mild interest - I doubt they'd go to the effort to implement it themselves, but they might be convinced to add a simple snippet. ![]() While on the MSDP subject, a second MUD server added MSDP support last week.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |