-
Notifications
You must be signed in to change notification settings - Fork 17
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
Migration to the latest Bevy API of 0.11 #11
Comments
related issues: |
I am guessing this is no longer maintained. Is there interest in a fork to bring it up to date? |
I just have never been able to make some time to keep up with it but I would love to transfer ownership of the project to someone else or for a fork to take off |
I was indeed interested in making some terminal arcade games using bevy for a personal project. I would be more than willing to help out with new ownership or on a fork. |
I will spend some time this weeke and see about at least updating it to Bevy and going from there. I did see @ecrax had a fork that looks to have been at least partially updated. |
Oh yeah, I totally forgot about this. As far as I can remember, there was some weirdness to one of the examples. But everything else (should) be working fine (I hope). Feel free to use my fork as a reference, or even copy it entirely :). |
Very cool! I will take a look at your fork 💯 |
Any updates? |
ah that's right, no progress yet. but this does remind me it is something i wanted to work on, thanks! |
Migrated to bevy 0.12: ecrax#2 |
much as the title says the beginning of migration to the latest bevy api is needed. additionally, it would be excellent to develop a consistent workflow of updating in step with each bevy release.
The text was updated successfully, but these errors were encountered: