Why even bother asking for advice if you aren't going to listen to what's given? It's really simple.
You CAN do it your way, but in this case, your way isn't exactly the BEST (or fastest) way to do this. Here's just a brief explanation as to why: When you install a patch (any patch), this patch is created usually based on BASE code, a set of code that hasn't been modified. QuickMud has!! Olc affects the following areas in QM: comm.c, merc.h, string.c, and more. Now, how familiar are you with code? Because, to begin actually converting things from old handlers (race, helpfile,command, etc), to NEW handlers , you MUST understand what you are doing. For example, in QM, you've got nanny.c.. Said file doesn't exist in rom. Most of the stuff that's in nanny.c is, well, it's in comm. So, you have that to contend with. How do you plan on dealing with the fact that hedit has changed structurally? Again, simply put, you can't just overwrite one with the other.. It can NOT be done. Perhaps, I'm dragging this out, but at least listen to reason here.. If the only reason you want QM is because it runs, well, so does stock Rom (patched with the following). You've got to do FAR less work to it to get it up and running, than you would if you converted QM's olc to olc2. If you want it for other reasons, then by all means, go out and do it. However, as I said, you're making more work on yourself than is necessary. You CAN do things your way, but it's about 10X EASIER to get the following patches and install them yourself in a STOCK rom mud. These are the ONLY benefits to QM as far as I've seen. Olc2 Erwin's Boards Copyover Color Hell, I've added those to stock rom in between 3 and 5 hours. And that was taking a rather long break at the time. The point is, weigh the benefits of each. QuickMud's really NOT all that. The 4 features listed above pretty much make the entire "feature" list of QM. As far as I see it, there's NO benefit to spending the time needed to create or update the OLC versions on QM. I'll say this in closing, because you're determined to do things your way: Better people than you have tried (no offense meant) to create patches from olcv1.xxx to olc2. I worked with an imp last year that runs one of the only rot1.5 codebases out there (there's few others that I know of, because of licensing issues and all). Once he saw how good OLC2 was, he wanted to work towards getting the Rot version of OLC upgraded. No such luck.. To the best of my knowledge, a year later he's still got someone working on it. I've worked with others, quite good coders actually, that have had previous versions of OLC installed, lookd at the patch for olc2 and the finished product on a stable mud, then just sworn because of the fact that upgrading it is such a large pain. In short, good luck. I highly doubt you'll be able to do something that these people (some of the best techs I know) have been able to do, or something that's taken them 1yr+ to figure out (and they're still working on it). If you don't have a pbase, there's NOT a lot of benefits (hell, there's none) to taking a stock rom codebase and patching those in.. It's your call though, as always. ------------------------------------------- TJW: Head tech, Dreamless Realms Mud Personal: http://twhiting.kyndig.com Mud: http://drealms.kyndig.com Snippets http://drealms.kyndig.com/snippets Telnet telnet://drealms.kyndig.com:9275 The OLC2 Pages http://olc.kyndig.com -------------------------------------------
