I think we need to reform the submission rules a bit
-> as simplistic as possible (performs a clear purpose and nothing else, no extras)
-> as modular as possible
-> naming conventions observed
-> a resource is useful if it both has a use and is different (pros vs cons) or superior to current resources (if any) that perform the same task
-> when using safety, safety must be optional. It is up to the user to decide whether they want to go with all out speed or all out robustness. Robustness is always a necessity, but speed should always be an option as well.
-> if clear improvements can be made to a resource, those improvements must be made to that resource. Good enough is not good enough, it must aim for perfection.
-> every resource must have a description containing information pertinent to that resource's implementation. For example, a linked list does not have to be described as a linked list, but the type of linked list should be described (if not done so within the data structure name) and the sentinel node used should also be described (if not done so in the API). If the resource is built differently from a standard implementation, those differences should also be stated.
-> all resources that a given resource uses must be linked to
-> clear API definition at the top within the docs with descriptions where necessary
-> customization must be done through globals, textmacros, or modules at the top within the docs
-> any resource that is a single function or initialized data structure is a snippet
-> any resource that is a data structure is a collection
-> any resource that creates, destroys, and manages its own data (UnitIndexer, DamageEvent, etc) is a system
-> any resource that is plugged into or has a major collection of other optional snippets that make it up is a framework (save/load with snippets)
-> any resource that creates, destroys, and manages data at the user's request and doesn't fit into the above categories is a script
-> resources must be commented
any resource not meeting all of the above criteria, whether currently approved or previously submitted, will be required to stay in submissions
any resource that stays in submissions in excess of 1 week will be graveyarded and a new submission must be made
not all of my resources meet the above criteria, so I'd have to do updates as well D: