lynx

That's good as well. You can then run: weidu --change-log path\to\aminota.bcs That will tell you where the file is from. Well, unless you already know it's from NeJ?

Thanks, true and added.

Ok, let's find out where that file is from, so we can check if it's supposed to be empty or not. I don't get any hits on g3 or shs github nor the original games, so you'll have to do the searching. You can try to do a regular file search in your game install for aminota.baf (not bcs).

Some mod file is a bit corrupt. Check out aminota.bcs in NearInfinity and please send it over as well.

I'd say thebigg's approach to adding scripting support for party members after the 6th to mods, while maintaining compatibility with engines that can't handle it (ie. most) and without modifying weidu itself.

The problem you're having is realizing that the perception of what you say is not at all dependent on what you think. That doesn't matter at all — you could believe in green zebras and monkeys in dresses would still trigger bad cultural memories. And races of course exist; it's a taxonomical category like any other. Whether it makes sense to try to describe human differences that way is another, contested, issue.

I've added an action to set 5 tokens for these, if anyone ever wants to use it as a gemrb-only feature: https://github.com/gemrb/gemrb/commit/e0d455cdbbb74c59e993c522f5d8abf5519a4394

Obviously the size is not 112 if it's matching that condition. But why pontificate, when you can measure it? Also, you can see that SPLv1 has a minimum size of 114: https://gibberlings3.github.io/iesdp/file_formats/ie_formats/spl_v1.htm

I'm pretty sure the only option you have is adding a new trigger to eeex or gemrb. What did you want to achieve, just to be able to print their names (=use a token)?

It's stored in the GAM file, so it could be read by weidu. But that's static, so the practical answer is: not reliably.

1. You can't by default, you'd have to use an external program that does support pcre-like regexes. It's more of a limit of the ocaml stdlib than anything else. 2. You suggested a workaround yourself — you can have an escaping function mangle the string first.

I can reproduce that, let's see what's going on... I can reproduce this even with my standard config, so there's been a recent regression. It's obvious from the log it's trying to load a bam cursor instead of the png ones. Apply this fix, I won't be able to push it for some time: diff --git a/gemrb/core/Interface.cpp b/gemrb/core/Interface.cpp index 975491e10..3f5ab63cd 100644 --- a/gemrb/core/Interface.cpp +++ b/gemrb/core/Interface.cpp @@ -685,7 +685,7 @@ int Interface::LoadSprites() // same layout as in the originals, with odd indices having the pressed cursor image std::string fileName; while (CursorCount < 99) { - fileName = fmt::format("{}{}", MainCursorsImage, CursorCount); + fileName = fmt::format("{}{:02}", MainCursorsImage, CursorCount); ResourceHolder<ImageMgr> im = GetResourceHolder<ImageMgr>(fileName.c_str(), true); if (!im) break; Cursors.push_back(im->GetSprite2D());

Didn't bg2ee automatically gain the iwd/pst ini spawn feature? That's more flexible and more easily tied to scripting than bothering with the ARE spawn entries: https://gibberlings3.github.io/iesdp/file_formats/ie_formats/ini_spawn.htm

I'd ask one of the modders that use it, I don't think it's documented anywhere. @Bubb should know its limits, since he's the developer behind EEEx.

They're handled (hardcoded) by the engine. Here's the list of triggers one can use: https://gibberlings3.github.io/iesdp/scripting/triggers/bgeetriggers.htm Some of them set objects/variables you can then use in actions, but none are mouse related.

This is usually done with IE scripts (BCS), with the block most commonly added to dplayer*.bcs to not pollute the global script (baldur.bcs). Example: IF HotKey(K) THEN RESPONSE #100 DisplayString(Player1,6150) END - no - no, yes - no Can't speak about lua hacks though.

There's a bot linking the two, so everyone is happy.

Feel free to join us on IRC/Discord to talk things through — starts are always daunting.

Thanks, added.

You caught us at a bit unstable time, as there are several regressions and bold changes, but that also means testing is even more welcome (just check the tracker before reporting). Eg. you'll probably see missing text in the demo (#1508). As far as playtesting efficiency, I'm not sure what you mean, but any game is game.

The demo needs all these optional plugins, so install development files and rebuild.

cat > demo.cfg <<KUKU GameType=demo GamePath=../demo GemRBPath=../gemrb PluginsPath=./gemrb/plugins/ Width=800 Height=600 KUKU You can generate a minimal config with that and then pass demo.cfg to gemrb.

I see you tried latest git. It works for me now, but there have been hundreds of changes in the past few days, so I suggest you first update to the latest code. At minimum you'll have to bump the resolution. I also see a bug in one way to run it, investigating.

You can restore the single space if the warnings bother you.

Yeah, whatever reformatter the mod used broke the signature by aligning the version with the first column. No biggie, just not standard.