-
Notifications
You must be signed in to change notification settings - Fork 2
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
Roadmap #1
Comments
Just a sidenote, I am planning to have EnderCore as a compile-time dep, but shade the files I use so that no dependencies are needed at runtime (@pahimar will know what this means :P) |
Awesome! Great to see the progress you're making there! |
Some thoughts
|
Oh good point....I totally forgot about mc version target. I think they wanted to go with 1.8 (what I have now barely relies on mc version at all so I can port it easily.) That will also mean I need to drop EnderCore as a "true" dependency, I'll probably just copy classes (and port them) out as needed. |
Alright, ported it to 1.8, and removed the EnderCore maven dep in favor of manual repackaging of the classes I use. |
I think since this is a collaborative mod it would be nice to lay out our thoughts for where it is going.
In my mind we need to
As per their specifications the user should only be able to use creations from their own account, so they would need to log in before doing anything. This requires the mod to "know" their password for at least a short amount of time, but we can have a privacy policy etc, and of course we would not store that data, only the access token returned.
Feel free to add any other ideas/thoughts you have.
The text was updated successfully, but these errors were encountered: