Notice: Any messages purporting to come from this site telling you that your password has expired, or that you need to verify your details, confirm your email, resolve issues, making threats, or asking for money, are
spam. We do not email users with any such messages. If you have lost your password you can obtain a new one by using the
password reset link.
Due to spam on this forum, all posts now need moderator approval.
Entire forum
➜ SMAUG
➜ SMAUG coding
➜ 1.4a (win.) Race and Class bugs.. possible fix?
|
1.4a (win.) Race and Class bugs.. possible fix?
|
It is now over 60 days since the last post. This thread is closed.
Refresh page
| Posted by
| Gatewaysysop
(14 posts) Bio
|
| Date
| Mon 01 Jul 2002 04:07 AM (UTC) |
| Message
| Greetings again all,
I was tinkering with the pre-compiled windows version of smaug 1.4a (downloaded from this site) and worked around a few bugs. Maybe this info will help others that are't able to or just plain don't want to re-compile (or are just lazy like myself).
FWIW I've had no real problems with new races, either when I create or edit them. When I save them, the <name>.race file does have the extra lines of "wear location <blah blah" at the end, but the race seems to function regardless. I just opened up notepad and deleted that chunk of the race file, leaving the "END" line of course. As I said though, it seemed to work whether or not I went throgh the trouble of removing these extra lines.
On the new classes, I found an interesting bug right 'out of the box.' The Augurer and Paladin classes were not showing up for new players. I'm sure this has been covered but I didn't immediately find a clear fix. Anyway, what I did was add two more classes Null and Null2. I suppose one could make these from within SMAUG but I just created copies of warrior.class and adjusted the second line of Null.class and Null2.class to read "class 9" and "class 10" respectively. Then I added these two manually to class.lst, (in the 9 and 10 positions) rebooted the mud and banned both null classes permanently. Rebooted again and logged in as NEW and voila! All the classes now show up.
I originally tried this with only one "null" class, but Paladins (#8) still would not show up unless I added a second null class. I tried this fix out further by adding a new class, setting it to number 9 and making the null classes #'s 10 and 11. As long as you put everything in the right order in class.lst, it appears to work fine.
I'm sure someone has probably mentioned some of this before, but like I said it wasn't immediately apparent to me. For those not wanting or able to re-compile, this seems like a not so difficult work around IMHO.
Hope this helps someone out. | | Top |
|
| Posted by
| Vaelarin
USA (8 posts) Bio
|
| Date
| Reply #1 on Tue 02 Jul 2002 04:57 PM (UTC) |
| Message
| There's a line of code in the nanny() function in comm.c - around line 1800, that affects this. I think it was added on purpose because the two classes augurer and paladin were not considered complete. Here's the code:
write_to_buffer( d, "\n\rSelect a class, or type help [class] to learn more about that class.\n\r[", 0 );
buf[0] = '\0';
/*
* Take this out SHADDAI
*/
for ( iClass = 0; iClass < MAX_PC_CLASS-2; iClass++ )
The last line here where it says MAX_PC_CLASS-2 change this to MAX_PC_CLASS-0. As it is, the code tells the menu to show all the classes except the last two. Change it to zero and it will show/make available all of them. I've been running it this way for a while with no problems.
Hope that helps. | | Top |
|
The dates and times for posts above are shown in Universal Co-ordinated Time (UTC).
To show them in your local time you can join the forum, and then set the 'time correction' field in your profile to the number of hours difference between your location and UTC time.
11,341 views.
It is now over 60 days since the last post. This thread is closed.
Refresh page
![[Go to top]](/images/gototop.gif)
top