Flame
Two
Here you can find some tips and trivia related to FlameTwo.
PowerPC G4
The current 2.8 FlameTwo version remains compatible on this PPC G4 12-inch PowerBook running 10.4.11. If you need to use/test something this old, download and run the aaeb demo installer instead of following the QuickStart guide included with Flame Two. The guide was designed for modern Intel systems, and was particularly tested with Sierra and High Sierra.
Scalability
Around 1997-1998, as SC testers started getting their hands on the original FlameThrower, the question of scalability came up often, and understandably. A fast G4 Mac Server ran 450MHz and shipped with 512MB of ram. 56kHz modems were more common than the "fast" 256kb/s "broadband" networks rolling out. Ultra 160 SCSI drives were considered quick at 20-30 MB/s. Even more burdensome, it was common and expected that this single CPU would be serving the whole site in addition to the FlameThrower work. Clearly lots has changed.
Here is a screenshot glimpse of a future extended post on the topic, which I hope to tackle soon.
For reference, each of these Tiger Server VM's has FlameTwo plus 11 more engines. 96 interpreters total, all sharing a 10G network to a business router with gigabit access to the internet. Static content is served with Apache via Akamai/Linode with separate network bandwidth. Lots to discuss :)
If you'd like to try so many interpreters, the multi-color kit can be downloaded here, (34+MB).
Lauguage tips
As users of SC, we use card fields to present information, and interchangably move data between them and user properties and variables. Things are slightly different with FlameTwo.
Apache, AAEB, and your FlameTwo variables all properly handle foreign language (non-english) characters. But if you try viewing them in a card field they may be horribly strange. The same thing can be said for user properties. Reading from and writing to them is fine, but if you want to "view" the contents of the properties in SuperEdit, they could look garbled.
The best advice is to lean less on fields when other languages are needed, and lean more on what you see in the browsers.
The textData property of draw graphics unfortunately suffers from the same text engine issues, and may have unpredictable results.
Remote AppleEvents
When multiple CGI engines are being utilized, it can be useful to "send" commands and data between standalones. Sending between standalones on the same CPU continues to work well through Mojave, but Remote AppleEvents are another story altogether.
If Remote Apple Events are enabled in the Sharing pane of System Preferences, you can send the same data to standelones on other CPUs or virtual machines. You simply add the "eppc://123.45.67.89/ etc address block to the command. But as of SC version 4.7.3, this remote event capability changed over time, either on SuperCard's side or Apple's side.
Tiger through Lion work as expected, but starting with Mountain Lion, the sending standalone claims all is well, and the receiving standalone never receives the data. If you rely on this type of inter-app communication, you may wish to choose those earlier OS's. Perhaps some of this has been addressed with SC v4.8. I currently have no capability to build anything in 4.8 or onward for testing.