Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Defining Standards #2

Open
Amaikokonut opened this issue Apr 15, 2020 · 1 comment
Open

Defining Standards #2

Amaikokonut opened this issue Apr 15, 2020 · 1 comment

Comments

@Amaikokonut
Copy link
Member

The standards listed in the readme are really old. It would be nice to redefine them and break them down into a checklist so we can tell at a glance what needs to be done for each species.

Things that might be on this list include:

  • Assigned its own classifier (since most of these currently reuse C3 classifiers and we certainly don't want our new scripts messing up docked ships)
  • Conforms to Creatures Development Standards (this might be broken up into multiple checklist items, I dunno)
  • Does not require CAs
  • Does not depend on another specific species classifier to survive (IE bugs should eat plants/leaves in general, not one specific plant/leaf agent)
  • Has population control limits (should we define these more strictly?)
  • Has extinction control limits (these aren't supposed to be foolproof, but should be pretty tough)
  • Is just a little bit more special in some way (??)
  • Has been bugtested (We should probably set up a standard testing system for this too)

I also don't want to imply that things can't be created outside of these standards (and of course anyone can fork this repo and do whatever they want with it), but for the purposes of making the species as global and useful to everybody as possible, this feels like a good starting place.

Would really appreciate any thoughts/feedback/discussion on this!

@JennaMalkin
Copy link
Contributor

See also Creatures-Developer-Network/C2toDS-Refresh#41 which may be useful in the Standards portion of this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants