lynx

What's with that html dump?

Thanks for double-checking and digging in — I just tested via the console. Now the first patch is applied, I finished the second (prevent casting, reenable both if status is restored), and GUIREC shows it.

Fallen stuff: seems it was hardcoded and the script actions are used only in the hell trials. Fixed now. TODO hiding visual: can reproduce, there's also pulsating now. RETEST needed voiced lines will get cut off: sounds like a regression haerdalis: can confirm, at least on a modded install — the whole troupe is left behind polymorph paperdoll: the palette issue is known + I suspect we show the doll for more forms than the original Disintegrate spell - leaves bodies: this is like in the original, it depends on the gore setting NMI bounty hunter: can you elaborate? Sudden day/night change: what do you mean? worldmap stutter when scrolling: can't reproduce, how are you scrolling? spell visuals (projectiles): this was a hardcoded mess, so that's why, but unless you provide more precise info, there's not much we can do. Eg. cloudkill/web animates too fast. Sarevok's shadow: how red? Everything is redder in dreams. NEEDS RESEARCH dire charm: known problem; it's not clear what the originals did — I suspect they just temporarily assigned wtasight or somesuch script. Saradush soldier NPCs make loud grunts: is it the hardcoded loudness problem, damping, cutoff? Firebea®d in the Candlekeep Inn: what happens in the original? NON-ISSUE Re stunning icon/effect: likely a data bug, where only some of the effects allow for a save and the ordering is not good. Kinderek weapons: the mod author didn't fully set up his character when entering the area you need to wait few second for NPCs to load: mod/megamod issue; if anyone lags, it's because their appearance is scripted and if you megamod, it can MODS Of the listed, I only tried Xan and what you reported could easily be by design in the mod. Please open new topics for new stuff, so it's easier to work through.

Thanks for digging in, so it turns out to indeed be a mod bug. pro5 seems to be the current maintainer, so zelazko, please bring it up to them — it's hosted on BWL. I find this kind of stuff highly annoying, so big thanks! Currently in the middle of fixing the remaining gcc8 warnings on master.

Just an observation. This is more about making the component choices actually get installed. If the interaction with weidu was similar to interactive, it would only be about mod install order and component order would be automatically taken care of. So maybe there are other ways to communicate them.

Looks more likely that your machine has been infected, hacked, altered.

Additionally, some of the most useful cheats are listed here, with shorthand versions (always affecting the selected character): https://github.com/gemrb/gemrb/blob/master/gemrb/GUIScripts/include.py Eg. that CreateItem could also be abbreviated as ci("misc4g") .

How are you making the pre-release?

khelban: that's only the default for LIBDIR, but I added the extra option anyway. Not yet pushed. as for gcc 8.2, does this work for critters instead? http://sprunge.us/Xmn3iU?diff

on leaving: make sure you don't exit the area before they manage to escape.

Ok, thanks. Updated iesdp.

Do you know what the second parameter is for? All users have it set to 1. All I can think of is perhaps what the variables are set to.

He set it in the area file. I don't think bg2 supports snow though.

These are engine hacks, so it would require a lot of work to reimplement them atop EE. And then again for everytime the binary changes.

the missing descriptions are a mod problem. My guess would be you installed an EE-only or a badly ported mod, but that's just speculation.

Err, well that would be something completely else, just like khelban12 said. You described lag as everyone understands it, so this doesn't fit. I just blame windows. The speed adjustments in that config are also just for low end machines and most of these degradations have not been reimplemented in gemrb. But yes, walking speed externalisation is a live todo item, but of course it requires programming and I believe you don't have a development setup.

You asked for something completely different in that thread. But let's leave it at that, there is no point in continuing the subthread. Interactivity is a thing of hot contention in package management.

1 *is* technically possible, that's what my initial mention of Expect was about. Good point about answer preservation for READLN, but I see that as a missing weidu feature, not something unsurmountable or something the mod author should save manually. Simple choice problems are easily solved, but we're talking about the hard one — arbitrary input.

You ignored the verification problem. Or are you suggesting user choice should be ignored in case of mistakes?

Not if mod install tool have a nice "Mod Config" button which will open such ini for the player and can save edits. Not everyone can use your install tool ... and different people might use different install tools. Mods are designed for the game, not for the install tool. Replace 'can' with 'willing to' All of my proposed solution (even 3 with custom ini/json) are not dependent from the install tool type and can be implemented via any install tool. Solution 1 and 2 already exist. For solution 2, you can even display additional info during console installation: "The config.ini file not detected, read config-default.ini to change default configuration" - player will be aware how to use ini files even if he won't use any install tool at all. It's all about removing ACTION_READLN by any means necessary, not to exclusively support preferred install tool. That's a useless argument if such tools don't exist. Make my life worse and claim someone can make it better? That's still a regression. What subtledoctor was probably aiming at is that this (nonexisting?) tool likely doesn't work on non-windows systems (mobile hw, linux, macs, bsds ...). I mentioned verification for the free-form entry use case, of course it's not much of a problem when you only have a discreet list of options. The install will have to be aborted and the tool probably can't know that beforehand, as the code needs to be executed first (Halting problem).

Well, having to use inis is a pain for users, though of course it hampers automation. Expect was invented for a reason though. I only used it once, for a 1-10 choice in the 10 pc party mod, but while absurd, could easily be converted to subcomponents. There is a more serious problem — input verification. If you just read it from an ini, what do you do about typos? READLN can handle it nicely: ACTION_READLN ~newmax~ OUTER_WHILE NOT(IS_AN_INT %newmax% && %newmax% > 0 && %newmax% <= 10) BEGIN PRINT ~Enter a whole number between 1 and 10 silly. What should the new maximum party size be? [1-10]~ ACTION_READLN ~newmax~ END

the 10pp mod takes care of fixing the scripts and dialogs, that's why it exists. There are very few occurrences that can't be handled automatically (like level scaling in the final soa fight).

I very much doubt it, you said it's just a vanilla install.

The log looks fine, so I'm out of ideas, sorry. It's in the realm of profiling now, which is not easy at all.