Chaosforge Forum
DoomRL => Discussion => Topic started by: Kornel Kisielewicz on July 18, 2009, 13:04
-
Well folks, the time has come to break player.dat compatibility. While that is a sad news in itself ( the older player.dat's won't be compatible ), this is your chance to request for things that will be in the new one! Except for general discussion on what you would like to see ( assume, that player.dat DOESN'T exist now ), I'd like you to post new ideas, and link old ideas into this thread. I'll be using this thread as a reference as I do that.
And yes, some of you may have already heard the news -- the next version will be 0.9.9 ;).
-
In stats:
Total damage dealt
Total damage taken
-
New section:
List of uniques found
List of special levels beaten
In stats:
Number of 100% kills victories
-
In stats:
-Kills made with weapon X for each normal weapon - preferably also split per monster as currently
-As above but for uniques - assuming it can be done without spoiling the unquest prematurely and assuming this won't make the coding hell. If that is too much adding category "unique weapon" to the above will suffice.
-Achievements and/or medals as proposed here (http://forum.chaosforge.org/index.php?topic=1278.0) and here (http://forum.chaosforge.org/index.php?topic=1466.0)
-Number of deaths by cause X (as in: "Geee it's the former humans that kill me the most")
-Number of times you visited special level X
-Just for laugh: Total count of turns spent playing DoomRL ever along with Doom-time equivalent (Not sure if this wouldn't eventually wrap around after sufficient number of plays though)
Edit: Also, this (http://forum.chaosforge.org/index.php?topic=1480.0) topic looks relevant to the whole breakage idea.
-
Just for laugh: Total count of turns spent playing DoomRL ever along with Doom-time equivalent (Not sure if this wouldn't eventually wrap around after sufficient number of plays though)
Well I for one can hardly see why this would happen... Since ten turns = 1 second, the computer should be able to take any number of turns and convert them into hours, minutes and seconds...
As for the "kills made with uniques" idea, one could simply combine this with "list of uniques found" so that it gets set up like this...
Unique name: Blaster ??? Phaseshift boots
Times found: 1 ??? 2
Total kills with this item: 83 ??? N/A
Former human kills: 51 ??? N/A
Former sergeant kills: 26 ??? N/A
And so on... Note that the questions marks (obviously) would represent a unique that the player hasn't found yet...
-
Note that the questions marks (obviously) would represent a unique that the player hasn't found yet...
Why not just not show them? Surely that would make more sense...
-
Note that the questions marks (obviously) would represent a unique that the player hasn't found yet...
Why not just not show them? Surely that would make more sense...
Well Malek reckoned that the uniques shouldn't be spoiled in this way if it could be avoided...
-As above but for uniques - assuming it can be done without spoiling the unquest prematurely and assuming this won't make the coding hell. If that is too much adding category "unique weapon" to the above will suffice.
-
What? No. I meant only showing the uniques you found, nothing more, nothing less. You can spoil yourself enough by looking at the wiki...
-
What? No. I meant only showing the uniques you found, nothing more, nothing less. You can spoil yourself enough by looking at the wiki...
Oh, I get what you're saying now... Well, I thought it might be nice if a player who doesn't want to spoil himself could at least see how many uniques he still has left to collect...
-
I think that would require a screen size larger than 80x25. ;)
-
I think that would require a screen size larger than 80x25. ;)
Or simply more than one page... To be fair, there's quite a fair bit of infomation on the player info pages that we have already...
-
I think this idea could work. Same basic concept, but fits into the 80x25 format well enough.
Unique Times Found Enemies Killed With Times Died With
---------------------------------------------------------------------------
Blaster 2 473 1
Pancor Jackhammer 2 367 2
Gothic Armor 2 N/A N/A
Hell Staff 1 N/A 0
Missile Launcher 1 37 1 (1 suicide)
Railgun 1 4 1
Similar idea for what enemies were killed by what weapons soon.
Edit: Idea made.
Former Human
Weapon #Killed By #Players Died With
-------------------------------------------------------
Fists 236 12
Combat Knife 428 4
Chainsaw 982 1
Butcher Cleaver 152 1
Pistol 578 14
Gramatton Beretta 73 0
Trigun 49 0
Anti-Freak Jackal 54 0
Shotgun 693 43
Combat Shotgun 973 27
Double Shotgun 435 15
Assault Shotgun 26 0
Pancor Jackhammer 73 0
-
Actually 80x25 isn't necessarily a limit - as mortem displayed at end of the game proves it is possible to make a scrollable screen. The question is how much work that would mean for Kornel though.
-
I was speaking horizontal limits, mostly. And I never doubted you could make console scrolling - have you ever looked at Linux's 'less' command?
-
Actually I'm thinking about vertical scrolling for some pages :)
-
So, it has finally happened:
17:19 < CIA-1> doomrl: epyon * r553 /trunk/src/ (dfbeing.pas dfhof.pas dfplayer.pas doombase.pas): * player.dat is no more... ( closes #20 )
This is so exciting :D/me giggles like a schoolgirl
-
R.I.P player.dat... We loved you. ;_;
(Aww well, I keep my old versions anyway; In case a genious converter or so will be created :)
-
Real-life time played (this would be really really nice)
# of keypresses
-
Real-life time played (this would be really really nice)
# of keypresses
Whilst the first one would be nice, the second just strikes me as a pointlessly massive number...
-
Especially if you just started playing AoB. And would it filter out fist-pounding? If not, then the number might be a bit too big. Just a bit, though. :P
-
I think that list of uniques (with the "times found" number, and, i guess, with description of that unique) should be stored in one list, while amount of kills with each weapon (unique weapons too) should be stored in another. It won't spoil anything because weapons should appear in "amount of kills list" only in the amount is more than 0. Also that would be good because uniques that are not weapons (so with which you cannot kill anyone) won't have a permanent 0 in "amount of kills with this item" - otherwise it would be a design failure. Uniques that were not found should appear in the list, but should have "not found yet" in all the values. Because it won't hurt anyone to know, how much of them are left to find. Imagine that you have a list of all uniques except, for example, the Railgun. But you don't know either you found everything, or if there are anything left. While, if you would know that there is one left - you would have bigger motivation to search for it.
How to represent table of "Amount of kills"? It seems to me that the best way is to place monsters in the columns and weapons in the rows. Like that:
Weapon\Monster Former human Former Sergeant
-------------------------------------------------------
Fists 236 12
Combat Knife 428 4
Chainsaw 982 1
Butcher Cleaver 152 1
Pistol 578 14
Gramatton Beretta 73 0
Trigun 49 0
Anti-Freak Jackal 54 0
Shotgun 693 43
Combat Shotgun 973 27
Double Shotgun 435 15
Assault Shotgun 26 0
Pancor Jackhammer 73 0
To see monsters that are to the right - make "right arrow" key to scroll one monster at a time to the right (not one line of characters at a time) and make weapon names always visible to the left (fixed, so only amount of kills and monster names would scroll when scrolling right). Same for vertical scrolling. To avoid low amount of kills per view - i have one idea. Abbreviate long names into several letters that are distinguishable from each other and make some moving cursor in the shape of the cross (so it would highlight current row and current column). And that current row and current column would be larger that the ones that are not highlighted (large enough to show full name of monster at the top and the full weapon name to the left). Like that:
Wea\Mon FH Former Sergeant FCp
-------------------------------------------------------------------------------------
Fis 236 12 456
CKn 428 4 645
Chsw 982 1 6
ButCle 152 1 6
Pstl 578 14 456
GrmtBer 73 0 45
Trig 49 0 456
Ant-F J 54 0 65
Shtg 693 43 48
C Shtg 973 27 347
D Shtg 435 15 15
Assault Shotgun 26 0 0
PanJck 73 0 0
Well, now i see that with monster names such thing works, while with weapons that produces only a waste of space. Well, we could output full weapon names, but at least make current monster highlightable.
-
Huzzah! Progress has been made!
Now, to rid myself of Player.dat...
whaddya mean, "It's not public yet"?!?
-
Just a reminder that this is a HOT TOPIC -- new player.dat is implemented as I write this ;).
-
Whatever you decide to track (real life time, pleeeeeeease!), could you also include per-game tracking of the same details in the mortem.txt?
-
How about in addition to how many of each monsters have been killed, also how many of each have spawned, and how many of each were resurrected?
# of small medpacks used. Large ones too. Phase devices as well.
# of powerups used, for each type. # of powerups spawned.
Amount of damage dealt to enemies, separated by source (per weapon, lava, barrels, other enemies)
Amount of damage taken by doomguy, by source
Amount of damage eaten by armor, by source
# of times each weapon type/unique was fired. # of times enemies fired.
# of times player moved in each of 8 directions? Haha, I guess I'm starting to stretch things.
Average spawn distance to stairs?
Special levels entered or skipped, cleared to what degree.
(The thing is, I'd rather have a new version earlier with less stat tracking and badges/ranks/etc than a longer wait with more bells and whistles in the 'achievements' realm.)