FireMage on 4/7/2013 at 16:16
It seems that we left the Halloween Theme, yes... A contest before October with YOUR OWN theme...
If we launch the 48 hour contest today, you got the time to launch a Halloween Contest just after because it won't be long and you know why! :cheeky:
Xorak on 6/7/2013 at 04:13
Just throwing this out there, but I wouldn't mind an August start time. That gives a couple weeks of preparation and general mapping on paper, that is, if that's allowed.
Or if someone finds they need to make new textures or creature meshes, they can take a couple weeks to prepare that stuff pre-contest. Because there certainly won't be any time to do it in 48 hours.
Are we settled on a 48 hour contest, 4 days, 7 days...?
FireMage on 6/7/2013 at 12:25
Ok, so, my proposition:
Starting day: 1st August
Contestant sign in and get their base mission.
When they got the base mission, the timer is launched and they got 48hours to create something.
After these 48h (or before) THEY MUST send their mission to the organizers (it might be a team).
The organizers will "TEST" the mission. If they found bugs, they'll send a PM to the author, then he'll have 5 days to fix it.
After these 5 days, the author will send a the fixed mission to the organizers.
When all contestants has created/corrected their missions, they'll be published.
NOTE: If somebody need some extra-days to create a mission, he will get it, but he'll lost some days to fix his bugs.
Example: A contestant X need 1 extra-days to create his mission. The organizers will accept, but he'll have only 4 days to fix his bugs instead of 5.
I think that the best thing to do, isn't it?
DrK on 6/7/2013 at 14:23
Quote Posted by FireMage
Starting day: 1st August
Sounds alright to me, but august 1st is a thursday, I'll be able to work on it during the next weekend, so it should start august 3rd. :p
Yandros on 6/7/2013 at 15:38
I think it's a mistake to make the organizers also the only testers. If turnout is strong they won't have time to test all the entries themselves. You're also effectively still giving 7 days since someone could take the full time and submit without testing, or have it tested externally before submitting. I think the best approach is to just give 7 days and encourage participants to test on their own as much as possible (at Shalebridge for example), but not require submission until the end of day 7.
Renault on 6/7/2013 at 16:06
I definitely think AntiMatter_16 should run the contest (if they're interested and willing), it was their idea after all.
I agree with Yandros on the testing too - whether the contest runs 48 hours, 4 days, or 7 days, let the author handle the entire process for start to finish. That should be part of the challenge of the contest, and then they won't be relying on (or be able to blame) anyone besides themselves for the finished product. I'm also in favor of a good base mission to eliminate all the menial setup work that needs to be done with starting an FM.
FireMage on 6/7/2013 at 21:48
Guys, I'm trying to find "how could we organize such contest".
It's original, not classic, so it's hard to organize.
No offense, but if you always disagree with me when I'm trying to search for an organization, I'll ask the question: When could we launch this contest?
I think that my last idea is good. A jury cannot be worst than a betatest team. It's not because the scene doesn't take place in Shalebridge Cradle that the quality is bad.:thumb:
As we said, the guys could create during 7 days max, but he will have no delay to fix his bugs. So you got the choice!
The organizer CAN BETATEST ALL MISSIONS, because if they are organizers logicaly, they're ready to play all the missions.:cheeky:
And the fixing delay will start when the organizers has finished their test.:cool:
If you really think that it is not a good idea, tell me what could we do REALLY?
Saying "I disagree because or not because" don't help! Because you're just saying what's wrong with my organization, not the good organization to apply.:erg:
Saying "we'll do this" without accuracy as you're doing, we will launch this contest the next century! :rolleyes:
AntiMatter_16 should launch this contest, yes, but does he want to organize first? And what did he think about the organization exactly?:confused:
We need an answer from him where he will tell us what to do. ;)
Yandros on 7/7/2013 at 03:09
Quote Posted by FireMage
The organizer CAN BETATEST ALL MISSIONS, because if they are organizers logicaly, they're ready to play all the missions.:cheeky:
And the fixing delay will start when the organizers has finished their test.:cool:
The second line here I guess makes it fair for the authors, but again, what if the organizer gets 6 missions all on the same day? It just seems like an unnecessary bottleneck to run all the testing through a single person, I don't see the benefit of doing that when there is such a large and willing testing community here. Also multiple testers will almost certainly do a better job than a single tester can do alone. Sorry Jordan, this just doesn't seem like a sound proposition, and I don't understand why you're insisting on doing it this way - it just makes the contest more complicated than it has to be.
Seems like simple is best: We have a 7-day contest, no restrictions other than time, no extensions, and use as much or little of that window for testing as you see fit. A simple contest with a short window, and the author gets to weigh the risk/reward of less testing (more dev time vs. potentially more major bugs) vs. more testing (less dev time vs. a more robust mission).
AntiMatter_16 on 7/7/2013 at 09:15
I'm somewhat hesitant to dedicate my time to running a mission contest, when I've never even participated in a contest before, and I'm not sure what kind of time requirements it would have. And I certainly wouldn't have the time to betatest even one or two missions, unfortunately.
I'd still be inclined to do a 48 hour contest over a 7 day period, where authors state a time when they want to start work, and then turn in a zip of the mission, finished and tested or not after an elapsed 48 hours, but no other restrictions whatsoever. After the week ends, all missions are made available for people to start playing, then vote upon them
The intention isn't so much to create a complete, well thought out, quality mission, so much as to challenge an author to see what they can create in a 48 hour period, and organizing their time and the scope of the mission to meet that challenge. One wouldn't necessarily HAVE to have a completed beta-tested product in order to win the contest either. The main goal would just be to create an interesting environment and fun gameplay for the player. The added benefit would be that an author who's in the middle of a huge production could divert their attention for a couple days to something else for fun, and if inclined, create an improved version later.
FireMage on 7/7/2013 at 09:50
Ok, so, just 48 hours to create a mission and nothing else. :cool:
The simplest things are are the best.:thumb:
Then, no base? no set of multibrush? and no links to get some packs?
I want to help you in the contest if you want, if you think that you won't be free... The only problem is that I WANT to be challenger in such contest... :sweat:
So, If I understood correctly... We start when we want?
You say I'm in, you're put in the list, and your timer is launched?
