@Pygmy, @FDR4PREZ, @Sitra Achara. I'm really sorry about all the system problems, and I wish I could help more on that end but it's honestly above my pay-grade. Once the game gets running, I can really be of help with problems you might encounter. If the frustration continues with getting it running, I would suggest trying it on an older computer. I know that's a lame answer, but it's the best I can do right now. As Sitra Achara mentioned, I pulled my hair out for a week a few years ago trying to get ToEE running on my brand new computer, and to this day I still can't get it to run full-screen. My only solution was to start it in window mode. Strangely, my Dad's new computer runs toee.exe perfectly full-screen, and it's very close to the same as mine (Lenovo, W11, 64-bit, lots of RAM). But mine has all the fancy"gaming-computer" stuff, with NVIDIA control panel and all that. I'm guessing that may what's causing interference somewhere deep behind the scenes.
It's hard to test for an operating system you don't have. Mine is an old Windows 10 PC, runs it fine (64 bit at that). Loving the detail, Marc - I don't want to give away anything but WOW! The sound effects, the additional items, so much happening!
I've installed it in the same folder with everything else, The Keep, ToEE-NC, Original ToEE. I also have Temple+. Running Windows 10 64bit. Got to level 4 with a party of 6. NO PROBLEMS so far, everything runs smoothly . Huge thank you , Marc . The mod is just amazing
Have been running Paladin's Cove without incident on my laptop (apart from not having any silver weapons - have I gone off course for 1st level?)
Yes, no worries. I stated in my first post that i have an older laptop and i will give that a try. It has Win10 on it, and I just remembered that I have a really older one with Win7 on it. So I have options. If you search on the GOG forum we can see many similar unresolved complaints. About the only solution mentioned there is install Temple+ Window Mode gets me to the opening vignette and then it crashes. This is nothing against your module and all about an older game versus a newer OS, and I am not upset at all. I'll post again once i am able to try on my older laptops.
@Shiningted, @Zalmoxes, @Pygmy, Very nice to hear you at least got off the ground with no messy bugs early on.
It's too much for me to think about right now. The best I could do at the moment would be to sneak in some of the more impactful (and/or simpler) changes that are not specific to any particular mod or adventure. I'm thinking things like getting the cleric spells alphabetized, being able to access faction numbers internally, implementing changes that fix annoying bugs that can be fixed with a direct change to temple.dll itself. Putting the full Temple+ wrap-around is an ambitious project. First I need get Paladin's Cove play-tested and stable for a long time. And that just got started last week. After that, I need to actually finish the whole thing (it's only about 70% done), and then test and stabilize that. Then I would have to take a very time-consuming deep-dive into how Temple+ works. Or, alternatively, someone who knows how T+ works would have to take a deep-dive into how Paladin's Cove works. Then again, maybe it's easier than I'm making it out to be. Even if it is, I need to finish P.C. by itself first, before anything else.
Loving Paladin's cove Marc! The detail is so amazing and I love it. Just for anyone wondering, newer PC windows 11 here, i downloaded it into the same folder as Temple+, C08NC and KoTB and i activated it through the front end with no issues and run it through the front end and hitting play no issues with load up (at least so far) 2 days playing now.
Could well be. Those examples you listed above don't require meddling with any files, they're engine level already. To get an idea, first thing to do is identify which files Temple+ is overriding that you have also modified. Temple+ already has separate file changes for "infrastructure" and "adventure specific" as best as it can, so it should make things easier (this is not 100% clean however).
Hi again. My first strange thing to report . Whilst in wilderness, I am attacked by two Brown Bears. My Druid summons a Black Bear which then attacked the Druid that summoned it?!? Maybe he was helping his kin ? And a minor one , one dialog line says something like "I now" when clearly was meant "I know" ( soreee , I forgot which and where... )
Great job @marc1967, I played through the first quest and had no issues. Everything about the module has been done very well so far!
As soon as I get a chance I am going to take a look and see what the level of difficulty is going to be for getting Temple+ and Paladin's Cove to work together. I imagine we would distribute some extra files with Temple+ to get them to work together like we do for KOTB.
Thanks Doug. When I said somewhere "it will happen soon" I was hoping the Temple+ folks would step up themselves - mainly because they have in the past, not because there is any moral compulsion on them. @Endarire - I don't have to say it, do I? Just consider it said. Unless you want me to say it publically.
Great find, Zalmoxes! That is a bug for sure. And what you said jokingly about the bear helping his kin is actually what is happening. I put in place a "comradery" code between similar creatures, akin to a faction number, but not related to the faction number itself. So if you are in combat with a certain creatures (like a brown bear), and one of his "friends" is a recruit in your party (your summoned black bear), that recruit will leave the party and fight with his "friend". This is what happened to you with the bears. But it was not NOT meant for that particular case. It was only intended for townsfolk mostly, and certainly NOT for summoned creatures you may have brought into the party. I have fixed the problem, which was a simple to change to about 15 protos in protos.tab. If you leave it the way things are, it should only be a problem if you summon similar type creatures against each other in random encounters. (bears vs. bears, snakes vs. snakes, wolves vs. wolves, etc.) But if you want the fix, I have updated protos.tab, which you can download if you want. Just put it into your rules folder, and the problem will be fixed. It's a small enough of a change that it shouldn't upset any saved games you have. https://drive.google.com/file/d/1RmhoGyIzp5_d4LyFL-CFd6AtVSh8FLqR/view?usp=drive_link