 |
dsmoth
Newbie
Joined: 16 Jun 2007
Posts: 1
|
 Posted: Sat Nov 10, 2007 1:05 am
CMUD v2?
|
Hey, I'm curious... do you know of a "shooting for" date for CMUD v2.x Public Version?
I'm getting ready to start a project with Lusternia... and I'd like to know if I should download the Beta version of CMUD for the added stuff? Or should I just start working in 1.34 and then it will easily port over to 2? And would Beta have some scripting support that I'd need and should use anyway?
Love to know! Thanks! |
|
|
|
|
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
Posted: Sat Nov 10, 2007 1:21 am
|
I would suggest taking some time to read through the version history http://www.zuggsoft.com/page.php?file=cmud/version.htm
You should be able to notice the new features and many of the fixes of bugs that existed in 1.34. As of the 2.10 version there were no traceable issues migrating from 1.34. In terms of when for the next public release only Zugg really knows how many high priority bugs are left on his list, and if you review the version history you will probably find that Zugg has crushed a massive number of bugs in the past few versions. The best I can say is soon. |
|
_________________
The only good questions are the ones we have never answered before.
Search the Forums |
 |
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Sun Nov 11, 2007 4:53 am
|
Definitely before the Christmas holidays. *Hopefully* before the end of November. I think the 2.11 version is pretty stable for normal use, but I still have a lot of bugs still to fix. If you get something working in 1.34, then it should work in v2.x without very little changes. At least that's the goal.
The 2.x version definitely has *many* various improvements to the scripting, so looking at the version history as Vijilante mentioned is a good idea. Especially look at the 2.00 version at the very bottom of the page since it describes most of the major new features in 2.x |
|
|
|
|
Rorso
Wizard
Joined: 14 Oct 2000
Posts: 1368
|
Posted: Sun Nov 11, 2007 10:09 am Re: CMUD v2?
|
| dsmoth wrote: |
Hey, I'm curious... do you know of a "shooting for" date for CMUD v2.x Public Version?
I'm getting ready to start a project with Lusternia... and I'd like to know if I should download the Beta version of CMUD for the added stuff? Or should I just start working in 1.34 and then it will easily port over to 2? And would Beta have some scripting support that I'd need and should use anyway?
Love to know! Thanks! |
You probably want to download the latest beta and participate in the testing. That way you can report errors you find with the scripting system, and hopefully get it fixed before the public version is released. There is a lot of interesting stuff in the new version. For example LUA scripting support, ATCP support which should make it much easier to map areas in Iron Realms MUDs, new XML import/export functionality, scripting threads, trigger testing like in zMUD, and more.
Just remember when beta testing that you need to take frequent backups. |
|
|
|
|
Azerack
Beginner
Joined: 05 Nov 2007
Posts: 14
|
Posted: Sun Nov 11, 2007 2:53 pm
|
So when a new version comes, will we have to save our packages, uninstall the old and install the new, or will there just be a simple "update" button that does everything for us? 
|
|
_________________
"I'd be more enthusiastic about encouraging thinking outside the box when there's evidence of any thinking going on inside it."
- Terry Pratchett |
|
|
|
Seb
Wizard
Joined: 14 Aug 2004
Posts: 1269
|
Posted: Sun Nov 11, 2007 4:44 pm
|
| Azerack wrote: |
| So when a new version comes, will we have to save our packages, uninstall the old and install the new, or will there just be a simple "update" button that does everything for us? |
The best idea IMHO (at the moment - might change when the Public version is released) is to install new versions in a different folder, with data saved to that folder too, and then you can copy your packages and other data to the new version installed location, and that way you can easily run whichever version of CMUD you want, and you've still got your old version and settings in case there any show-stopper bugs for you. |
|
|
|
|
Rorso
Wizard
Joined: 14 Oct 2000
Posts: 1368
|
Posted: Sun Nov 11, 2007 4:59 pm
|
| Seb wrote: |
The best idea IMHO (at the moment - might change when the Public version is released) is to install new versions in a different folder, with data saved to that folder too, and then you can copy your packages and other data to the new version installed location, and that way you can easily run whichever version of CMUD you want, and you've still got your old version and settings in case there any show-stopper bugs for you. |
It also depends how CMUD is installed. For example if CMUD uses "My Documents" then both versions will try access the same packages. You can't have one version access "My Documents" and the other use the CMUD folder. |
|
|
|
|
Fang Xianfu
GURU
Joined: 26 Jan 2004
Posts: 5155
Location: United Kingdom
|
Posted: Sun Nov 11, 2007 5:31 pm
|
For installing public versions, you need to do nothing except run cmudinstall2xx.exe. The installer will do everything for you. One thing you might possibly find useful is uninstalling CMUD and deleting anything left in the folder it was installed to, but you don't need to do that. You don't need to backup your packages because they're kept in My Documents by default.
For beta versions, all the things mentioned above might be useful. It's also important that you keep regular backups, simply because bugs can emerge that totally wreck packages. There was one a while back that corrupted preferences in packages. |
|
|
|
|
Seb
Wizard
Joined: 14 Aug 2004
Posts: 1269
|
Posted: Mon Nov 12, 2007 1:35 am
|
| Rorso wrote: |
| Seb wrote: |
The best idea IMHO (at the moment - might change when the Public version is released) is to install new versions in a different folder, with data saved to that folder too, and then you can copy your packages and other data to the new version installed location, and that way you can easily run whichever version of CMUD you want, and you've still got your old version and settings in case there any show-stopper bugs for you. |
It also depends how CMUD is installed. For example if CMUD uses "My Documents" then both versions will try access the same packages. You can't have one version access "My Documents" and the other use the CMUD folder. |
Yeah, well, I find it all gets pretty confusing if multiple versions of CMUD can access the same settings in My Documents, so I always have the data directory in the install folder. But then I have installed about 30+ versions of CMUD so far.
You do point out a flaw with the installer though - it assumes you are only ever going to have a single version of CMUD installed. Actually I found another flaw when I uninstalled some old CMUD versions some time ago - it removed the shortcuts for the latest version I had installed and not the ones for the version I had just uninstalled. I haven't tried to replicate this with recent versions though, but I expect it hasn't changed. |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Nov 12, 2007 5:35 pm
|
| Quote: |
| it assumes you are only ever going to have a single version of CMUD installed |
That is true because it uses a single Registry setting to determine where the data files are located. So each version of CMUD is going to use that same registry entry. This probably won't change because I really don't want to fill up your registry with a different key for every new version of CMUD (especially since I'm doing weekly versions right now).
As Rorso mentioned, you can use the option that stores the data files into the installation directory (instead of using the My Documents option). This allows you to have multiple versions because now the single registry entry just says "use the program directory" and so it uses whatever directory the CMUD.EXE file is being run from. This is actually how I run multiple versions on my system here.
Of course, the reason this isn't the default and the reason the whole "My Documents/My Games/CMUD" stuff exists in the first place is to make Vista happy. Vista doesn't want data files in the Program Files directory. So the default installation options are set up for the typical Vista user. Advanced users who know what they are doing can easily get around that and select different install options.
Uninstallers typically also make registry entries that keep track of where something is installed. Again, I don't like to clutter the system with a different name for each version. In the Add/Remove programs, I only want CMUD listed once. I don't want each version of CMUD listed separately...a lot of people (including myself) would complain about this spam. So yes, when you uninstall, it will always uninstall whatever the latest version of CMUD is on your system because that's where the Windows registry settings point. Windows just doesn't do a very good job handling multiple versions of software like this. It's no different with most other software (MS Office, etc). In fact, try running multiple versions of most any Microsoft software on your system...you'll get all sorts of problems.
Anyway, not something I'm going to spend much time on. For the vast majority of users, they just wait until the public version, run the CMUDxxxInstall.Exe program to update to the new version, and then they are good to go. It's only Beta Testers that need to worry about anything else. |
|
|
|
|
Seb
Wizard
Joined: 14 Aug 2004
Posts: 1269
|
Posted: Mon Nov 12, 2007 6:03 pm
|
Yeah, not a problem for me - I know what I'm doing and just work around these issues or whatever, but worth pointing out for new beta testers.
|
|
|
|
|
|
|
|
