ENIGMA Development Environment

While I certainly don't oppose the idea, I do, however, feel like this is just another case of "stick it on github and the problem is magically solved". The problem with this ideology is twofold: 1) Interested manpower. Most of our interested manpower is already working on the wiki and enigma, which have higher priority than the bot and the website (as they should). As for generating interest, that leads to point 2) Generalizability. The bot and the website are pretty much singletons. They don't generalize to anything else, so there's not really a need for a second one to be launched anywhere else on the entire internet. Generally a project is best suited for source distribution and version control when it's expected that there will be multiple instances of it.

This leads to a more serious issue: more leechers than seeders. With so few people actually contributing to these projects, the only thing opening the source code effectively does is allow people to read it, learn from it, and abuse it. We're revealing our security flaws, but are we fixing them? If we're not, people will use those security flaws.

Just my two cents and concern. At any rate, I'd love to see them both worked on more, but I think we should hesitate a little before we just jump to "throw it on github for all to see".

You could fudge it and do a sleep(1) every few frames.

Room speed can be set to 0 as of f2c5c2f89adc. Robert has been maintaining the latest builds, so he'll probably build it for you.
Note that this behavior may lead to incompatibilities in GM.

This sounds like a LateralGM bug, so it belongs on the LateralGM tracker, not the Enigma tracker (the link at the top). But it looks like gra's going the correct route anyways.

Regardless of packages, those are essential libraries that must be obtained in whatever way mac provides, and I'm fairly certain the mac installation instructions and dependencies pages on the wiki explain how to get those sufficiently.

LateralGM is proud to state that these changes have been merged into the official LateralGM repository with appropriate revision to make them acceptable.

Robert has expressed that he does not desire to continue to maintain a separate fork of LateralGM, and his changes were always intended to be merged back into the main LateralGM repository maintained by myself.

Note that for the time being, Robert will be in charge of understand exactly what this implies for persons wishing to checkout or build from the LateralGM repository (namely, which branch to use), at least until I can figure it out for myself.

The Override tag will not directly cause any implications. They simply prevent the programmer from doing something stupid like mistyping an override function (capitalization, for example) and ending up with inherited behavior when you thought you overrode it. They're just a preventitive measure, so to remove them will not break anything.