[3.1.2v2, Unix] Have existing character, start new one that died, can't access old?

[apeiron]

So I have a character I've been playing for a few days, level 20something. I decide I want to experiment with another class. I start a new character with angband -n. That character dies. Now, I can't seem to be able to access my old character that's still alive. I'd really hate to lose that 20something because, frankly, it's the highest I've ever gotten a character. =\

[SaThaRiel]

Sorry, -n is for a *new* character that will be loaded when starting Angband. Almost the same as you would commit suicide with your existing and start over.

If you want to test out other races/classes use the -u switch instead.

I fear that you old char is gone (mine too because i used -n now too ).

[Magnate]

Sorry, -n is for a *new* character that will be loaded when starting Angband. Almost the same as you would commit suicide with your existing and start over.

If you want to test out other races/classes use the -u switch instead.

I fear that you old char is gone (mine too because i used -n now too ).

I'm afraid that's correct.

-u uses a specified savefile, and leaves any character in the existing savefile untouched

-n uses the original savefile and wipes any existing character.

Ooops.

[fph]

Good to have this feedback, though. This needs to be stated in uppercase, bold blinking letters in the command options help.

[Magnate]

Good to have this feedback, though. This needs to be stated in uppercase, bold blinking letters in the command options help.

Done - added warning to the usage statement as of commit 44f9c61. This will be in nightlies soon.

[SaThaRiel]

Ok, my char is luckily not gone - i forgot the -mgcu option and my GTK interface doesn't seem to work at the moment. So it doesnt start a new char.

I hope the warning is just a clarification and not a blinking, bolded text

[fph]

Done - added warning to the usage statement as of commit 44f9c61. This will be in nightlies soon.

Thanks a lot!