It's been the same ~/.rocksndiamonds with whatever been in there, not fresh. It would ask again even if it was the exact same RC and the it's previous run had finished the submission process.
Sorry, you are right; this was a misunderstanding.
When looking at the other thread, filbo's suspicion of leaking file descriptors seem to make a lot of sense; in this case, R'n'D wouldn't be able to write to the setup file anymore (to mark that tapes have alredy been uploaded).
At the time, it was showing this for ALL levels.
Yes, that makes sense if the game cannot read level files anymore!
It's this default level, although I think it should display an error instead of showing a default level.
The problem is that usually not being able to read a level file means that there *is* no level file, or that it's broken. In this case, an error message is indeed displayed (but only in the shell, or in the log file, but not in the game), and a fallback to the "empty default level" is made.
It's 'sand', perhaps I should have looked up what the official name for this before calling it something.
Well, it's all the same. In R'n'D it's called "sand", in EM/EMC it's called either "dirt" or "grass" (depending on graphics, but it's indeed a separate game element with same properties, if I remember right).
A big clue to this default level being shown for all levels, may be in the stdout.txt upload for RC2 post showing it stopping saying "- uploading score tape to score server - uploaded." and started saying something like "Tape NNN: (no level found)"
Yes, if R'n'D cannot read a level file, it uses that default level. The real question is *why* R'n'D cannot read or write any file anymore after 1005 tapes.
I think filbo's suspicion might indeed point into the right direction. Here are some messages from the file "stderr.txt" for RC2:
[WARN] cannot read level '/home/bryan/.rocksndiamonds/levels/Contributions 1995 - 2006/Contributions_2002/rnd_alan_bond/003.level' -- using empty level
...
[WARN] cannot write setup file '/home/bryan/.rocksndiamonds/levelsetup.conf'
So it affects both reading and writing files, but the problem does not occur anymore after restarting R'n'D.
This indeed looks like R'n'D was running out of file descriptors!
I have never seen something like this, but then, uploading thousands of tape files is nothing that happens every day... :-/
