Jump to content

  • Log In with Google      Sign In   
  • Create Account


Member Since 04 Oct 2012
Offline Last Active Aug 30 2014 11:27 AM

Topics I've Started

Advice for managing two different codebases for one game using Git (browser and iOS ver...

11 October 2012 - 04:37 AM

I'm making a JavaScript and HTML5 game. I mostly work in the browser on my Mac, but the final ideal goal is to deploy on iOS as well as browser. Therefore at least a couple of times a week I compile the entire thing using a different framework to deploy to and test on my iPhone. Most of the code ports over nicely, but as you can probably expect some parts require modifications and tweaking (not to mention the fact that the browser version does not need the framework files). This results in my having to change up various piece of code in both files on the day that I test the port. I try to consolidate the code as much as possible and sometimes end up making edits to the iOS code that are ported back to the browser code, or vice versa. Juggling two codebases for the same game can get quite confusing and a hassle in general.

The editing timeline basically looks like this:
  • Work on browser version, add new features, test, etc. Doing this in the browser allows me to work much more efficiently than compiling and testing in Xcode each time.
  • End of week port entire thing to iOS framework, deploy to iPhone
  • That day fix any problems in iOS port, try to consolidate code between the two as much as possible. This results in tweaks being done in both codebases and copies/pasted between each other that day
  • Continue working on browser version until next port
Right now I use Git for version control, hosting my code on Github for the browser version of the game. I have a dev and master branch. I do not currently use version control for the iOS version at all because I do not know the best way to set this thing up. Should I maintain the entire iOS codebase including the framework in another branch of my main game repo? Should the iOS version be in its own repo? Ideally I'd be able to set it up so that I can just pull relevant files from the browser branch to the iOS branch when I'm testing the port (but sometimes parts of the code would need to be left out, as there are some differences required), then push necessary changes back to both the browser and iOS versions of my hosted code.

I'm not a Git expert and am just not sure what the best way is to go about this. Right now I mostly use it for keeping a main working version of the game in one branch and merging the development branch into it when experimental stuff gets finalised. Fiddling with two sets of code on these porting days is getting confusing and I'm finding myself making mistakes, plus wasting tons of time. Can anyone advise how one might manage this kind of thing better?

Opinions on resetting difficulty+experiencing the same series of overarching events fro...

11 October 2012 - 01:48 AM

I'm curious about people's views on having the player (optionally) experience the same story from three different perspectives in different playthroughs. I was originally going to post this in the Writing forum, but realized the question is more about the overall player experience in terms of progression rather than the story itself. Apologies if I was wrong and placed this in the wrong forum.

The idea: The core mechanics basically involve an Asteroids-like multi-directional shooter and build on that. The player selects a character they want to play out of three at the beginning (female, male, AI) based on a brief description and an overview of strengths/weaknesses. Player completes playthrough with that character, then optionally chooses another character to use and starts from the beginning of the overall story timeline. I'm guessing each character's playthrough may take 45 minutes to an hour (but this estimate is still very flexible).

Progress: Most of the core mechanics are complete (with much refinement to go), but in terms of content right now I am building levels for the first character, allowing me plenty of opportunity to vary up what I'm going to do with the other two based on feedback I receive here.

Question: As a player, would you prefer to experience the same series of events through another character's eyes/personal perspective or would you prefer to just have each character progress you further in the main story of the game without overlap? Do you see the former working? As an example:

Character A: Starts at Level 1, Day 1.
Level 1: Recover Blue Widget from planet.
Level 2, 3, etc
Finish playthrough

Character B: Starts back at Level 1, Day 1.
Level 1: Defend main ship from attack for X time while Blue Widget is being recovered from planet.
Leve 2, 3, etc.
Finish Playthrough


Character A: Starts at Level 1, Day 1, finish at Level 10, Day 10
Character B: Starts at Level 11, Day 11, continuing where A left off.

The first case would be a matter of optionally restarting from the lowest difficulty after you are done with whatever character you chose to play first.

The second case would be a matter of continuing the difficulty progression with each character. You would have no choice in what character you use - you'd start with A, go on to B, finish with C. I guess technically here you don't even have to have multiple characters with this option, so the main question is - do you see the first case working to deliver a positive player experience?

Original Rationale: I had hoped that if I can do this right, I can potentially have the player glean new pieces of understanding or information as they experience what's happening from varying points of view. Seeing things from different perspectives is interesting to me personally, and trying to intertwine three paths in that way successfully is even more so. However, I'm not sure if this is actually as potentially fun and interesting as I'm hoping it could be, or if this would give the player the most enjoyable experience even if I manage to do it right in terms of writing this thing. Which is why I'm here, looking for opinions Posted Image