|
|
|
![]() |
|||
|
|||
How about dating them as well?
Like this: DEM_08-23-2009(1).dem |
![]() |
|||
|
|||
Quote:
DEM_20090812_083654.dem |
![]() |
|||
|
|||
+1
|
![]() |
|||
|
|||
Or just name it exactly how autorecorded SourceTV demos are named:
auto-20090326-2244-ff_openfire.dem |
![]() |
|||
|
|||
ah yeah, good point, just use that formatting then imo. would be useful to have some way to distinguish stv and client demos from each other just by looking at the name tho (mb just put something different where stv says "auto").
|
![]() |
|||
|
|||
agree - a step further (separate issue) would be a dialogue at the end of the game to select if you wanted to delete it (knowing you hadn't done anything good). This way you wouldn't end up with a directory full of demos you'll never look at :x
|
![]() |
|||
|
|||
Perhaps such kind of task could be done via lua scripts?
|
![]() |
|||
|
|||
A little late but heres my suggestions for something like this...
This is how I name my demos... ff_2_3_2009_0001 FF for the game, 2_3 for the version number, 2009 for the year, 0001 for the number of the demo. What would be nice is if a txt file of the same name was made at the same time that had all the information in it. Map name Class you played as Any other classes you played as and at what tick you switched to them Team you played on Any other team you played on and at what tick you switched to them And ability to put in any notes from a bind. Bind X "demonote" which brings up a chat like item where you can type in "just had a killing spree of 5 people and got away clean with flag" or what ever you want. and it puts that into the text file with the same name of the demo thats being made at that time with the tick number of when you hit in demonote. It could all just be appended onto the end of the text file so there is no need to worry about what other info is already there. |
![]() |
|||
|
|||
Yeah this is a good idea. I cant find the demo code though.
|
![]() |
|||
|
|||
not wrote here when prematch is over start autorecord etc... btw
|
![]() |
||
|
||
Indeed, prematch is annoying when watching demo's, sometimes there is like 10 minutes pm cause people are so slow. I know you can fast forward but starting when pm ends is a better way to record i think
|
![]() |
|||
|
|||
ah ye thanks for bringing that across from other thread :p
|
![]() |
|||
|
|||
agree `auto-mapname/date/time.dem`
and yea it better start when pm ends or about to end |
![]() |
|||
|
|||
and auto screenshot scoreboard end match.
|
![]() |
|||
|
|||
Would be nice if it could be something like:
Code:
DEMO-20090917-1342-ff_mulch_dm_b2.dem DEMO-20090917-1440-ff_openfire.dem DEMO-20090917-1457-ff_openfire.dem DEMO-20090917-1620-ff_openfire.dem DEMO-20090917-1823-ff_plasma_beta1.dem |
![]() |
|||
|
|||
I don't think you really need to have demo on the front, after all if its a .dem file you know its a demo.
and instead of the time I would prefer to have what number in the series it was and what version it was from. I do like the idea of putting the name of the map right in the demo name but not really needed. I would prefer if there was a text file with the same name as the dem file which would have all the info in it. Name of map. Date and Time it was played. teams you played on and the tick number when you switched to it (just in case you switch teams during the game) Classes you played and the tick number when you switched to it (for same reason above) Maybe a way to leave a little note in the text file via the console "demonote did soemthing at this point or person cheating or what ever" and have that note with the tick number put into the text file. |
![]() |
|||
|
|||
I think that we really just need to fix messagemode so that you can set up a script that will prompt you to put whatever the hell you want as the name of the demo!
|
![]() |
||
|
||
Scripts are not intuitive to this generation of gamers, Quakelive has autorecord enabled by default, new fps gamers are just used to it.
Recap, Scripts are lame, features are good. |
![]() |
|||
|
|||
I almost have this working, but I need to find the right place to start recording on connect.
|
![]() |
Issue Tools |
---|
![]() |