Player will easily choose the wrong number in Character selection, because the count number begins from Slot "1" to Slot "3" instead of "0" to "2". The previous version of OpenKore seems not having this problem. Is it better to change back the previous style?------------ Character selection ------------
# Choice
0 Slot 1: XXX (Acolyte, level 53/40)
1 Slot 2: YYY (Novice, level 9/7)
2 Slot 3: ZZZ (Novice, level 9/7)
3 Create a new character
4 Delete a character
------------------------
Please choose a character or an action.
---------------------------------------------
Enter your answer:
all RO | 2.0.6 | the count number in Character selection
Moderators: Moderators, Developers
-
- Perl Monk
- Posts: 11
- Joined: 22 Apr 2008, 03:46
- Noob?: No
all RO | 2.0.6 | the count number in Character selection
-
- Perl Monk
- Posts: 416
- Joined: 04 Apr 2008, 03:08
Re: all RO | 2.0.6 | the count number in Character selection
i dont see the problem... if people are too stupid to pick the wrong chars its their own fault for not readin properly.
This is not a bug, but works as intended
This is not a bug, but works as intended
-
- Developers
- Posts: 157
- Joined: 04 Apr 2008, 13:33
- Noob?: Yes
Re: all RO | 2.0.6 | the count number in Character selection
I also found it slightly confusing but if you think about it this is the best implementation possible.
Think about all the possible situations. Two characters, one in slot 1 and the other in slot 8, is a great example.
Think about all the possible situations. Two characters, one in slot 1 and the other in slot 8, is a great example.
Oh no.
-
- Perl Monk
- Posts: 810
- Joined: 04 Apr 2008, 17:26
- Noob?: No
Re: all RO | 2.0.6 | the count number in Character selection
It works exactly the same as every other menu. Modify it yourself if starting with 0 is too hard.
cs : ee : realist
-
- Super Moderators
- Posts: 801
- Joined: 06 May 2008, 12:47
- Noob?: No
Re: all RO | 2.0.6 | the count number in Character selection
I second this.Motivus wrote:I also found it slightly confusing but if you think about it this is the best implementation possible.
Think about all the possible situations. Two characters, one in slot 1 and the other in slot 8, is a great example.
Since this is not really a bug, it cannot be resolved either.
One ST0 to rule them all? One PE viewer to find them!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!
One ST_kRO to bring them all and in the darkness bind them...
Mount Doom awaits us, fellowship of OpenKore!