Open tterrag1098 opened 9 years ago
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)
I have made some progress on the HTTP requests, you can log in with /ctb-login <email> <password>
and get a response in chat:
This is of course temporary, but I have a bit of backend handling the POST request.
Yet more progress, you can now use /ctb-creators
to get the creators for a user once you log in.
Awesome! Great to see the progress you're making there!
Some thoughts
1) Is the dependency on EnderCore necessary? I know you have some utility methods you don't want to have to rewrite but at the same time it is a dependency moving forward 2) Have we decided what version(s) of Minecraft we are targeting? Are we sticking with Minecraft 1.7.10 and or 1.8.*?
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.