New Temple+ Available

Is there anything that can be done about the particle effects for Ghoul Touch? It the first time in all these years that I used the spell, which can be effective for coup de grace. Unfortunately, the particle effects occur when cast, and stay on the caster rather than the paralyzed target. The particle effect goes away during sleep.

 

Here are the comparison videos for lines vs. clusters.





Also, here's a bonus video for observant people.

 

Also, yeah, the ghoul touch particles should be fixable. I'm pretty sure they're just mis-designed, and the particles for the stench cloud on the target get applied to the caster while they're holding charge. That's just wrong. The caster particles should just be a glowing hand or something.

 

Oh, those videos really seal the deal with me wanting the new moving cluster of images.

 

Great! Know that it isn't only when holding the charge, it is also happens after hitting the target. Saving or not saving is also irrelevant

 

Hey wait a minute, I recognize that Wizard!

 

I just noticed something with Color Spray. It is using pre-3.5 rules limiting its effects to 1d6 creatures. This limitation was removed in 3.5 as shown in the srd. My simple, inelegant solution was to mod the py in my overrides to 10d6. Even if Widened, it should be enough!

Here's a small Temple+ question about the different override folders. I know that root override is supreme, but I am wondering how to utilize the module ones - especially for Co8 8.1 NC. I know there was a lot of talk about clearing the root override folder and using the module override folder, but what can we do for Co8 specific modded files? Can I just create one in the EoEE module foler?

Has the fix for Widening Cone-shaped spells been released yet?

 

Wow. I think that's the first time I've ever seen an OnBeginSpellCast that actually does something.

I don't think there's anything special (right now) about the override subdirectories. Like, I don't know of a way to make one of the directories only load when some module is selected for the game. But, what it would allow is for you to put all the stuff that's only relevant to one module into a separate subdirectory, and then manually disable it (by deleting the mod_specs.json file) when you're not playing that module. And you can see on the title screen which subdirectories are being used, to check that it's appropriate for the module you're playing.

And no, I don't think the widen fix has been released yet. It's merged into the main branch, so you could try running a build from that if you wanted to do early beta testing. I'm not sure if nightly releases are still being packaged, though. It looks to me like the build skips that part.

 

Do you mean that the files that I put into the SGoS module override folder must be removed / disabled if I play another module or Co8? I thought the engine ignores the module folders when the module isn't activated.

 

I was just looking at installing Paladin's Cove to Temple+ despite the creator's wish to the contrary. It seems like a lot of others did the same. Please help me understand why zmod has 2 folders in the module folder - the Temple+ Setup only sees the one that isn't core? ToEE only has one folder (module). I extracted everything in the Paladin Cove data folder to a module folder called PaladinCove, but the Setup does not recognize it. I saw that there is also a ToEE inside the .tfm which I did not install since it seems to have the same files. I'm very curious how Temple Plus setup is different from Co8 FrontEnd. Thank you!