Open Chain Level

klisse · Post by **klisse** » 19 May 2008, 09:38

Open chain level

Been a while since last chain level now, but I guess nobody orka arrange such a thing anymore just because it's to much effort to nag on kuskis all the time. So way not make it open without any dictators,rules or list of people waiting for doing their part?

How could this possible work, it takes just one idiot to ruin it all? Not at all if we create a system to avoid it!
The only rule we need is that designers upload a correct named level (based on the version system defined below) to moposite. If some idiot e.g. uses all objects, just create a new subversion the level you like and the chain continues.

So here is the one and only rule:
- Name your level like this C_<version_number>#<count>.lev and upload it to moposite when ready (long filenames allowed), include also the new tree in your post. If you fuck this up hopefully someone may correct it.

Anyone understand that? I guess not... So here is an example.

Levname will be consists of <parent_levname> and <number_version_of_daughter_lev>. for example:

1 - Abul@ create first part (C_1)
2 - Jonn Create second part (C_1#1)
3 - pex didn't like Jonn's part but liked Abul@'s and therefore he continue on Abul@'s part (C_1#2)
4 - Sworgy, Jq and n00b continue on pex part. (C_1.2#1, C_1.2.1#1, C_1.2.1.1#1)
5 - Sweq liked Jonn's part and continued the Jonn-chain followed by "Fucker" that used all objects(C_1.1#1)
6 - But Ralli really liked Sweg's part and continue Jonn-chain followed by BÃ¶rn, Ram1 and Marcku (C_1.1.1#1, C_1.1.1.1#1, C_1.1.1.1.1#1, C_1.1.1.1.1.1#1)
7 - Pinkong didn't like Marcku's part and continued on Ram1's chain (C_1.1.1.1.1.1#2)
8 - "Fucker" created another based on Jonn's part that nobody liked (C_1.1#2)
9 - Lukace didn't like Abul@'s part and created new first part, he liked it so much that he continued it himself (C_2)
10 - Ram1 liked Lukace first part and continued it (C_2#1).

Code: Select all

C_1 - Abul@
C_1#1 - Jonn
C_1.1.1#1 - Ralli
C_1.1.1.1#1 - BÃ¶rn
C_1.1.1.1.1#1 - Ram1
C_1.1.1.1.1.1#1 - Marcku
C_1.1.1.1.1.1#2 - Pinkong
C_1.1#1 - Sweq
C_1.1#2 - Fucker
C_1#2 - pex
C_1.2#1 - Sworgy
C_1.2.1#1 - Jq
C_1.2.1.1#1 - n00b
C_2 - Lukace
C_2#1 - Ram1

If you want that others should continue your chain I guess it's common sense not to change others part to much, use to many objects or make your part to difficult. But it's all up to you!

Hopefully this will work out, lets see who will make first part? ...or comment the idea.

insane guy · Post by **insane guy** » 19 May 2008, 12:53

I dont understand the rules at all, but making first part seems ez.

there you go:

klisse · Post by **klisse** » 19 May 2008, 14:42

insane guy wrote:I dont understand the rules at all, but making first part seems ez.

there you go:

Excellent!
Here is the version tree so far.

Code: Select all

C_1#1 - insane guy

Ok, one more example if last was to complicated.

If insanse guy's part is ok, next contributor should upload C_1#2.lev (update count after #) and so on.
If someone mess up his part, lets say that jappe makes a to hard pipe part and upload it to C_1#2.lev. next contributor should "subversion" insane's part C_1#1 -> C_1.1, add a counter C_1.1#1.lev and continue his part.

This go on forever, or lets say to the deepest version tree count is 10? (10 designers in one chain)

Version tree example:

Code: Select all

C_1#1 - insane guy
C_1.1#1 - BÃ¶rn (or someone else makes his part after jappe messed up big time)
C_1#2 - jappe  (sick pipe part)

Kale · Post by **Kale** » 19 May 2008, 14:58

C_1#2.lev: (8.09 KiB) Downloaded 209 times

There it goes. I made it in a bit of a hurry cause i wanted to make it before someone else does

Guess it's OK. Also added text "Insguy" under the start of insguy's part.

Mawane · Post by **Mawane** » 19 May 2008, 16:23

I'm currently making a Chain Pipe level with Jappe, Pab, barryp and tubby without this system and it works fine.

Igge · Post by **Igge** » 19 May 2008, 16:55

Continued on insguys lev.

Code: Select all

C_1#1 - insane guy
C_1.1#1 - igge
C_1#2 - Kale

i think

btw, i will have to edit my name later, but that should be ez fixable, right?

oh, and didnt change the lev title, but that can't matter, right?

error · Post by **error** » 20 May 2008, 05:42

i want will be in :X
i want make any part :S

Coc0k · Post by **Coc0k** » 20 May 2008, 08:13

nice idea

Coc0k · Post by **Coc0k** » 20 May 2008, 14:47

Code: Select all

C_1#1 - insane guy
C_1.1#1 - igge
C_1#2 - Kale
C_1#3 - Coc0k

Kale · Post by **Kale** » 20 May 2008, 16:40

YOU'RE DOING IT WRONG , coc0k

FinMan · Post by **FinMan** » 20 May 2008, 18:12

I have sum sax graphig cards etc. in this computer (Ye, now im teh "FinMan_CrapComp"

) but ill try some.

Coc0k · Post by **Coc0k** » 21 May 2008, 06:49

Kale wrote:YOU'RE DOING IT WRONG , coc0k

what?

Igge · Post by **Igge** » 21 May 2008, 07:14

FinMan wrote:I have sum sax graphig cards etc. in this computer (Ye, now im teh "FinMan_CrapComp" ) but ill try some.

i think that if you continued on insguys lev, name would be C_1.1.1#1 (don't blame me, not my idea)

Coc0k · Post by **Coc0k** » 21 May 2008, 08:08

i propose to change the rules. levname will be consists of <parent_levname> and <number_version_of_daughter_lev>. for example:
1 - Abul@ create first part (C_1)
2 - Jonn Create second part (C_1#1)
3 - pex didn't like Jonn's part but liked Abul@'s and therefore he continue on Abul@'s part (C_1#2)
4 - Sworgy, Jq and n00b continue on pex part. (C_1.2#1, C_1.2.1#1, C_1.2.1.1#1)
5 - Sweq liked Jonn's part and continued the Jonn-chain followed by "Fucker" that used all objects(C_1.1#1)
6 - But Ralli really liked Sweg's part and continue Jonn-chain followed by BÃ¶rn, Ram1 and Marcku (C_1.1.1#1, C_1.1.1.1#1, C_1.1.1.1.1#1, C_1.1.1.1.1.1#1)
7 - Pinkong didn't like Marcku's part and continued on Ram1's chain (C_1.1.1.1.1.1#2)
8 - "Fucker" created another based on Jonn's part that nobody liked (C_1.1#2)
9 - Lukace didn't like Abul@'s part and created new first part, he liked it so much that he continued it himself (C_2)
10 - Ram1 liked Lukace first part and continued it (C_2#1).

Code: Select all

C_1 - Abul@
C_1#1 - Jonn
C_1.1.1#1 - Ralli
C_1.1.1.1#1 - BÃ¶rn
C_1.1.1.1.1#1 - Ram1
C_1.1.1.1.1.1#1 - Marcku
C_1.1.1.1.1.1#2 - Pinkong
C_1.1#1 - Sweq
C_1.1#2 - Fucker
C_1#2 - pex
C_1.2#1 - Sworgy
C_1.2.1#1 - Jq
C_1.2.1.1#1 - n00b
C_2 - Lukace
C_2#1 - Ram1

Coc0k · Post by **Coc0k** » 21 May 2008, 08:10

so, we have

Code: Select all

C_1 - insane guy
C_1#1 - Kale
C_1#2 - Igge
C_1#3 - Coc0k

Kale · Post by **Kale** » 21 May 2008, 14:11

A lot more clear. Still too hard to understand, tho.

klisse · Post by **klisse** » 21 May 2008, 15:29

Coc0k wrote:so, we have
Code: Select all
C_1 - insane guy
C_1#1 - Kale
C_1#2 - Igge
C_1#3 - Coc0k

Nice, this will fix the bug from last rule. I will update first post.

FinMan · Post by **FinMan** » 21 May 2008, 19:54

Elma doesnt work well in that computer seems. Someone other will make level first

klisse · Post by **klisse** » 21 May 2008, 20:34

I should add a part also..

Code: Select all

C_1 - insane guy
C_1#1 - Kale
C_1#2 - Igge
C_1#3 - Coc0k
C_1.3#1 - klisse

Coc0k · Post by **Coc0k** » 22 May 2008, 07:20

klisse wrote:I should add a part also..
Code: Select all
C_1 - insane guy
C_1#1 - Kale
C_1#2 - Igge
C_1#3 - Coc0k
C_1.3#1 - klisse

i thought that you could draw left part

klisse · Post by **klisse** » 22 May 2008, 07:38

Coc0k wrote: i thought that you could draw left part

This is anarchy, god save the queen.

Coc0k · Post by **Coc0k** » 22 May 2008, 07:43

klisse wrote:
Coc0k wrote: i thought that you could draw left part
This is anarchy, god save the queen.

why?

Harald Hasch · Post by **Harald Hasch** » 23 May 2008, 03:53

because we are sinners and go to hell. he might show mercy with the queen

Costya · Post by **Costya** » 24 May 2008, 20:49

have these bars and dots any meaning?

C131, for example, is much more comfortable for me

FinMan · Post by **FinMan** » 24 May 2008, 21:15

You can rename it in folder.

klisse · Post by **klisse** » 24 May 2008, 21:30

Costya wrote:have these bars and dots any meaning?

C131, for example, is much more comfortable for me

Yes, they have meaning (atleast the dots). You could for instance name the level C_1.11.1#1 and so on..

Costya · Post by **Costya** » 25 May 2008, 08:03

ok, i'm agree, this mean that levelmakers are nabs and can't design 2nd part properly.

FinMan · Post by **FinMan** » 25 May 2008, 09:45

ill make next part in evening if you ppl want.

I got better comp back

zebra · Post by **zebra** » 25 May 2008, 23:17

Kale wrote:A lot more clear. Still too hard to understand, tho.

I agree. Even though the system does make sense, it is too complicated. There shouldn't exist a situation that a chain lev splits up into two different chain levels.

I suggest the following system:

Let's assume that the chain lev name is 'Fire'. Levels would be named just like Fire01, Fire02, Fire03 etc. I think we are not so strict that we would just abandon the previous maker's part. If you don't like it, just edit it and make it a little bit better. That's the way it wouldn't split into two different versions.

To prevent a situation that two different designers are designing the level at the same time: If you want to make the next part of the lev, say something like 'me next' in this topic. Then everybody else knows that you are making the next part, and can give you few days for finishing it. Let's say that you should post your level in the topic in 5 days, otherwise someone else can continue the level.

And if there still happens a situation that two designers have edited the level in the same time, then the one who is slower (who hasn't yet posted his lev to lauta) should somehow merge their edits. That's not going to be easy thing but maybe somehow possible with ALE. But that kind of situation shouldn't occur if everyone just remembers to tell beforehands that he's gonna edit the level next.

You could also make reservations, like making a 'me next' post after someone has already said 'me next'. In this case, editing of your post (adding the level to the post where you said 'me next') would be appropriate to keep the time line clear.

And, if there are many chain levels open at same time, it would be the best way to have different thread for each.

Ok that's just a suggestion, but I think that's one which everyone could understand. You could rename the level in elma and no fear that the levelname would exceed 8 characters (when you can't open it in elma anymore).

Grace · Post by **Grace** » 26 May 2008, 13:07

zebra wrote:
Kale wrote:A lot more clear. Still too hard to understand, tho.
I agree. Even though the system does make sense, it is too complicated. There shouldn't exist a situation that a chain lev splits up into two different chain levels.

I suggest the following system:

Let's assume that the chain lev name is 'Fire'. Levels would be named just like Fire01, Fire02, Fire03 etc. I think we are not so strict that we would just abandon the previous maker's part. If you don't like it, just edit it and make it a little bit better. That's the way it wouldn't split into two different versions.

To prevent a situation that two different designers are designing the level at the same time: If you want to make the next part of the lev, say something like 'me next' in this topic. Then everybody else knows that you are making the next part, and can give you few days for finishing it. Let's say that you should post your level in the topic in 5 days, otherwise someone else can continue the level.

And if there still happens a situation that two designers have edited the level in the same time, then the one who is slower (who hasn't yet posted his lev to lauta) should somehow merge their edits. That's not going to be easy thing but maybe somehow possible with ALE. But that kind of situation shouldn't occur if everyone just remembers to tell beforehands that he's gonna edit the level next.

You could also make reservations, like making a 'me next' post after someone has already said 'me next'. In this case, editing of your post (adding the level to the post where you said 'me next') would be appropriate to keep the time line clear.

And, if there are many chain levels open at same time, it would be the best way to have different thread for each.

Ok that's just a suggestion, but I think that's one which everyone could understand. You could rename the level in elma and no fear that the levelname would exceed 8 characters (when you can't open it in elma anymore).

Very Clear and Simple, however, what happens if someone uses all the objects/pictures/polygons and thus creates havoc?

zebra · Post by **zebra** » 26 May 2008, 14:33

SmaXa wrote:Very Clear and Simple, however, what happens if someone uses all the objects/pictures/polygons and thus creates havoc?

I think in that case there are the following solutions:
1) the next designer edits the havoc away
2) the chain lev is finished.

Oh and if the situation is that the user has totally ruined the lev, the next designer can take the earlier version of the level and post it again as a next version. In that case though, at least if the user ruins the level again, a lauta ban would be appropriate.

Grace · Post by **Grace** » 28 May 2008, 08:01

Okies Zeb

good Idea =P

klisse wrote:Open chain level

Been a while since last chain level now, but I guess nobody orka arrange such a thing anymore just because it's to much effort to nag on kuskis all the time.

TeamEF released Split Lev only couple of Weeks ago.

Ali · Post by **Ali** » 23 Jun 2008, 18:55

hey, lets do what zebra said

OPEN CHAIN LEVEL:

Rules:
1. Download lev from lauta
2. Announce on lauta that you are making another part ('me next')
3. Add your part
4. Post lev on lauta along with chain table (= list of levelmakers)

Notes:
- levname OpenCxx.lev (xx = number of your part)
- make your part short (less than 20 secs)
- make your part finishable (place flower at the end of your part)
- don't mess the lev with a lot of objects/pictures/polygons (don't even sign your part)
- if somebody messes his part, next guy will correct it

---------------------------------

Chain table

Code: Select all

OpenC01 - Ali

Mawane · Post by **Mawane** » 23 Jun 2008, 19:15

"me next"

Chain table

Code: Select all

OpenC01 - Ali
OpenC02 - Mawane

Grace · Post by **Grace** » 24 Jun 2008, 08:59

Me Next.

Chain Table:

Code: Select all

OpenC01.lev - Ali
OpenC02.lev - Mawane
OpenC03.lev - SmaXa

Bjenn · Post by **Bjenn** » 16 Jul 2008, 10:59

Me Next!

Chain Table:

Code: Select all

OpenC01.lev - Ali
OpenC02.lev - Mawane
OpenC03.lev - SmaXa
OpenC04.lev - Bjorn

Bjenn · Post by **Bjenn** » 29 Sep 2008, 15:45

Continue plz someone!!

Coc0k · Post by **Coc0k** » 29 Sep 2008, 16:01

me next!

ChainTable:

Code: Select all

OpenC01.lev - Ali
OpenC02.lev - Mawane
OpenC03.lev - SmaXa
OpenC04.lev - Bjorn
OpenC05.lev - Coc0k

Bludek · Post by **Bludek** » 13 Apr 2010, 13:45

me next!

ChainTable:

Code: Select all

OpenC01.lev - Ali
OpenC02.lev - Mawane
OpenC03.lev - SmaXa
OpenC04.lev - Bjorn
OpenC05.lev - Coc0k
OpenC06.lev - Bludek

totem · Post by **totem** » 13 Apr 2010, 13:52

ok me next then