Omnimaga
Omnimaga => Discontinued => Our Projects => Ash: Phoenix => Topic started by: squidgetx on November 01, 2010, 03:10:28 pm
-
mmmmmmm...subforum. Btw, "Phoenix" in the board name is spelled wrong. (sorry for the inconvenience)
Anyway.
I need to know what the community thinks is the best option for death consequences. I am currently completely on the fence about these two choices. Please vote, discuss other options and the available options here. Thanks!
Option 1: Load at last save point
Advantages: very easy and small, most people end up doing this in RPGs that use option two merely by just shutting the game off w/o saving
Disadvatages: Can ruin games where you forgot to save, can trap players in dungeons (think saving in the middle of the Elite 4 in pokemon; it means that if you can't beat them, you have to force yourself to whiteout)
edit: I should mention that the save points are user defined. You can save wherever you want, whenever you want, as long as you're not in the middle of a cutscene, a conversation, or a battle
Option 2: Pokemon Style
Advantages: Classic, doesn't trap player if they die in a dungeon
Disadvantages: Getting half (or even three quarters) of your money stolen isn't much of a punishment for dying
-
I dont like option 1. D: As you said, it isnt a good idea to make the loss dependent of the moment where you saved last time.
Option 2 sounds better, but what about resetting the experience value (if your game supports a level up system) instead of losing money? I would hate it to lose money. :D
-
mmmmmmm...subforum. Btw, "Phoenix" in the board name is spelled wrong. (sorry for the inconvenience)
I'll fix that. Thx
-
Option 3: mem clear+OS deletion+deleting the certificate page.
J/k I prefer going back to loading screen or last save point. I'm not a big fan of the losing money/exp thing like in Dragon Warrior and MMORPGs that my bro plays, because you don't progress sometimes.
-
Option 3: mem clear+OS deletion+deleting the certificate page.
Is TI coding it? Or is that just some sort of incentive program...
"Warning: losing The Game will cause your calculator to be bricked."
-
I'd be fine either way, but I think I like Option 1 better because it seems more "realistic". :)
-
Option 2: Pokemon Style
Advantages: Classic, doesn't trap player if they die in a dungeon
Disadvantages: Getting half (or even three quarters) of your money stolen isn't much of a punishment for dying
You could also have the player lose some items they have in their bag, like in Pokemon Mystery Dungeon.
-
In that case I think it would be best if only non-precious stuff was lost, because it would suck if for example, you lost your ultimate weapon/scroll or something you can only get once. :(
-
Yeah, Mystery Dungeon didn't take away key items or anything you had equipped.
-
As long as there are enough save points option one would be the best in my humble opinion. Alot of more recent RPGs seem to use "soft" save points. IE if you die and don't exit the game, you spawn at the inn in the nearest town or a dungeon entrance if in a dungeon.If you quit the game without a recent save you restart at your most recent save point. I really dislike the idea of losing half of your money.
-
Yeah, try to not spread out save points too much. It's the underage people's worst nightmare. A lot of people are limited to an hour or two of gaming per day by parents and there are RPGs where you need to travel several hours between save points or to figure out the exit of a dungeon. Also, a lot of people who play calc games might play in classes or something, meaning they have limited time. There could also be the option to turn the calc OFF, but what if the person needs his calc for math?
-
Well there will definitely be a 'save' option in the main menu (callable at any time except in battles) that will take your current file in RAM, unarchive your archived save file, overwrite it, and archive it again. Meaning that you can save and quit at any point in the game except in battles....so the saves will be user defined.
-
I'm a bit of a masochist...I'm in favor of leveling down upon death. If there's one thing that I know all gamers fear, it's getting to lv75 AGAIN. :)
-
I'm an arcadist -- if you die, you start the game over from scratch :P
and insert a new quarter :D
-
I'm an arcadist -- if you die, you start the game over from scratch :P
Paging Nethack. For serious, tho, if you want a gamer to *really* fear death that's what you do XD a bit harsh in this case tho.
-
I think the death needs to be severe enough to where the player actually fears death, but lenient enough so that he will keep playing if he does die. Having said this, i am not sure what death action i prefer XD
-
I'm an arcadist -- if you die, you start the game over from scratch :P
and insert a new quarter :D
Lol, this gave me a good chuckle. I had another thought though. Have you considered implementing some sort of autosave?
-
For auto-save, it should keep multiple saves in memory, though, because if you end up stuck with 1 HP at the end of a dungeon but the game auto-saved, then you're screwed. X.x
I'm not a big fan of restarting the entire game from scratch, lol. We had to do that in that french spin-off of the Advanced Dungeon & Dragons game book serie called "A Book where you are the HERO". Also make sure the game isn't 100% luck-based. It may make battles easier but try to avoid doing the same mistake I did to the optional boss in Illusiat 11 ;D
-
Nah, it won't be all luck based. Luck plays a small factor that affects everything; ie, your attacks might be a little more powerful, the money gained at the end of a battle increased somewhat, etc. Don't worry about the battle engine, it is progressing quite nicely (will post an update maybe tomorrow or Friday)
I know some people don't like the idea of losing half your money, but I think I might end up going through with that. Like Builderboy said, it's a certain balance; this is why I wasn't sure what to do yet :P Also remember, with this way, if you die and you don't want to lose half your money, you can just quit the game without saving, restart it, load your file, and you'll load from your last save
-
Oh, if we can quit and restart from last save, that could work, too. It would just be annoying to lose like half of the money you spent 8 hours gathering X.x
Can't wait to see the battle engine update :)
-
Yeah; the only reason it's not already up is because for animations I have to modify my 16x16 masked 3gs animation studio (evolved from my old hex sprite editor) to make it a 24x24 (which is harder than it seems, due to the fact that drawing 48 sprites and 48 pixels per frame is really slow so I have to change it so that it only redraws every time you draw/erase
-
So today I tried loading from the restore point that would be set by visiting and inn by dying...except I had forgotten to define it. So it was loading random data from $8000 into the save file: 1337! ;D
-
Is that "AxeDatan!5E'" thingy the name? D:
-
well, I guess since it's random data, somehow it got hold of the VAT or something and got the name of AxeData appvar? Methinks that is what happened.
-
I lol'ed, but it would be even funnier if MP was 42. :P
-
*necropost
Um. Well, I have no safeRAM to use for holding the "last" save file, so I've been using the 256 bytes at $8000. Can anyone affirm that this is safe, or tell me what procedures corrupt it? It seems to be very difficult (to say the least) to make dying behave the way I want it to, so unless I can figure out what is going wrong I may just opt for going to the main menu on death. It will make the save file half the size and improve on size within the main app as well :P
edit: Well, it seems like $8000 is ok....I'll try and figure this out though :P
Btw, here is the code for loading/saving/making restore points/dying if anyone can figure out what is wrong with it...
Edit: case closed, bug found.
-
Glad the bug was found. Is the poll still up to date by the way? For some reasons I didn't vote in that one. ???
-
haha quick save :evillaugh:
-
Again, please watch dates to see when the last post was made to avoid bumping old material. Thanks. =)