{"action":"closed","issue":{"url":"https://api.github.com/repos/PistonDevelopers/hematite/issues/209","labels_url":"https://api.github.com/repos/PistonDevelopers/hematite/issues/209/labels{/name}","comments_url":"https://api.github.com/repos/PistonDevelopers/hematite/issues/209/comments","events_url":"https://api.github.com/repos/PistonDevelopers/hematite/issues/209/events","html_url":"https://github.com/PistonDevelopers/hematite/issues/209","id":60058449,"number":209,"title":"Make setup a little easier.","user":{"login":"mattico","id":853158,"avatar_url":"https://avatars.githubusercontent.com/u/853158?v=3","gravatar_id":"","url":"https://api.github.com/users/mattico","html_url":"https://github.com/mattico","followers_url":"https://api.github.com/users/mattico/followers","following_url":"https://api.github.com/users/mattico/following{/other_user}","gists_url":"https://api.github.com/users/mattico/gists{/gist_id}","starred_url":"https://api.github.com/users/mattico/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mattico/subscriptions","organizations_url":"https://api.github.com/users/mattico/orgs","repos_url":"https://api.github.com/users/mattico/repos","events_url":"https://api.github.com/users/mattico/events{/privacy}","received_events_url":"https://api.github.com/users/mattico/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/PistonDevelopers/hematite/labels/draft","name":"draft","color":"e11d21"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-03-06T04:38:17Z","updated_at":"2015-11-25T16:48:54Z","closed_at":"2015-11-25T16:48:54Z","body":"I'm creating this issue to organize the discussion that started in #177 about making the setup process for hematite a little easier. In particular, [this Gist](https://gist.github.com/toqueteos/e2e2921d4f9e639b0eec) by @toqueteos is of interest. Goals:\r\n* Reduce required arguments as much as possible\r\n* Reduce set-up steps as much as possible\r\n* Simplify world file handling\r\n\r\nIn order to accomplish this, I propose the following changes:\r\n1. Assume that the minecraft folder is in one of the default locations, unless overridden by a flag.\r\n2. Use the newest supported jar from the minecraft folder, unless overridden by a flag.\r\n3. Automatically extract the jar to `assets/` or just read from it in memory?\r\n4. Don't require a fully qualified path for world folders, assume it's in the minecraft folder. E.g: `hematite world` is equivalent to `hematite ~/.minecraft/saves/world`\r\n\r\nPros:\r\n* Small, localized changes\r\n* Makes hematite easier to use\r\n\r\nCons:\r\n* Zip library dependency\r\n* Flags\r\n"}}