mr asked me to do patch where you can put longer than 8 char names
it was quite ez, only i dont know if i didnt rewrite some memory which i shouldnt:))
i can do it the way that it will be definitely correct but you know, if its not necessary, then i'm lazy, it would be a bit harder
now its quite ez 5 chars update (otherwise it would be some >50)
so the only question is how long do you want those names..
i will release the patch then
Well it's not a very good idea to use >8 chars then, think about a battle for example, somebody uploads a >8 char recname and half of battlers couldn't view it.
Last edited by dz on 17 Dec 2005, 21:18, edited 1 time in total.
mr wrote:Would be nice to use following example of .rec-format in internals:
09mr10304b.rec
so 16 chars is necessary imo (for me 10 enough but there's many longer nicks than mine)
Yes that would be very awesome indeed. But to make it really happen would mean it would need to be spread in a very large scale because of the compability issues. Moposite could be a very useful method to spread it, but we all know that moposite is a bit hesitative with new things such as this.
Elma 2 on the other hand... should already have been released seven times already according to sources so is it even rational to just wait things to happen?
mr wrote:Would be nice to use following example of .rec-format in internals:
09mr10304b.rec
so 16 chars is necessary imo (for me 10 enough but there's many longer nicks than mine)
Yes that would be very awesome indeed. But to make it really happen would mean it would need to be spread in a very large scale because of the compability issues. Moposite could be a very useful method to spread it, but we all know that moposite is a bit hesitative with new things such as this.
Elma 2 on the other hand... should already have been released seven times already according to sources so is it even rational to just wait things to happen?
I agree. Moposite's attitude to patch is important. Personally I don't wait "any" improvements vs. patched Elma in this sector.. I mean replay watching, alo, long filenames etc..
dz wrote:Well it's not a very good idea to use >8 chars then, think about a battle for example, somebody uploads a >8 char recname and half of battlers couldn't view it.
Seems like it will be 15 and supporting also special chars such as _-., etc. Moposite will do a 1.2 release in a few weeks, finally. With these new features.
dz wrote:Well it's not a very good idea to use >8 chars then, think about a battle for example, somebody uploads a >8 char recname and half of battlers couldn't view it.
But they can still rename to 8 chars and then watch, am I right? Not that big problem then I think.
Abula wrote:
Seems like it will be 15 and supporting also special chars such as _-., etc. Moposite will do a 1.2 release in a few weeks, finally. With these new features.
This is very cool indeed. Think of all the lovely rec naming after this patch, that will be very nice. Hm, 15 chars, what kind of info would be ok to fit in it...
LevelnumberNickTime.rec, that will take most of space for players with long nick...
LevelnumberNickTimeDate.rec would be awesome. But 15 is not enough for it if nick has to be long. Other ideas?
there is 20-bytes buffer in elma. subtract 4 bytes for extension and one for null-termination. 20 - 4 - 1 = 15.
if >15 then i guess mila will allocate it in own memory zone so then name-length can be up to 255 characters (limited by findfile-routines here), but it's harder to code.
BaSkG008_01.34.67_8-ball - max 25 chars for me, most often 22, of course can shorten it with a zero less, no dots or sach. A bit longer for longer nicks.
54_01.41.99_8-ball - 18 chars for internals.
If we're increasing the limit at all, why not make it even longer so people can note even more things, like vsync, attempt number, team, nationality or anything else they wish.
let it be long enough to add comments such as "oh shit, i fucked the end up but had perfect middle" or "yeah, nice run but with slow style"
e.g. internal_16_new_wave_01:30:23_kinghias_kt_austria_23.05.2006_17:59_driven_with _start_bounce_middle_hang_and_screwed_end_part_but_all_in_all_i_am_pleased_with_it