First of all, BASCO always used to be separate from MTC.

Secondly, it was customary to build a 6 seconds start segment onto which others would build. This is to lift the burden of "acquiring initial speed" from the builders, and also to give everyone the same starting conditions. Otherwise, some people will start building in corner, others in the middle, some on the ground, others in the air...

Thirdly, have you even tried building a 10 second track under 1000 coppers?

"2 day building, 5 day judging" is also unheard of; I remember when judging one BASCO for TMN, we did it simply by launching a server with nothing but the submitted tracks on it (protected by password so only judges could enter). The rule of thumb was: if you cannot reach the finish in 3 tries, and make a perfect run in 6 tries, then give it a 0. Like this, we managed to judge some 20 submissions in <3 hours, and that was it. So even if we take into account the international nature of the jury, 5 days timeframe indicates you plan to make the judging too complicated (which is especially strange when compared how quickly and with how minimalistic comments the MTC judges can dismiss a full-blown track which took weeks to build)

All in all - I'm terribly sorry for that, but guys -- Are you sure you're asking the right people the right questions when planning these things??

1000 coppers is indeed quite little



the rest of your post, alcator, is total nonsense and completely unecessary criticism since this format (at least a similar one) has worked very well in tmu...

@Space/Alcator/Tuta: Yes, scenery is part of your job. But the 1000 coppers limit can be expanded and after reading your posts I think it must be expanded; we'll discuss that and I'll inform you as soon as possible.

@Alcator:

... says:
First of all, BASCO always used to be separate from MTC.

I don't see a reason for separating BASCO and MTC. Running both competitions at the same time is simply not possible (organization, users, judges, ...). It would be either BASCO or MTC then. So why not do the BASCO as MTC?

... says:
Secondly, it was customary to build a 6 seconds start segment onto which others would build. This is to lift the burden of "acquiring initial speed" from the builders, and also to give everyone the same starting conditions. Otherwise, some people will start building in corner, others in the middle, some on the ground, others in the air...

Well, everyone does have the same starting conditions - a blank map. I think it will be interesting to see different 'start types'. Besides, I think this has already been done in TMU BASCO as well.

... says:
"2 day building, 5 day judging" is also unheard of [...] 5 days timeframe indicates you plan to make the judging too complicated

No, judging will not be complicated at all, it will be very simple (it's the same system like the one we used successfully in the last BASCOs; the same applies for the timeframe): Judges drive the tracks and just give each one a mark out of 10. Then, depending on how close the scores are, I will pull together a shortlist of a number of tracks for the final vote. Those remaining tracks get played again and the judges place them into their order of preference, which decides on the winner.

broadsword says:
EDIT: What about blockmixing? Allowed or not?
IMHO, it kinda spoils the challenge of building by the terms of the previous builder. Besides, it might make life difficult for the next builder or at least create a huge disadvantage for non-mixers when it comes to overall flow from one part to another if some are mixed and others aren't

In my actual case, i needed a block mix to hide a flickering texture (which occured due to a bug with a normal block and the whole map was build without TM2Unlimiter). You can take a look at this problem in my post at the maniaplanet forum, where i describe my issue with block 4-3-1. In such cases, i think it should be allowed. And about the huge disadvantage for non-mixers. They don't need to use it, why should they. It's possible to create brilliant maps without block mixing (e.g. klovni tech maps).

Tuta says:
1000 coppers is indeed quite little

Dunno why people always say 1000 coppers should be to little? I mean i build multiple 6-7min tracks under 10k coppers. And if there are six parts with coppers over 1000 you reach very fast 7000 coppers and with this you already reach the limit for most low end pc configurations to be able to play the map at all.

dammit! already submitted my track without scenery!



May I edit my part ?

I might just be tired but do we need to squeeze scenery into it too? not another stage for the scenery when all parts are done?

edit:

tcq says:

Tuta says:
1000 coppers is indeed quite little

Dunno why people always say 1000 coppers should be to little? I mean i build multiple 6-7min tracks under 10k coppers. And if there are six parts with coppers over 1000 you reach very fast 7000 coppers and with this you already reach the limit for most low end pc configurations to be able to play the map at all.

wait.. I think I misunderstood the rules now (along with almost everyone else). A completely blank building area is already 1125 coppers.... never thought about that... that means the start coppers limit is 2125 which should be plenty!


still think scenery should be a separate part cause it seems odd like this but whatever

tcq says:

In my actual case, i needed a block mix to hide a flickering texture (which occured due to a bug with a normal block and the whole map was build without TM2Unlimiter). You can take a look at this problem in my post at the maniaplanet forum, where i describe my issue with block 4-3-1. In such cases, i think it should be allowed. And about the huge disadvantage for non-mixers. They don't need to use it, why should they. It's possible to create brilliant maps without block mixing (e.g. klovni tech maps).

I was not talking about any specific case, but about blockmixing in general. Hiding a texture bug seems quite trivial in my eyes - and could probably be done without anybody noticing, even if they tried. (And not hiding it should have no negative effect on your track's score - after all, you can't be penalized for a default shortcoming.)

However, several mixes are not as trivial. If a winning builder has blockmixed in the racing route, there's a risk that the next builder, if he does not blockmix, will end up building a part which doesn't contribute to the track's flow -- or even decreases it -- due to his lack of flexibility in comparison to others, meaning he will be at a disadvantage. In any case, this is ultimately a matter of taste - I am not saying that mixing is better than not mixing or vice versa. Yet my opinion is that not allowing blockmixing might increase fairness between builders not at the mixed stage, but the one thereafter.

But what about scenery? Well, in the last BASCO at least, you were allowed to remove / alter the previous user's scenery (as long as it wasn't game-breaking) to open up space for your new part. I have not done any blockmixing in TM2, but in TMU mixing occasionally rendered blocks impossible to move/remove. If that is also the case in TM2, the builder could make spaces in the editor inaccessible to the next builder. Perhaps they could be removed by blockmixing, in which case it could become yet another advantage/disadvantage between mixers and non-mixers.


Lastly, another question: 00:10.xx or 00:10.00?

maybe split tracks to drift and nodrift?

KekX says:
5. Build your idea for the next stage of the track, adding about 10 seconds to the validation time.

broadsword says:
Lastly, another question: 00:10.xx or 00:10.00?

I would interpret it as 10.xx, because else it would have been up to and not about

awesome theme!