There are a lot of people in these topics who do stupid shit and tell us half of it. For example, they use tables plus trainers at the same time. Use 2-3 options from the trainer, activate them, then 2-3 from the table. Then when the tables doesn't enable some script.. barge on the forum to whine the table is not working. That's all they say, never the context, never what they tried, it's ike they're fucking morons who can't talk proper sentences.
Like the OP said, everything works fine, tried it on the Steam version. The only other thing I can think of, that can be tried, is for the user to fucking close a shit load of their processes OR enable the options at main menu. Then go in-game. Why.. because if already in game world and game has allocated memory till the 4GB boundary, then any allocation you do in the scripts will turn to be a far address. And when that happens, the script won't activate cuz "offset too long"..
I suggest using trampolines in the future, just as a precaution method. Simply doing "alloc()" doesn't guarantee the allocation will be close to the game process. Yes, even if you specify the module in the alloc itself. Seen this myself with games like Odyssey, Origins, etc. Heavy mem eaters.
@OP: Although it works for you and many others, it's not an excuse
Why not say you don't give a fuck about it instead? Doesn't look like you wanna help the user solve this, so you might as well be true about it
)
Lastly, if a script doesn't activate, please fucking right click it (after you tried to activate it) and take a screenshot of the error you see there? That's the least you can do.. Thanks!