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
➜ Adding new spell damage types
|
Adding new spell damage types
|
It is now over 60 days since the last post. This thread is closed.
Refresh page
| Posted by
| Checksix
(1 post) Bio
|
| Date
| Mon 16 Jan 2017 06:19 PM (UTC) |
| Message
| I'm curious about how to add new spell damage/resist/suscept types, without messing up the existing system. I'm assuming it has something to do with this piece of code:
#define SPELL_DAMAGE(skill) ( ((skill)->info ) & 7 )
#define SPELL_ACTION(skill) ( ((skill)->info >> 3) & 7 )
Because simply adding an entry to spell_dam_types seems to mess a lot of things up -- namely, sset <spell> damtype sonic changes the acttype, etc.
Am I looking at having to rewrite the way spell damage is saved/looked up (changing them to strings in the code or int values in an array) in order to add ~5 damtypes without messing up a lot of other things due to the BV system?
Running mostly stock SmaugFUSS1.9.
Thanks guys,
Checksix | | Top |
|
| Posted by
| Nick Gammon
Australia (23,166 posts) Bio
Forum Administrator |
| Date
| Reply #1 on Wed 18 Jan 2017 12:50 AM (UTC) |
| Message
| | I think you need to show the code you added, which didn't work. The defines on their own don't prove much. |
- Nick Gammon
www.gammon.com.au, www.mushclient.com | | 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,225 views.
It is now over 60 days since the last post. This thread is closed.
Refresh page
![[Go to top]](/images/gototop.gif)
top