|
nutsnbolts Apprentice
Joined: 01 May 2002 Posts: 188 Location: USA
|
Posted: Wed Jan 07, 2009 8:49 pm
Zmud to Cmud...uhh.. |
Ok, I haven't used Zmud in a long long time but I do have my Mud "folder" which should have all my triggers, scripts, etc. I recently purchased Cmud and essentially, I can't figure out for the life of me on getting the old zMud into cMud?
Anyone can assist? |
|
_________________ Thank you for everything, it's always appreciated. |
|
|
|
Rahab Wizard
Joined: 22 Mar 2007 Posts: 2320
|
Posted: Wed Jan 07, 2009 9:26 pm |
It has been a while, but I believe the procedure is:
In the Sessions window, click New Session
Fill in Title, Host, and Port
For Filename, click Browse
Browse until you find and double click on the .mud file for your old char
Click Open Session Offline
It should load the package
I forget whether it automatically produces a compatibility report--if it does not, then:
Click Settings
In the Package Editor, click File|Compatibility Report
This should produce a report on (most but not all) problems your scripts might have due to incompatibilities between zmuc and cmud
Fix all the problems reported by the report
Go through the 'Changes for zMUD Users' document (sorry, I don't know how to insert a link here)
Go through your scripts looking for problems noted in the document (most of them should show in the compatibility report)
Finally, connect to the mud and try it out! |
|
|
|
Fang Xianfu GURU
Joined: 26 Jan 2004 Posts: 5155 Location: United Kingdom
|
Posted: Wed Jan 07, 2009 9:34 pm |
The first time you run CMUD, as well, it should offer to import your zMUD characters. You can do this yourself with File->Import zMUD sessions when CMUD opens. Be aware that some things are different in CMUD, though - you should run the compatibility report to check for obvious errors.
|
|
|
|
nutsnbolts Apprentice
Joined: 01 May 2002 Posts: 188 Location: USA
|
Posted: Wed Jan 07, 2009 9:36 pm |
Fang Xianfu wrote: |
The first time you run CMUD, as well, it should offer to import your zMUD characters. You can do this yourself with File->Import zMUD sessions when CMUD opens. Be aware that some things are different in CMUD, though - you should run the compatibility report to check for obvious errors. |
Where is the compatibility utility? |
|
_________________ Thank you for everything, it's always appreciated. |
|
|
|
nutsnbolts Apprentice
Joined: 01 May 2002 Posts: 188 Location: USA
|
Posted: Wed Jan 07, 2009 9:36 pm |
nutsnbolts wrote: |
Fang Xianfu wrote: |
The first time you run CMUD, as well, it should offer to import your zMUD characters. You can do this yourself with File->Import zMUD sessions when CMUD opens. Be aware that some things are different in CMUD, though - you should run the compatibility report to check for obvious errors. |
Where is the compatibility utility? |
Forget it. |
|
_________________ Thank you for everything, it's always appreciated. |
|
|
|
nutsnbolts Apprentice
Joined: 01 May 2002 Posts: 188 Location: USA
|
Posted: Thu Jan 08, 2009 5:31 am |
Crap lots of incompatibility.
|
|
_________________ Thank you for everything, it's always appreciated. |
|
|
|
albo Apprentice
Joined: 27 Mar 2008 Posts: 106
|
Posted: Mon May 04, 2009 2:34 am |
Well, I noticed a lot of compatibility with mine, and of course some incompatibility when I recently downloaded cMUD to try out for 30 days. But the issue I am seeing is that cMUD has so many new options that I am practically rewriting my entire main script. I have this trigger:
Code: |
trigger priority="7630" id="763">
<pattern>Exits:</pattern>
<value>#ALARM "AlarmID" +2 {#exec %pop( variablename)}</value>
</trigger>
|
which are all over the place, in different class folders, with different names for the alarms and the variables to %pop are different. When trying edit them to this:
Code: |
trigger priority="7630" id="763">
<pattern>Exits:</pattern>
<value>#ALARM "AlarmID" {+2} {#exec %pop( variablename)} classname here</value>
</trigger>
|
it will tell me that the trigger already exits. I was like that is bull jive! zMUD let me do it. But I soon starting making this trigger:
Code: |
trigger priority="15580" id="1558">
<pattern>Exits:</pattern>
<value>#ALARM "QB" {+2} {#switch (%class(classname)) {#execute %pop(variablename)}
(%class(classname)) {#execute %pop(variablename)}
(%class(classname)) {#execute %pop(variablename)}
(%class(classname)) {#execute %pop(variablename)}
(%class(classname)) {#execute %pop(variablename)}
</value>
</trigger>
|
so that it would just check to see which class folder was enabled and then execute %pop from the appropriate variable. Just a tedious task, but I mean would this be a better way to go about doing that? |
|
Last edited by albo on Mon May 04, 2009 4:50 am; edited 1 time in total |
|
|
|
wrym Magician
Joined: 06 Jul 2007 Posts: 349 Location: The big palace, My own lil world
|
Posted: Mon May 04, 2009 3:03 am |
Probably, but without knowing all your scripts it's hard to say, and could be hard to say even then.
I know towards the beginning of cmud several people did numerous test comparing speed on different trigger schemes, but i think the general conclusion was:
The more triggers/settings you have the slower cmud will process settings
The deeper your class path, the slower cmud will process settings
Enabling/disabling is faster than creating/deleting
The quicker lines are rejected from a trigger pattern the faster processing is
I think I would put all of that into one trigger and one alarm, and enable/set alarm time rather than numerous similar triggers and continuously recreating that alarm. Makes making a change easier, and it can be easier to find settings.
Yes, Cmud is picky with setting ID's. If you don't use a setting id, trigger patterns & whatnot get used, the first 64 characters
Yeah, Cmud has gobs of new features, and Zugg always seems to be adding new cool ones. |
|
_________________ "To the engineer, all matter in the universe can be placed into one of two categories: (1) things that need to be fixed, and (2) things that will need to be fixed after you've had a few minutes to play with them" - Scott Adams, The Dilbert Principle |
|
|
|
|
|