Volunteers needed - beta testing next Temple+ release

No mods in regards to Turn Undead unfortunately. It would be easier though...

 

No, I mean *any* mods - that includes your module(s), sagenlicht stuff etc. If you recall there was a 1000 condition limit which sagenlicht recently broke in his branch, and I imagine you've added quite a few yourself so maybe you ran into the same issue.

 

Good catch @Sitra Achara !!

Apparently Turn Undead condition hit number 1000! That's not good. Will it work with more conditions limit?

Update: Looks like it works well.

Code:

        static int(__cdecl* orgHashtableInit)(CondHashSystem* hashtable, uint32_t capacity) = replaceFunction<int(__cdecl)(CondHashSystem* hashtable, uint32_t capacity)>(0x101EB9F0, [](CondHashSystem* hashtable, uint32_t capacity) {
            if (capacity == 1000) capacity = 2000;
            return orgHashtableInit(hashtable, capacity);
        });

I'm using KOTS module and 121 new conditions, mostly for monsters.

Update 2: In total 1024 modifiers:
len(debug.dump_conds())
1024

 

I've already hooked that elsewhere, so no duplicates please. I haven't actually changed the capacity for next release though.

 

Yes, sure. I just hooked for my development.

Capacity won't change anything IMHO. Either I will reduce unused modifiers in my module, or suppress ones created for Complete Arcane spells.

In any case, for ToEE increase of capacity will not have effect.

 

Eh? What makes you say that?

 

It's easy - around 900 are used now with Sagenliht's modifiers. Changing capacity will not increase modifiers, they still are going to be ~900 in number.

 

Ah I thought you meant sthg else. Anyway I probably will increase the capacity, just playing it safe for next version.

 

Small update:

The main thing holding back the release was stability concerns. I'd gotten reports of seemingly random crashes, which I couldn't trace to the root cause.

The trouble is that since these are relatively infrequent, it's hard to reproduce and diagnose - I just don't have the time to play the game for tens hours until such a crash occurs.

So I've been working on an automated playtester that goes through some section of the game over and over, hoping to be able to reliably reproduce the crash error. I've so far got it to basically play the tutorial dungeon in a loop. Which is pretty cool, but unfortunately it doesn't trigger any crash yet (or fortunately, depends on how you look at it).

The current plan is to keep expanding this infrastructure, with several goals in mind:
1. Generalize its UI handling so it handles any resolution, and windowed mode
2. (related to above) Make it deployable so more users can test it concurrently
3. Set it up as a test bench for new features/spells/classes/etc - would probably save me many hotfix releases
4. Eventually, perhaps players won't be required at all

 

I've released an interim version in place of the originally planned 1.0.85. It's mainly a fixes-only patch that addresses most of the major issues that cropped up in the last year and a half. See changelog here:

https://github.com/GrognardsFromHell/TemplePlus/wiki/Changelog#v1085-released-2022-03-20


The rest of the planned update is postponed. Hopefully no more than 2-3 months out...

 

Little update:
I've finally got me a laptop - dual booted wife's macbook, no less (why didn't I think of that sooner??)
Means I can get about an extra 5 hours a week for Templeplus, which is a lot for me these days

Now I have 2 months to do this, which is until baby #3 is out

 

Congrats! It doesn't get easier after two, but it's not as hard as the transition from one to two (and much less than the transition from zero to one!).

 

Update:
Getting a laptop really put me back on track. Besides the additional hours, it helps with the headspace management. Much easier to pick it up in the evening that way.

Right now I have the auto player crudely going through the new game motions: New game, select PCs at the party pool, get through the shopmap and some of the early Hommlet motions (picking up Elmo and doing the Furnok gambling bit for lodging quest).
This might not sound like much, but most of it was about laying the infrastructure: figuring out where the UI elements are programatically, moving amd clicking the mouse (now works in windowed mode too and independently of resolution), and setting up convenient dialogue handlers.

The next step is to generalize these basic building blocks to more complex higher level actions, so the auto playtester can handle things like simple combat and getting around with less pre-scripting / manual fiddling.
By next week or so I expect it to capable of grinding random encounters in a loop with simple melee combat, at least.

 

Why is there a ToEE bot?