lynx

While bad, since they could've just shipped it like all the other libraries, you just have to install that specific old OpenSSL and it then runs. Not trivial, but doable.

Graion: cool, I'm happy on behalf of others. But a minor Android API bump is likely a trivial patch and rebuild away, not something substantial. Could make modding harder though, if the previous versions were still on the API that allowed external storage.

It's exactly the same, except I don't know if all the dependencies are available via vcpkg.

Tooling is still regularly updated and perhaps you saw that recently a weidu GUI was released.

Beamdog got acquired and downsized, so the chances of further updates are even slimmer.

You can't, you have to build it yourself.

I don't know of any build bot services that provide images with Windows RT nor would it be a sensible use of ours and theirs resources for something so rarely used.

It makes sense though and the manuals are all sorts of wrong. There's a bit in the ITM structure that dictates this (there's a bg2 sling that explicitly adds strength). Perhaps it's just on by default in iwd.

Audacity is as old as bg2, Gimp is from the mid nineties and both have been team projects almost from the start. It's easiest to fix by just not mentioning people, since besides DLTCEP and maybe SK, all the rest have multiple authors.

Hey,

noticed two things after reading the announcement.

1. It's not clear whether the kit from S&F is included or if the mod must be installed first.

2. The attribution section of the readme is all sorts of off. Almost all of the projects/tools listed have teams behind them and Sourceforge is not one of them (just a host like G3).

suy, nothing is stopping you from fixing the rare (I imagine) mods with multiline descriptions. It seems odd to advocate avoiding global workarounds while the bad state persists.

Location is the position of the container. Think of it as the centroid, though it doesn't have to be. In fact, it can be outside the bounding box.

Vertex coordinates are normal coordinates, yes.

"First vertex index" I never had to set before. It should be the index into the areas vertex region of the format, where all of them are bunched up (that's why you can get oddly high numbers). https://gibberlings3.github.io/iesdp/file_formats/ie_formats/are_v1.htm

Bounding box aliases look fine as well.

The few mods using multiline descriptions just need to be fixed to use a single line description (ok, maybe escaping would work, but it's ugly).

Nice, congratulations on the release!

Updated and can confirm. Mask of King Strohm guard scripting and BG1RE's Branwen's girdle of gender banter rely on the behaviour.

I was testing with weidu directly, I don't have any mods to install.

The three bugs mentioned in this thread. Not that I think they are EE-specific (except the UI one).

I doubt running the windows weidu binary changes anything, it's more likely weidu does runtime checks (too tired to check though).

GemRB doesn't really care about case nor did I understand what you wanted to say.

My pristine bg2ee install is clearly in a case-sensitive place (touch a; touch A # creates two files, not one) and weidu is able to extract files from biffs just fine. But even if drastic measures as mentioned are eventually needed, that doesn't detract from that being terrible. Or that consistent file naming is a good idea.

You don't "need the case insensitive directory anyway", but let's not copy the discussion from the other thread.

I can see no reference in IESDP to this action from now to before iwdee was released. So HUH? But I added it.

The originals did have weather, most commonly snow. If you're testing, it's easiest to trigger transitions via the Weather action.

Using a different partition or toggling settings on an existing one is a tall order for a regular user, plus it could have systemic side effects. Silly suggestion just because EEs have 2 isolated bugs that can be handled as before in mods that need it.

On 10/4/2023 at 5:11 AM, subtledoctor said:

I tend to just start from an existing projectile that is most like what I want, and then make adjustments guided by the IESDP’s .PRO file format information. 

Not really, most are documented as already mentioned.

It was hardcoded, so no. I can think of approximations via scripting, but nothing bulletproof.

Was any of this area and other in-game art made completely by you, not by remixing existing assets?

This was likely lost in the refactoring into proper data, where I think action.ids was used as the lookup table. So it should be easy to check if anything else was known, but also thus omitted.

It hasn't been ported to python3 yet, but I didn't know py2 didn't work on newer windows any more. Either way ielister should work on windows still.

@AL|EN lowercasing is still good, since it's less likely the mod author will make a consistency mistake, it just doesn't fix everything.

someone just hit it via imprisonment too.