Closed GoogleCodeExporter closed 9 years ago
I would really like this to have several slots would be nice.
Especially testing it from beginning would be possible.
Original comment by SamuelPl...@gmail.com
on 25 Nov 2010 at 7:05
Additionally, savegames should be placed on the sd-card instead of internal
storage. So the players can get the actual files. (For doing backups etc.)
Original comment by oskar.wi...@gmail.com
on 26 Nov 2010 at 1:57
I have started looking at this, it will make testing much easier.
Do we want to save the "quicksave" on sd card also? The quicksave is written
very frequently. Every time most of the dialog boxes are shown, the quicksave
is written.
If the device doesn't have a mounted sd card (such as if it is mounted on a
computer instead), the game won't be able to quicksave and will crash.
Maybe we should save the quicksave to internal storage (like we do now), and
save the other slots to sd card?
On a side note, the savegames on sdcard will most likely be created in
"/sdcard/andors-trail/savegameNN", where NN is the slot.
Original comment by oskar.wi...@gmail.com
on 1 Dec 2010 at 9:54
IMO its good to have the quicksave on the internal storage then.
"/sdcard/andors-trail/savegameNN" - sounds good.
In the loading screen there should be the following informations to distinguish
savegames:
- player name, level, xp, gold
Side note: Someone with evil creativity could have the idea of cheating by
manipulating the savegame. Perhaps you could have a internal memory (md5) what
savegames exist. On the other hand you could not bring your savegame to another
phone then. (Connecting the two phones (bluetooth, internet) could work then)
;-)
Original comment by SamuelPl...@gmail.com
on 2 Dec 2010 at 7:01
I have now made an initial implementation of this. Four save slots, saved to sd
card. Very easy to add more save slots if we want.
I'll upload an APK soon when the quest log thing is done too. Hopefully this
weekend.
Regarding "cheating" by manipulating the savegame: I have no problem with that,
if someone gets joy out of it then please go ahead. After all, the game is
open-source, so you could just tweak your sourcecode to make your character
supermighty. Some people really like that, and I wouldn't want to deprive them
of that. :) If it would be a multiplayer game, then it would be a problem, but
not right now I think.
Original comment by oskar.wi...@gmail.com
on 3 Dec 2010 at 8:43
I totally agree about what you said about cheating - I had just some thoughts.
Original comment by SamuelPl...@gmail.com
on 3 Dec 2010 at 8:59
Original comment by oskar.wi...@gmail.com
on 3 Dec 2010 at 9:55
Original comment by oskar.wi...@gmail.com
on 3 Dec 2010 at 10:00
Thank you very much for providing different savegames! I can play from
beginning now and test it.
Some thoughts to improve it:
1) Currently loading and saving are accessed from different locations. (ingame
and from the menu)
IMO its better to place both in the menu. Then Ingame would only be a menu with
"exit to menu" and "preferences".
Or put them both ingame.
2) Could you additionally provide xp & gold values in the savegame?
3) If I save a game I would ask you to make sure that I do not overwrite
another hero easily. If 2 people play on the same device (or as in my case you
play 2 heros) there should be a security question: Do you really want to
overwrite this savegame? It contains a different hero name.
Or make it more obvious what hero file is saved right now: "Save the game of
[hero name], level [level number]" + xp & gold values if you accept (2).
Original comment by SamuelPl...@gmail.com
on 10 Dec 2010 at 7:39
1) Hm, maybe. I'm not completely sure. This way feels more intuitive I think.
When you are viewing the startscreen, you haven't really started the game yet,
so saving from there could feel odd.
2) Ok, done.
3) Good point, I'll look into that when I get time.
Original comment by oskar.wi...@gmail.com
on 12 Dec 2010 at 10:20
1) Disable it if there is no current game and noone would think its odd.
2) Thanks.
Original comment by SamuelPl...@gmail.com
on 12 Dec 2010 at 2:48
Original comment by oskar.wi...@gmail.com
on 20 Dec 2010 at 9:10
Original issue reported on code.google.com by
oskar.wi...@gmail.com
on 20 Nov 2010 at 10:26