Unintended Consequences

Yeah, so it all started as an innocuous attempt to do some good.

What could go wrong, I thought?




I mean, the Dire bear worked alright, no?...




Alas, dealing with demons is never a good idea.






We got off to a rocky start, but eventually we found some common goals





Next time, I guess I'll settle for something more mundane...​

For those who always wanted to teach their pet demon to fetch, head on over to 2EF14C inside Temple.DLL, where the array of proto definitions for animal companions is If you want to play it fair, you'll also adjust the Minimum Level Requirement array which starts at 2EF174 (it starts off with a bunch of zeros, but it's there, trust me! Each value takes up 4 bytes, or in practice, a value followed by 3 pairs of zeros).

​

Here are the values I've used in my little experiment: (red highlight for the Dire Bear replacing the Chicken, black highlight for the start of the arrays)

​

Enjoy!

Edit: to replace the Dire Rat with Dire Bear (at level 13) make the following edits:

Code:

Offset 0x2EF158  change E8 36  to AA 38
Offset 0x2EF184  change 00 to 0D

 

I love doing that too

but I did not Edit the temple.dll to do that

all I did was edit the meshes.mes file I think

change the monster file path in meshes.mes


way more easy

 

Holy crap! Does this mean that characters who have at least 13 levels in the druid class will be able to have dire bear animal companions (in accordance with D&D 3.5) (http://www.d20srd.org/srd/classes/druid.htm#theDruidsAnimalCompanion) in a future version of the Circle of Eight modpack?

 

Probably. The only issue is that it has to come at the expense of another animal, because unfortunately it's a fixed length table.

I'm thinking no one will miss the Dire Rat, but I could be wrong. The chicken is pretty useless too, but it was obviously included for the lulz so I'd prefer to keep it.

What do you think?

 

My ASM Wizardry is still weak, I can barely cast Mordenkainen's Faithful JNZ :rant:

The real issue is that the table has no padding between it and the next bunch of data, so I'd be overwriting something else if I extended it.

One day, when I actually know what I'm doing, I'll externalize that list entirely. Until then, swapping the Dire Bear for a pre-existing AC should be good enough. We've committed worse crimes in the name of modding already

 

I think it's the right way to go since the dire rat is really a poor choice anyway...

I am looking forward to put my hands on that modified temple.dll :dance:

 

Looks like the above discussion is now irrelevant

​

 

Oh my... you did you do it?

 

Shouldn't be a problem - they're defined right in front of the AC table. I'll throw in the wildshape while I'm at it, because it's right after that!