{"action":"created","issue":{"url":"https://api.github.com/repos/eternaldensity/Sandcastle-Builder/issues/1346","labels_url":"https://api.github.com/repos/eternaldensity/Sandcastle-Builder/issues/1346/labels{/name}","comments_url":"https://api.github.com/repos/eternaldensity/Sandcastle-Builder/issues/1346/comments","events_url":"https://api.github.com/repos/eternaldensity/Sandcastle-Builder/issues/1346/events","html_url":"https://github.com/eternaldensity/Sandcastle-Builder/issues/1346","id":99878458,"number":1346,"title":"Shards/pane track - lots of boosts coded, what comes next? ","user":{"login":"Calamitizer","id":7929933,"avatar_url":"https://avatars.githubusercontent.com/u/7929933?v=3","gravatar_id":"","url":"https://api.github.com/users/Calamitizer","html_url":"https://github.com/Calamitizer","followers_url":"https://api.github.com/users/Calamitizer/followers","following_url":"https://api.github.com/users/Calamitizer/following{/other_user}","gists_url":"https://api.github.com/users/Calamitizer/gists{/gist_id}","starred_url":"https://api.github.com/users/Calamitizer/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Calamitizer/subscriptions","organizations_url":"https://api.github.com/users/Calamitizer/orgs","repos_url":"https://api.github.com/users/Calamitizer/repos","events_url":"https://api.github.com/users/Calamitizer/events{/privacy}","received_events_url":"https://api.github.com/users/Calamitizer/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/eternaldensity/Sandcastle-Builder/labels/meta","name":"meta","color":"f7c6c7"},{"url":"https://api.github.com/repos/eternaldensity/Sandcastle-Builder/labels/molpification","name":"molpification","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":109,"created_at":"2015-08-09T09:21:19Z","updated_at":"2015-08-30T01:00:32Z","closed_at":null,"body":"So, I've coded most of what's in my head for the shards/panes track, and most of it is pushed. I'll be backing off of coding new content now as we evaluate what to do next and which boosts need work or need scrapped.\r\n\r\nWhat's left relevant to those boosts is A) unlock conditions, specifically the numbers involved (e.g. how many CatPix does the player need to drain before boost X unlocks, &c.), and B) prices, specifically related to non-shard pacing (e.g. how does this mesh with the bonemeal/vacuum/logicat/qq track). I need a lot of help calibrating both of these things as they're very important for QA. What is SOP for deciding things like this? \r\n\r\nNext question: should this update wait to be released with TaTPix, or not? Personally, I am torn. On one hand, only three boosts (Aperture Science, Dimension Keyhole, and Green Sun, none of which is fully coded since neither is TaTPix) directly relate to TaTPix so far, since I have been focused on handling CatPix. There is plenty of CatPix content to be released, imo. But I also don't want that content to run out of steam before TaTPix is coded, or the whole point of shards is ruined. I would lean to releasing at least some of it earlier, but I'm not sure it would feel like it had a point. What do you guys think? \r\n\r\nIn short, I'm just not sure what needs to happen next. I would really appreciate thoughts on the current content of the track, as I've been working mostly in isolation and I don't want to code a bunch of stuff that's considered bad. If I have made any questionable design decisions, please let me know; that's my big question here. I'm still extremely new to both JS and game development so I'm constantly worried about doing something dumb. "},"comment":{"url":"https://api.github.com/repos/eternaldensity/Sandcastle-Builder/issues/comments/136067018","html_url":"https://github.com/eternaldensity/Sandcastle-Builder/issues/1346#issuecomment-136067018","issue_url":"https://api.github.com/repos/eternaldensity/Sandcastle-Builder/issues/1346","id":136067018,"user":{"login":"pickten","id":6465870,"avatar_url":"https://avatars.githubusercontent.com/u/6465870?v=3","gravatar_id":"","url":"https://api.github.com/users/pickten","html_url":"https://github.com/pickten","followers_url":"https://api.github.com/users/pickten/followers","following_url":"https://api.github.com/users/pickten/following{/other_user}","gists_url":"https://api.github.com/users/pickten/gists{/gist_id}","starred_url":"https://api.github.com/users/pickten/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pickten/subscriptions","organizations_url":"https://api.github.com/users/pickten/orgs","repos_url":"https://api.github.com/users/pickten/repos","events_url":"https://api.github.com/users/pickten/events{/privacy}","received_events_url":"https://api.github.com/users/pickten/received_events","type":"User","site_admin":false},"created_at":"2015-08-30T01:00:32Z","updated_at":"2015-08-30T01:00:32Z","body":"Aware of the first (there are erroneous math.abs, but it's not like you can fledge on negpix anyways -- I'll fix it, but it's less high-priority than, say, getting the indicators working). I know the source of the second and suspected there'd be something there, but it doesn't make itself shown on classic so I didn't notice."}}