-
Notifications
You must be signed in to change notification settings - Fork 115
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
Development Tracks #124
Comments
A few other potentially low/medium priority tracks might be:
I guess you can put these together under "chores". Maybe I can create tracking issues if they are fine. Just giving my 2 cents. |
You’re welcome to create tracking issues for these 👍 I’d consider them all part of an overarching ‘Builds’ track. |
I created the following build-related issues for now: |
@erlend-sh do you think this issue should be updated or maybe closed in favor of new tracking issues? |
Now that we have all our essential items queued up, we need to map out the other “main tracks” of development we wanna kick off next. Item dev will always be an available track because there’s an infinite number of items (-variations) to be made.
Tracks
🎨 👉 We also need main tracks for pixel-art, sounds, level design etc., but we’ll return to those in a few weeks, once the coding tracks are in progress.
🚧 Under Construction: ( edit by @zicklag ) With bevy rewrite, a lot of things have been moved around and we are still getting things stabilized. We're in the middle of documenting and re-organizing so these development tracks may not be 100% accurate at the moment. Feel free to comment, open a discussion, or hop on the Discord if you have questions on how you can contribute!
The text was updated successfully, but these errors were encountered: