Heh, I'm still young and I still have time to make choices like these -> I've been 'developing a game' of sorts for a few months now (including learning C and Obj-C then that makes it over a year) but after really taking into the account the situation and where I was headed with the project I came to the conclusion that it was far to ambitious.
I have the skill to do all the art, animation, and programming (A lot of experience with Adobe Flash CS5 and love maths) but there is not enough TIME.
I also thought my game would not be suitable for the market/mobile technology/touch and accelerometer input/especially for the time it would take to develop.
New plan. :)
This game is on a much smaller scale and overall open to much more optimization to the efficiency of my workflow.
The game is platformer-ish (<- *Insert references to innovative secrets here*) and I want it to be really easy for:
A) Me to create levels (possibly using an external program)
B)The user to create levels ('simple' drag and drop from objects list)
--------------------------------------------------------
TL;DR
--------------------------------------------------------
I want to have a file format that allows me to easily store and transfer/upload/download levels.
I need a very minuscule set of variables because all the logic and such will be determined upon loading the level.
Variables per object:
Object: Type:(integer value corresponding to a collection of objects defined in code that each have individual logic patterns/graphics)
Position.x
Position.y
-(Possibly)Some other attributes
I'd like to be able to save/load this data REALLY fast and be in a very simple format that is easily transportable (e.g. online, through e-mail, social networks etc...)
Some ideas I had in mind were using strings of characters and numbers in a recognizable format like:
f247897 -> f (type of object represented by a letter) 247 (pos.x) 897 (pos.y)
Or even to allow for simple digit value changing:
f1036z12000 -> Where z is recognized as the divide between the two positions
This seams like a very compact way of storing data in just a simple NSString (Not sure how to actually save an NString other than overkilling with a .plist :P)
Perhaps there is a way to split a string into characters and store them individually in an array of sorts? Of course to compare the characters and load data corresponding to their significance/value.
I'm very open and looking forward to ideas/discussion about this topic - I don't see it/haven't seen it around very much. :)