Thunder Waffle

Yeah so members not as smart as real plugin contributors can push their modified plugins and higher entities then on some website / application can approve/deny the revision. To help unify all plugins.

One problem with H3/ODST/Reach is the plugin distrubution. You can go to Remenant mods and find some plugins or XboxChaos or S7. Hell, some plugins are more mapped in some areas on XC then Remanant. Some people spend time researching what is already done. A simple revision control could fix this.

Note saying is either said than done. I only said this because I use Gerrit & GIT daily for Android, but I don't know the simplicity of wrapping something like that into Assembly, but I will say I think it will aid in grouping the community together if their changes go to a central repo where they can all gather for approvals. EX (1 - 4 verifications, +1 approval from an admin).

Think about Entity & Halo 2. People updated it from 1.3 Beta -> 2.1.7 all seperately. Troy finally got it on GIT at v2.0.0 and that melded the development for it, but it was far too late.

Just an idea. I wrote a lot.

How are plugins handled?

Is there version control? Or some easy system for the community to interact with them.