GG of course being 32 bit was well known for having memory constraints and
anomalies (sometimes in the editor and sometimes transferred to stand-alones.)
Back in the day, I've had such strange anomalies as trigger points being all jumbled
up (in standalone in fact!)

I wonder if those memory issues particularly particle testing will be inherited by MAX-
-although of course the memory capacity will be over 10 times as great. (What actually
is the limit?)
In testing particles in GG, it only take 5-6 re-tests before the particles you have
custom summoned to disappear and default sprites and setting to take over.
Then you have to shut down GG and restart!
Just wondering if it's a good idea to bring out some of these monster issues
prevalent in GG, now that MAX has a little more development breathing space?

Like mentioned, sure, there's a ton more available memory in MAX, but why
allow the memory leaks / accumulations to accrue? Maybe wicked engine already
has a system for that? Or-- maybe a fix in MAX will transfer to a fix in GG jr??

The custom particle reset has nothing to do with 32bit or memory leaks.

It’s ‘just’ a bug and can be fixed. It doesn’t feel like a monster issue though can be annoying.

The only way to know how max has been adapted is to test it when a stable version comes out.

A lot of changes have been made as you say so needs several months of active testing to check the new state of play.

The trigger zone issue sounds worse - do you have a map that can be used to highlight and test the problem?

Cheers.

Howdy, cybernescence-
"do you have a map that can be used to highlight and test the problem?"

Maybe that is hanging around here somewhere, though this was almost
a couple years ago- and so I haven't re-visited it since then.

An image zone swapped with a story zone, and a couple other zones
got confused. It was too odd. The particles though are something that
I was recently working with. Radical!