lynx

I'm pretty sure it does work. What doesn't should be identified and fixed. The only engine hack I remember from ia or 1pp was for the deva component.

It wouldn't be that easy. Now we use the new profs if bg2 is detected and the old ones otherwise. Most of the code is in LUProf*.py. It wouldn't be technically difficult to change, there's just several places where it expects the current behaviour. How does TA's version work? It shows both prof versions at once?

No, it would have to be reimplemented (some of the changes are easy though), since it relies on the new tobex. btw, check out ctrl-w for loot.

Way too much stuff in one thread. As for the console spam, it's hard to say; I don't see it, so it could be an openal problem on windows or some other thing. It could potentially explain some sound issues. Some of the faintness is likely from the range of the speaker from the center of the viewport. I don't know if our model of the audio is similar enough (damping range, speed etc.) to the original. You can also tweak relative sound volume by modding sndchann.2da from the original game.

It's not too clear which parts refer to gemrb, but I tried entering and leaving the Candlekeep tavern 5 times in a row and the ambiet music switched as expected every time. Also, 0.9.0 is already one release behind, so better grab the latest.

Still, it would be possible to add them to cloaks, but it would only display on the inventory paperdoll.

It doesn't. Drawing them. None.

ninja'd by 4 hours? There's ADD_PROJECTILE for new projectiles, but projectiles in general are quite complicated beasts.

The GemRB team announces the availability of GemRB 0.9.1! GemRB is a portable open-source implementation of Bioware’s Infinity Engine. The new release features loads of improvements in core game systems, making Icewind Dale II almost completable, but also in the rest of the engine. Among other things this means further improved speed, better unicode support and deprecation of Python 2 support. As usual the release also comes with many smaller features, bug fixes, polishing and code cleanups. More in the full release announcement: https://gemrb.org/2022/08/29/gemrb-0-9-1-released.html

The GemRB team is proud to announce a new release. Check out the details here: https://gemrb.org/2022/08/29/gemrb-0-9-1-released.html

Yeah, why would you even try using weidu with wine when it has a native version?

You have beer golems in Pathfinder; in the computer games if you're connected with the god of festivities.

Seemed obvious to me, but I've now added a note to op 39 on IESDP — thanks! https://gibberlings3.github.io/iesdp/opcodes/bgee.htm#op39 (just have to fix the ids reference) The duration stuff for stunning was more interesting, since we just used a single round in GemRB.

https://gibberlings3.github.io/iesdp/scripting/actions/bgeeactions.htm#373

Remove on entry, readd on exit.

You know, unless there's copyright issues or the mod does something unspeakable like overwriting files, I think you'd be welcome to host here.

Let's not turn this thread into another duck one.

It's definitely possible. I don't know about BAMv2, but in v1 the color of the first pixel in the palette defined the tranparency (usually pure green).

Why makes you think it's not enabled?

Another thing to note, the shadow does respawn, but it respawns weaker. It's the only different shadow, not a lesser one like the rest. After the first respawn, all are the same. And there should be two respawning, shadow1 and lshadow1. Like I said before, I think the case for leaving it be is stronger than for enabling. Besides what was already said, just looking at the ini gives me an impression that the timeline was like this: all spawns are shadow*, then they disabled them by gimping the spawn groups, then they added shadow1.

Just noting that the pst one appears in two blocks of the ini, not just one. It's the only ini with this particular problem. I've now also checked if anyone misspelt the colon or the orientation, but no hits.

What are the filenames? You can derive the id from that quite easily.

Ah, that's right, even the description has that typo: venomous. Can gas be venomous? Shouldn't it be poisonous, since you ingest it?

Here's a few more ideas: Searing cloud, Miasma, Noxious doom.

When signing up everyone had to agree with some basic terms, including, to quote directly: This is probably the base set from Invision, not what G3 adds on top (if anything). Still, it's clear a post like that ticks more than one of those adjectives and has no place in this space. You're getting off easy, but please stop wasting everyone's time.