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

Roadmap #1

Open
tterrag1098 opened this issue Sep 12, 2015 · 7 comments
Open

Roadmap #1

tterrag1098 opened this issue Sep 12, 2015 · 7 comments

Comments

@tterrag1098
Copy link
Contributor

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

  1. Get the API interfacing figured out
    • Logging in to creatubbles
    • Downloading a specific creation from one's library
  2. Get the UX figured out
    • I think we should first maybe create something simple like a command, then once that is functional create a block/GUI.
  3. Art
    • I don't art. We need an artist.

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.

@tterrag1098
Copy link
Contributor Author

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)

@tterrag1098
Copy link
Contributor Author

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.

@tterrag1098
Copy link
Contributor Author

Yet more progress, you can now use /ctb-creators to get the creators for a user once you log in.

@petervdw
Copy link

Awesome! Great to see the progress you're making there!

@pahimar
Copy link

pahimar commented Sep 16, 2015

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.*?

@tterrag1098
Copy link
Contributor Author

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.

tterrag1098 added a commit that referenced this issue Sep 17, 2015
@tterrag1098
Copy link
Contributor Author

Alright, ported it to 1.8, and removed the EnderCore maven dep in favor of manual repackaging of the classes I use.

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

3 participants