{"action":"created","issue":{"url":"https://api.github.com/repos/ehgoodenough/papercut/issues/77","labels_url":"https://api.github.com/repos/ehgoodenough/papercut/issues/77/labels{/name}","comments_url":"https://api.github.com/repos/ehgoodenough/papercut/issues/77/comments","events_url":"https://api.github.com/repos/ehgoodenough/papercut/issues/77/events","html_url":"https://github.com/ehgoodenough/papercut/issues/77","id":111555812,"number":77,"title":"Plan what to do next for Project Papercut","user":{"login":"ehgoodenough","id":1202938,"avatar_url":"https://avatars.githubusercontent.com/u/1202938?v=3","gravatar_id":"","url":"https://api.github.com/users/ehgoodenough","html_url":"https://github.com/ehgoodenough","followers_url":"https://api.github.com/users/ehgoodenough/followers","following_url":"https://api.github.com/users/ehgoodenough/following{/other_user}","gists_url":"https://api.github.com/users/ehgoodenough/gists{/gist_id}","starred_url":"https://api.github.com/users/ehgoodenough/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ehgoodenough/subscriptions","organizations_url":"https://api.github.com/users/ehgoodenough/orgs","repos_url":"https://api.github.com/users/ehgoodenough/repos","events_url":"https://api.github.com/users/ehgoodenough/events{/privacy}","received_events_url":"https://api.github.com/users/ehgoodenough/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-10-15T06:48:44Z","updated_at":"2015-10-15T22:42:30Z","closed_at":null,"body":"@skylarjhdownes @EdKerscher @eCorbeau, leave comments below. What should we try to target next with this project? At the moment, Skylar and I just fixing bugs here and there. What would you like to see come from this weekend prototype?"},"comment":{"url":"https://api.github.com/repos/ehgoodenough/papercut/issues/comments/148543941","html_url":"https://github.com/ehgoodenough/papercut/issues/77#issuecomment-148543941","issue_url":"https://api.github.com/repos/ehgoodenough/papercut/issues/77","id":148543941,"user":{"login":"eCorbeau","id":15066452,"avatar_url":"https://avatars.githubusercontent.com/u/15066452?v=3","gravatar_id":"","url":"https://api.github.com/users/eCorbeau","html_url":"https://github.com/eCorbeau","followers_url":"https://api.github.com/users/eCorbeau/followers","following_url":"https://api.github.com/users/eCorbeau/following{/other_user}","gists_url":"https://api.github.com/users/eCorbeau/gists{/gist_id}","starred_url":"https://api.github.com/users/eCorbeau/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/eCorbeau/subscriptions","organizations_url":"https://api.github.com/users/eCorbeau/orgs","repos_url":"https://api.github.com/users/eCorbeau/repos","events_url":"https://api.github.com/users/eCorbeau/events{/privacy}","received_events_url":"https://api.github.com/users/eCorbeau/received_events","type":"User","site_admin":false},"created_at":"2015-10-15T22:42:30Z","updated_at":"2015-10-15T22:42:30Z","body":"Re: procedural tile-based terrain maps: That's more of an AI issue than a map generation issue.  Generating maps is something that I have plenty of experience tinkering with; the only reason I didn't go for it during the game jam is because I don't know javascript and other features were a bigger priority for the team members who do know javascript.  If I'm implementing this feature as part of learning javascript though, then it's not a big problem to add basic terrain as part of level generation.  It would be barely more complicated than adding an additional type of monster."}}