Nimin Contest: You make an event!
14 years ago
General
As mentioned in the Aftermath journal, I won't be doing much in terms of new events myself for the next release, however you, the players, will get the chance to do a full event!
Synopsis - Instead of only being able to make prostitution scenes, one or two of you will be able to have your own full event (including button options, multiple paths, and even item rewards) in the game. I will be choosing the "best" (and maybe "second best") events to go into the game for everybody else to play. This is your chance to exercise your creativity in a game that many people seem to love!
Details
What and Where
You would be completely writing a full event. The event would be for Tieden (in Tieden, as a random exploration). It would be a "big" event, like Lila and Malon, where it can potentially have a unique character or two (but it doesn't necessarily have to, if you can come up with something else). It should also involve knots somehow, as that is a key lupan feature.
How an event works
Essentially, it's modular based on variables.
For instance, with Lila, I have a lilaRep variable (Lila Reputation) that progresses based on certain actions, and what you see is based on what your lilaRep is. So, you start out at 0 lilaRep, you'll see the introduction encounter, and it can go to 1 or 2 based on what path you choose. At lilaRep 1 you have different buttons and text than lilaRep 2, and those can lead to even other reputation values and even more options. It's the way it tracks the "choose your own path" kinda things, like those books for children.
Also with Lila, she has lilaVulva and lilaMilk variables to account for the "changing" portions. These I use to output different descriptions of her based on what those different variables are, such as "if lilaVulva is between 2 and 5, say X". There's also a lilaPreg to track her pregnancy.
As for how the event actually proceeds, it's a lot like how the prostitution events function, except for one main difference: buttons. You can specify what each button says and what happens when they're selected, leading to far more branching and progression than you can get with just a prostitution scene. You can have the buttons change as the event progresses, or you can have the buttons remain the same and have their results change as the event progresses, or any possible combination you can think of.
You just have to say "if this variable is this much, do that" (if exRep < 2, do this) and "if button 1, do that" and specify which buttons have which text.
What you need to do
The event must be accessible by all genders (male, female, herm, genderless), but it may have prerequisites to start the "quest line" and can have gender-specific prerequisites to progress the quest line. However, progressions of the quest line, even if they had gender-specific prerequisites, still have to account for all genders. Even though it could require a cock to progress the quest, the player may have lost the cock later and the quest has to be able to handle it. This means giving me different text for each of the possible genders if that gender can access the selection (for example, if everybody can have sex, you have to account for cocks, vaginas, or the lack thereof). I'm sure you can glean what I mean by the events already in the game.
You need to have a complete event. You cannot just give me an idea and expect me to write it for you, or finish half the event yourself and leave the rest to me. I will read through it and convert it to code, that's all.
What you can do
You can track up to 10 variables for your event. I ask that you try to keep it efficient, not having a variable that is used once for one single line and is unused otherwise. You can also have up to 3 of those variables being tracked outside of the event. For instance, the lilaPreg variable changes based on how much time has passed, and is thus tracked outside of the event with other time-based variables.
You can have up to 6 items as rewards for your event. These do not have to be available for all paths of the event (for instance, if you go down one path you might not be able to access certain items anymore). You also have to clearly state what they do and write out the text that would be shown when you use them.
You can essentially create the Tieden lifestyle and environment in your event, since I have not gone into it myself.
What you can't do
You are not allowed to use a non-lupan race in your event, unless you make a unique race available in Tieden that's not available to players (and even then it's iffy). You also cannot have any racial transformations for the player outside of lupan transformations. You may potentially change the race of an NPC within the quest, however.
You can't include gore, scat, fat, or sex with old people. This is a personal preference that I maintain within the game.
How to submit your event
You may submit your event via note to me. However, since I'm sure it would be quite massive, you would probably be better off sending the .txt/.rtf/.doc file to me via email at xadera1[at]yahoo.com . Please no pdfs or docx or other filetypes.
If you want to send me a rough outline in advance, or general idea, to see if I would accept it before you start writing it all out, you're free to send it to me via note or email, or even in a comment below if it's short enough to fit.
How they will be judged
Since not all of the events will be used, I will be judging them to determine which would be best in the game. Creativity, originality, and innovation are all big pluses. If I don't think it would fit well in the game or it takes too many liberties (giant robot monsters battling in space, wat?), I probably won't take it. But, most importantly think about and read your own work. I will probably toss any submissions that are too hard to read to bother fixing, filled with too many typos and grammatical errors, has impossibly complicated logic (code wise), and/or reads like an immature ill-conceived fanfic.
Deadline
You have 1 month to submit the fully completed event! That means you have until November 15th, 2011. If you are interested in submitting, trust me, you'll probably need the whole month.
After the 15th, I will notify potentially decent events about changes they could make for a better chance. You will have a week to make those or any other changes you see fit. After that week, I will choose one or two winners, finish up whatever fixing needs to be done, and have it ready for the next release, whenever that is.
Reward
You have your own idea in the game? Idk, this contest is for you guys, not me. If there are no usable events by the time the deadline is up, I'll just create one myself later down the road.
UPDATE: Thanks to a generous donation, there is now a monetary prize as well! If you win, you get $15 via paypal! Or, if 2 submissions are accepted, each person gets $10 ^^ If you don't have Paypal, I could also transfer the money to Steam to buy you an appropriately valued game instead =3
Things I forgot to mention
I don't know yet, I just made this journal!
Synopsis - Instead of only being able to make prostitution scenes, one or two of you will be able to have your own full event (including button options, multiple paths, and even item rewards) in the game. I will be choosing the "best" (and maybe "second best") events to go into the game for everybody else to play. This is your chance to exercise your creativity in a game that many people seem to love!
Details
What and Where
You would be completely writing a full event. The event would be for Tieden (in Tieden, as a random exploration). It would be a "big" event, like Lila and Malon, where it can potentially have a unique character or two (but it doesn't necessarily have to, if you can come up with something else). It should also involve knots somehow, as that is a key lupan feature.
How an event works
Essentially, it's modular based on variables.
For instance, with Lila, I have a lilaRep variable (Lila Reputation) that progresses based on certain actions, and what you see is based on what your lilaRep is. So, you start out at 0 lilaRep, you'll see the introduction encounter, and it can go to 1 or 2 based on what path you choose. At lilaRep 1 you have different buttons and text than lilaRep 2, and those can lead to even other reputation values and even more options. It's the way it tracks the "choose your own path" kinda things, like those books for children.
Also with Lila, she has lilaVulva and lilaMilk variables to account for the "changing" portions. These I use to output different descriptions of her based on what those different variables are, such as "if lilaVulva is between 2 and 5, say X". There's also a lilaPreg to track her pregnancy.
As for how the event actually proceeds, it's a lot like how the prostitution events function, except for one main difference: buttons. You can specify what each button says and what happens when they're selected, leading to far more branching and progression than you can get with just a prostitution scene. You can have the buttons change as the event progresses, or you can have the buttons remain the same and have their results change as the event progresses, or any possible combination you can think of.
You just have to say "if this variable is this much, do that" (if exRep < 2, do this) and "if button 1, do that" and specify which buttons have which text.
What you need to do
The event must be accessible by all genders (male, female, herm, genderless), but it may have prerequisites to start the "quest line" and can have gender-specific prerequisites to progress the quest line. However, progressions of the quest line, even if they had gender-specific prerequisites, still have to account for all genders. Even though it could require a cock to progress the quest, the player may have lost the cock later and the quest has to be able to handle it. This means giving me different text for each of the possible genders if that gender can access the selection (for example, if everybody can have sex, you have to account for cocks, vaginas, or the lack thereof). I'm sure you can glean what I mean by the events already in the game.
You need to have a complete event. You cannot just give me an idea and expect me to write it for you, or finish half the event yourself and leave the rest to me. I will read through it and convert it to code, that's all.
What you can do
You can track up to 10 variables for your event. I ask that you try to keep it efficient, not having a variable that is used once for one single line and is unused otherwise. You can also have up to 3 of those variables being tracked outside of the event. For instance, the lilaPreg variable changes based on how much time has passed, and is thus tracked outside of the event with other time-based variables.
You can have up to 6 items as rewards for your event. These do not have to be available for all paths of the event (for instance, if you go down one path you might not be able to access certain items anymore). You also have to clearly state what they do and write out the text that would be shown when you use them.
You can essentially create the Tieden lifestyle and environment in your event, since I have not gone into it myself.
What you can't do
You are not allowed to use a non-lupan race in your event, unless you make a unique race available in Tieden that's not available to players (and even then it's iffy). You also cannot have any racial transformations for the player outside of lupan transformations. You may potentially change the race of an NPC within the quest, however.
You can't include gore, scat, fat, or sex with old people. This is a personal preference that I maintain within the game.
How to submit your event
You may submit your event via note to me. However, since I'm sure it would be quite massive, you would probably be better off sending the .txt/.rtf/.doc file to me via email at xadera1[at]yahoo.com . Please no pdfs or docx or other filetypes.
If you want to send me a rough outline in advance, or general idea, to see if I would accept it before you start writing it all out, you're free to send it to me via note or email, or even in a comment below if it's short enough to fit.
How they will be judged
Since not all of the events will be used, I will be judging them to determine which would be best in the game. Creativity, originality, and innovation are all big pluses. If I don't think it would fit well in the game or it takes too many liberties (giant robot monsters battling in space, wat?), I probably won't take it. But, most importantly think about and read your own work. I will probably toss any submissions that are too hard to read to bother fixing, filled with too many typos and grammatical errors, has impossibly complicated logic (code wise), and/or reads like an immature ill-conceived fanfic.
Deadline
You have 1 month to submit the fully completed event! That means you have until November 15th, 2011. If you are interested in submitting, trust me, you'll probably need the whole month.
After the 15th, I will notify potentially decent events about changes they could make for a better chance. You will have a week to make those or any other changes you see fit. After that week, I will choose one or two winners, finish up whatever fixing needs to be done, and have it ready for the next release, whenever that is.
Reward
You have your own idea in the game? Idk, this contest is for you guys, not me. If there are no usable events by the time the deadline is up, I'll just create one myself later down the road.
UPDATE: Thanks to a generous donation, there is now a monetary prize as well! If you win, you get $15 via paypal! Or, if 2 submissions are accepted, each person gets $10 ^^ If you don't have Paypal, I could also transfer the money to Steam to buy you an appropriately valued game instead =3
Things I forgot to mention
I don't know yet, I just made this journal!
FA+

I might note you if anything comes to mind.
Plus things being ridiculous is always funny. :3 And having the size of a knot count as it's own thing may make some people happy.. hehe
Lemme play Schedule Shuffle and see if I can come up with anything submittable by the deadline. Got a couple of ideas, anyways.