lynx

Thanks, didn't even notice that.

Wow that's interesting, a weidu syntax error. The one line it tries to patch looks fine too, so I'm none the wiser. I guess I'll just have to try it myself later.

I don't suppose you saved the error you got with Djinni Companion? I filed a reminder either way.

I'd guess it's a design leftover. Could be an optimisation, but I doubt that, since the games keep many copies of stat values already.

That's no excuse for this there, it's not really a performance improving bug.

I question the original assertion.

Do you really need it programmatically? You can save list with the Advanced search in NearInfinity. Add a filter with the field "Category" and set the value to the item type that you want.

Here's a column inserter I made for an iwd2 mod where column position matters. It supports a default value, so you can override only the needed cells.

• function: https://github.com/lynxlynxlynx/gemrb-mods/blob/master/cleric-of-eilistraee/functions.tpa
• example call: https://github.com/lynxlynxlynx/gemrb-mods/blob/master/cleric-of-eilistraee/cleric-of-eilistraee.tp2#L33

Thanks go to CamDawg for the idea and debugging help.

It just has to be last.

If you wanted to complicate matters, local vars can be set via effects as well:

https://gibberlings3.github.io/iesdp/opcodes/bg2tob.htm#op187

Wouldn't make sense mechanically either, thanks — updated.

So I guess nothing to do here?

The fact that they still haven't commented anything is enough for me, the intentions were clearly malicious. And the community is already proposing alternative governance models for a new open game license, new gaming systems etc. They couldn't have shot themselves in the foot harder if they tried.

I don't understand how one could retroactively change a license — any such legal text that allows it is garbage.

EDIT: I feel this is an appropriate level of hype for the future:

Ah, it's all about iterative improvements, don't worry about it. It looks fine to me, but I'm not a native speaker.

Well yeah, each level is stored in a separate stat, so you get what you asked for. You can check the other two levels, but don't rely on any ordering, since it depends on the class name.

1. is correct for sure, we had to make it conditional in gemrb.

3. I never tested if both are needed; we just check for enchantment and that seems to be enough.

Weather can be changed via scripts, but you can't say "give me just a flash of lightning". And using fading would probably be too slow.

There is no such opcode in iwdee, it's pstee-only (the original has it elsewhere):

https://gibberlings3.github.io/iesdp/opcodes/pstee.htm#op354

Yes, they were hardcoded in the originals. InfinityAnimations used engine hacks to add new ones, you can look at that. It would be easiest to base your mod on it, even if you just repurpose one of its slots.

Feel free to submit a PR.

Look them up on IESDP

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

Use the cast spell on condition effect with the enemy sighted condition. There's just more hassle to make it apply only once per combat and to make it work properly as an equipping effect.

If you want to improve readability, I suggest removing clutter (so called chart junk) first.

If you have all the data points labelled, there's no need for the vertical axis labels. But that's minor. It'd be much cleaner the other way around, without the numerous labels — people supposedly know how to read charts. Either way many ticks could go.

If the labels remain, I suggest at least rounding. I guess the underlying library just sucks and you can't improve placement (overlap, cutoff)? And you could only draw them when the slope changes or there is an intersection.

I'd also suggest a bit thicker connecting lines, so when there's more of them, it's easier to match the colors with the legend, since it's more likely similar ones will get used.

The legend could also use more spacing. Personally I prefer vertical ones, since all the markers are then aligned and easier to compare.

As for the baseline: like I said, I'm not sure what the best would be. Perhaps 0 (for relational integrity), but perhaps not, it's combat after all. So maybe fists at STR 24, which could have respectable damage in theory, but I guess crappy APR and to hit chances that likely lead back to 0.

Just set a limited duration on the effect.

Nobody has been doubting the intention, just your engineerial approach to perception and pigheadedness.

To lighten the mood, here's a German gem I found today, after it has been online for at least two years, from a reputable institute at that: