Valery, why Era 2.7.4?
Let him delete Mods\WoG\Data\Scripts directory, because Win 10 compatibility was reached only in 2.8.X branch, when the whole virtual file system was rewritten. And it took quite a lot time to catch all its issues. Particularly this question was answered dozens of times on HC

Archer30, glad to see you and yunings here.

Quote:The latest report was WoG campaigns not playable since all maps are now forced WoGified upon starting.

!#UN:P5/0 in WoG campaign fixes it. No global scripts loading. In my WoG Campaigns release I extracted all scripts, fixed bugs in few of them and added !#UN:P905/0 in each scenario.

ERM/Lua is scripting engine. If you run something in it, scripts must be loaded. If map author wants to disable all global ERM scripts by any reason (because of old-style variables clashing), why not to do it using !#UN:P5/0?

Quote:The problem mods and scripts is that "poor compatibility" concept does not exist. Either it works 100% or not. A simple error means 0% compatibility, mod will not work and map can't be completed..

So WoG 3.51 scripts are fully compatible with WoG 3.59 TE? Even written with hacks, even relying on not documented features and bugs like preserving garbage x-vars,y- values between triggers?
I've already recommended to use the version you developped mods on. Era 2.8.4 would probably fit community needs. Yep, it has many not fixed and ignored old ERM issues and 10x times slower, but still, is playable, like WoG 3.58.

Old WoG !?MP/!!MP implementation, for instance, leaded to constant crashes in multi-core execution mode. It was not thread-safe. Updated implementation, on which I tested a bit Atlantis, has 1 small issue, but game does not crash anymore.

Era 2.46 had not ERM tracking support. On 2.6+ (iirc) you can press F11 or get a crash and open Debug\Era\erm tracking.erm to see 10000 of latest executed receivers and triggers in valid order and with all information about files, lines and positions.

Quote:Even just testing the compatibility is unimaginable time-consuming.

Perhaps, some issues can be fixed automatically via script in php/python/what so ever. But it's easy to use Era 2.46 for really old and poorly written mods.

Many scripts are just easier to rewrite in Lua or at least ERM 2, because tons of code in WoG 3.58 scripts. for instance, are functions callings functions for loop implementation and duplicates conditions like &v1=7/y5=-1/y65=3, &v1=7/y5=-1/y65=3, &v1=7/y5=-1/y65=3...

I could write

Era 3 was written to maintain 99% compatibility with modern mods or mods without dirty hacks. Any bugs, which are really new bugs, will be fixed if reported.
!!HE:X short syntax will be fixed in the next release and probably backported to 2.9.14.

Normal code should almost have no issues. Using y- variables was almost a bad idea, using UN:C hacks everywhere + TL timers like Jim Vogan liked was always a hardly porbable solution.
After upgrading Era many ERM errors, that were silently ignored in WoG 3.58f scripts, became reported by engine.
!!IF&v1000000=7:M^Possible crash, but did you know that old ERM engine never checked indexes in conditions?^;

-------------------------------

I suggest 2.46 for really old mods, 2.8.4 for most of Valeries mods, 2.9.13/Era 3 for modern mods.
Will try to fix reported bugs, introduced by Era.