lynx

I found it hard to believe anyone could properly produce a mod that G3 wouldn't be willing to host.

Surely this would break IDS targetting ...

I've added it to GemRB with 3 lines of code, so it should be relatively easy to hack in through dll injection etc. as well.

This is already like this in the original, so it should also go to bg2fixpack.

Does the gui mod modify the files as well? Perhaps you need to install widescreen first.

Not yet is a better way to put it. As of the next release only the volcano time-reversal scripting is in the way, I didn't find any other critical path problems. But it's definitely not something to postpone playing for.

It's only easily moddable in gemrb, as the original had them hardcoded.

4. Use the sum of the two speeds. No data changes needed, but the bug gets fixed and easy modding is possible.

Goddard/Jon Irenicus did some work on the data side of things, but that's about it. It's not just about replacing the graphics, but a lot of the structures need their offsets scaled, coordinates used in scripts and dialogs the same and maybe more. It's mostly a data mod if you pick a fixed upscaling factor; engine changes could just speed up some things, provide shortcuts. And there are probably some things that still need to be unhardcoded, but other than that, I imagine it could work without touching the engine. A lot of work either way, but I'm sure there'll be enough interest and volunteers eventually.

I don't see any value in it, to be honest. Enemies won't switch targets; a downed pc might even attract more attention due to being easier to hit, so the benefits would be decreased. But you die by failing any save anyway (much unlike 5E), so the small unpredictable window of time this buys is small.

I guess we have different expectations of DestroySelf and I treated it as if it also did something like UnmakeGlobal.

Ah, true, there is a tiny race condition of sorts. If the Xzar block fired the same tick you wanted your mod block(s) to fire, it wouldn't work. Only for that one tick, so very unlikely, but yeah, better safe than sorry.

It's the last block, so a Continue wouldn't do anything.

Well yeah, it's a community project, so any help is welcome. File format stuff is in these files: https://github.com/Gibberlings3/iesdp/tree/master/file_formats/ie_formats

A readme template is also available on G3's github, while the mod should already be nice and tidy if you used the RealMod mod template.

Ah, interesting, I thought it was a separate engine, a light lift-up. It's odd that they didn't just use the extra death var scopes from iwd. As for the bit, I then can't say if that helps. It's what we need to do for the original pst in gemrb when compared to other games, but this mess was tested with something else — I think the Ignus pedestal.

KAPUTZ is fine and in fact only usable in pst. I doubt that was removed in pstee, as there are at least 10 other users. pst has partly different flag bits for area animations and that's definitely true for bit 1 (blend, when counting from 0) — 0x0100 should be set instead.

+7 of the creature's.

PersonalSpaceDistance is the Range reduced by the creatures' circle sizes.

Good idea, added. And yeah, welcome back.

Thanks for the note, I've updated the IESDP descriptions to be a bit more telling.

I have no clue if LeaveAreaLUAPanic does anything practically useful. Maybe for multiplayer? In GemRB we've had a longstanding comment about it and deliberately changed it to do almost nothing (using parchment for eventual load screen image). You mention Brage and that's one reason for it, because in his script the two calls are not together.

No, that's not so easy.

You can compile it yourself, it's not that complicated (see its github repository). A distro upgrade would also fix it, but of course that requires plenty more work.

He has a thac0 of 20, no proficiencies (a +2 penalty — I know in iwd2 only non-pcs are penalized, but perhaps it's true in other games as well), no extra strength. So a 16 missing someone with ac 5 (as in the screenshot) is in line with our code, since it's only 21, while you need a 23. And I can't believe a claim of a missed critical hit.