Side Stories: Luka vs All - Group 1

This is Group 1 from the Side Story Luka Vs All. It is going to be made up of a selection of various story.ini files for the side story, all on one page... hopefully without becoming excessively long. Just, in order to create this side story on the site it's going to need sub pages, and ... well, I didn't want to create hundreds of them...

Alright, so the idea here is that I'm creating a side story - on site - it's not finished yet, won't be for a while... but I'm working on it in stages on the site so that people trying to develop side stories of their own can use it as a reference to see both how to create various aspects of their side stories, as well as get image references from in the actual game. In addition to these images, I will be adding a few custom images for the side story, these images are not otherwise available. They're being used because, unlike the actual game / storyline, monsters in this side story are not destroyed / reverted to a lesser state, they're just defeated in a friendly battle and, well - lose. As such, I figured that they'd need a exit picture.

The main page for this story can be found here. It has been suggested that I make the story downloadable in sections as they're completed, which to me sounds like a reasonable idea, so after I complete the pictures section (which allows you to view pictures of the battles / specifically the individual monster images and image references for side story development) I'll start doing that.

Group 1
Group 1 includes the first 12 Monster Girls that Luka will face in his epic battle. It's been split up mainly because I didn't want to have a continued list of all monster girls in one section... Just figured it'd be a really long list... also, this way the story can have other key events happening within the main side story vs just at the start of various battles... should help with redundancy when the story is running, should you lose a battle...

Beyond that, I used groups because I didn't want to put all the battles on individual pages, and I sure couldn't put them all on the same page because - really - that'd be way too long to look at for someone scrolling vs using the navigation menu at the top...

Folder Structure / settings / layout
The folder structure for this is pretty simple... but it's not just one folder so I thought laying it out might help some people...

  - the monster girl quest folder
 *   - the mod folder in your monster girl quest folder
 *   - the folder for my side story
 *   - standard resource directory (custom bg / sprites / sounds / whatever...)
 *   - the folder for the Slime Girl fight (could also be group1\001_slimegirl but I didn't want to get that specific)
 *   - will add more folders as I get to them...
 *   - will add more folders as I get to them...
 *   - will add more folders as I get to them...

001_SlimeGirl

 * This section reflects the folder structure ... It will include the story.ini file as well as any custom stuff required for the folder. (maybe custom graphics and / or sound...) Though this section isn't really 100% needed, I felt it important to show the structure along the way so that someone building a complex side story and following along with this tutorial can see how it works. Also because there will be other folders, organization is key... :)


 * As an extra note, any [section] in square brackets is included in story.ini. Originally I had everything organized in a sub section of story.ini, but I'm thinking it's probably a little too nested so I'm changing that.
 * The story.ini is in sub-folder LukaVsAll\001_SlimeGirl, and could be played on it's own... Every new instance of a command is referenced as [#], click the number and you will be shown the description in your browser. When you're finished, there's another link [↑] which you can click to bring you back to that section in the story.


 * A slight change of plans... I've decided that because this is the first battle in the side story, and that this is taking significantly longer than I'd anticipated; that I'm going to make the Slime Girl battle into something more spectacular. As such, she will no longer be a level 1 monster, instead something much bigger; more to ensure that the battle lasts quite a while. I've already added a number of attacks to Slime Girl's repertoire, in doing so however, I've pretty much ensured that they won't all be used. Bigger battle, greater odds of using them all. Should be fun.


 * By the end of the Slime Girl battle, my intention is to use everything that can be used in a battle, as well as explain it all so that you, the reader, will have a full understanding of what is used to create an elaborate battle within a monster girl quest side story. :) Enjoy.


 * skilld1 - skilld4 (OHKO attacks) I'm not really sure that I'm going to use yet... I may use one of them, but having a bunch of them could be problematic... :( we'll see... Hope you're enjoying the story so far :)


 * Added one extra image created for me by jamjamstyle over at deviant art.

greened section represents file: MGQ\MOD\LukaVsAll\001_SlimeGirl\story.ini 

[setting]

 * title

Story Stuff: [story], [victory] & [lose]

 * ''This section (including [story], [victory] and [lose], essentially deals with the story more than the actual battle... though these sections are required, it's not so much battle related...


 * [story]


 * [victory]


 * [lose]
 * anten
 * monocro_on
 * monocro_off
 * monocro_on
 * monocro_off
 * monocro_off
 * monocro_off
 * monocro_off
 * monocro_off
 * monocro_off
 * monocro_off
 * monocro_off
 * monocro_off
 * monocro_off

Basic Battle Settings: [data], [ruka], [anno] & [sel]

 * This section, including [data], [ruka], [anno] and [sel], is the backing of your story. Everything that's said in reaction to anything that happens is listed here, you can tweak it further in other sections beyond, but here is the initial interaction...


 * [data]
 * notes about [data] section


 * [ruka]
 * notes about [ruka] section


 * [anno]


 * [sel]
 * [sel]

Luka's Skills - [hero_skillx]
notes on this section


 * This section was modified to make it appear shorter in the index...


 * [hero_skill1]


 * [hero_skill2]
 * [hero_skill3]
 * [hero_skill2]
 * [hero_skill3]
 * [hero_skill3]
 * [hero_skill3]
 * [hero_skill3]

Slime Girl Skills
Alright, this section pertains to the monster girl skills... It's made up of [onedari], [skillx#] and [overkill_x#]. This section can get very complex, but doesn't need to... Though there are lots of options available, you don't have to use them all... In this example I've used a very small selection of what's available, so it can be pretty basic. for a full understanding, click here.

The [onedari] section is a little different however, it doesn't actually do anything with the monster girl skills... That section is set to request those attacks during the battle...

[onedari]

 * notes re: [onedari]

[skilla1] - [skilla8]
This section was added as a section summery for navigational purposes. Instead of directly linking everything in the index, I'm making one heading for all of it. Reason being that the index became very long, and adding multiple battles to this page would make the index multiply in length...


 * [skilla1]


 * [skilla2]


 * [skilla3]


 * [skilla4]


 * [skilla5]


 * [skilla6]

[skillb1] - [skillb4]
This section was added to help minimize the length of the index... mainly because with multiple battles on this page, the index will be exceptionally long... also, it's pretty easy to manually navigate this section once you're here... :)

As a note with this section, [skillb1] to [skillb4] are used as bound attacks. To access the b group, you must set skill_kouka to 3.


 * [skillb1]


 * [skillb2]


 * [skillb3]


 * [skillb4]

[skillc1] - [skillc4]
This section is for the second set of bound skills, resulting from a bind attack with skill_kouka set to 4. Thought I should go back and explain that... :)


 * [skillc1]


 * [skillc2]


 * [skillc3]


 * [skillc4]

[skilld1] - [skilld4]
This section is for the one hit knock out (OHKO) attacks. I'm probably not going to use all of them, but I plan on using at least one.


 * [skilld1]


 * [skilld2]
 * skillname = "Slime Hell "
 * skill_kakuritu = "50"
 * skill_sel1 = "Welcome to Hell! "
 * skill_anno1_1 = "The Slime Girl dives toward Luka... "
 * skill_anno1_2 = "reforming her body to entwine him fully in herself... "
 * skill_damage1_1 = "-10"
 * skill_damage1_2 = "10"
 * skill_se1 = "ero_slime1"
 * skill_anno2_1 = "She twists her body like ropes, her breasts wrapped around Luka's manhood... "
 * skill_anno2_2 = "her lips spread across his own... "
 * skill_damage2_1 = "50"
 * skill_damage2_2 = "100"
 * skill_se2 = "ero_slime2"
 * skill_anno3_1 = "Her breasts begin to pump back and forth along his shaft "
 * skill_anno3_2 = "Her Slimey clit forcefully runs up and down his tongue... "
 * skill_damage3_1 = "500"
 * skill_damage3_2 = "1000"
 * skill_selx1 = "Lets see how close we can get baby... "
 * skill_selx2 = "I bet you've never been this close to anyone! "
 * skill_lose_sel1 = "You like my tits baby? "
 * skill_lose_sel2 = "How they can jerk you off all on their own..? "
 * skill_overkill = "overkill_d2"

Charged Attacks: [skilltame] & [skillcounter]
... not really as plural as it sounds... this section will contain skilltame0 and skilltame1, it may contain skillcounter0 and skillcounter1 as well, but ... haven't really decided yet... :)


 * The [skilltame0] and [skilltame1] sections are for a charged attack. It's a two part attack, the first part of which, skilltame0, deals no damage and is somewhat different than a standard skill definition. The second part, skilltame1, is the actual attack, and is pretty much the same as a standard attack for scripting purposes. There are added definitions to be made (skill_selmiss1, skill_selmiss2 and skill_selmiss3) which; well... you'll see about. Should be fun... :)


 * [skilltame0]


 * [skilltame1]

Slime Girl Skills: Overkill
This section is the overkill sections for various attacks (in this case every attack has an overkill scene). Overkill scenes are a great way to add some customization to the end of your battles, really... anything attack that you've created should have a specific ending, and if you can customize that a little further, why not?
 * Remember, at the end of your overkill section you need to include 'overkill_end', that said, if you have a fairly consistent ending, you could just do minor things in your custom overkill section, then go to another preset, more default, ending that then leads (after overkill end) to your standard [lose] section...

[overkill_a1] - [overkill_a8]

 * I've segmented this area into one group so that the page remains easy to navigate as it grows in battle count.

It should be noted, however, that the sections here don't need to follow this naming convention, instead you can name them whatever you want; just make sure that you reference it accordingly under skillxx -> overkill...


 * [overkill_a1]
 * notes on overkill
 * overkill_end
 * overkill_end
 * overkill_end
 * overkill_end
 * overkill_end
 * overkill_end
 * overkill_end
 * overkill_end
 * overkill_end
 * overkill_end
 * overkill_end
 * overkill_end
 * overkill_end
 * overkill_end


 * [overkill_a2]


 * [overkill_a3]


 * [overkill_a4]


 * [overkill_a5]


 * [overkill_a6]

[overkill_b1] - [overkill_b4]

 * This section reflects overkills for bound attacks... [b1 - b4]


 * [overkill_b1]


 * [overkill_b2]


 * [overkill_b3]


 * [overkill_b4]

[overkill_c1] - [overkill_c4]

 * This section reflects overkills for bound attacks... [c1 - c4]


 * [overkill_c1]


 * [overkill_c2]


 * [overkill_c3]


 * [overkill_c4]
 * 0 = "bg,bg084,10,1000"
 * 1 = "name,Slime Girl "
 * 2 = "mmmm, lick around my dirty hole you naughty boy! "
 * 3 = "hehe, you must be really really naughty to cum while doing this! "
 * 4 = "name,Luka "
 * 5 = "I... I... I mean, it was an accident! "
 * 6 = "name,Slime Girl "
 * 7 = "Ha! Accident he says! That's pretty funny... "
 * 8 = "Well, because of your little 'accident'... you're going to be licking that hole a lot from now on... "
 * 9 = "name,Tongue Press "
 * 10 = "Rotating her upper body fully around, the Slime Girl looks down at Luka's face only inches from her ass... "
 * 11 = "She smiles and presses his head forward into it... "
 * 12 = "name,Slime Girl "
 * 13 = "Now, spread those cheeks and get in good and deep Luka... "
 * 14 = "Tongue fuck my ass for me baby! "
 * 15 = "name,Luka "
 * 16 = "... mmph... "
 * 17 = "name,Slime Girl "
 * 18 = "Don't talk with your mouth full! "
 * 19 = "name,Hole Expansion "
 * 20 = "The Slime Girl reshapes her body to allow her asshole to stretch much further than before... "
 * 21 = "She presses Luka's whole face inside, making him lick all the way around her rim as she rotates around him... "
 * 22 = "name,Luka "
 * 23 = "... "
 * 24 = "name,Ass Escape "
 * 25 = "Luka's hands run down the Slime Girl's legs, giving her a sence of comfort in his obedience to her... "
 * 26 = "Quickly, Luka shifts upward and forces her off of him with the last of his strength. "
 * 27 = "name,Luka "
 * 28 = "ckhaaa (gasp) "
 * 29 = "name,Slime Girl "
 * 30 = "You dirty little bugger! "
 * 31 = "name,... "
 * 32 = "She looks at Luka and watches as his face returns to normal colour... "
 * 33 = "name,Slime Girl "
 * 34 = "Oooh... you couldn't breath... ... alright then, I guess I understand... "
 * 35 = "Just lick it from now on then, and maybe use some fingers... hehe... "
 * 36 = "overkill_end"
 * 37 = "end"

[overkill_d1] - [overkill_d4]

 * This section reflects overkills for OHKO attacks, really these are the attacks that should definitely have an overkill section.

Charged Attack Overkills

 * This section reflects overkills for charged attacks. Though there is only one charged attack and one counter attack... it still needs it's own section for clarity...

Slime Girl Images

 * Alright, so this section is going to deal with image display (after the battle). It won't actually be called at all during the battle, but I felt that keeping it somewhat organized and dealing with everything within the monster's own folder would be a little bit more organized... especially since otherwise I'd have one file with a huge number of monsters; which would get to be pretty confusing.


 * This section will be repeated fairly heavily throughout every battle file, though it'll also include the direct image reference for each monster; unfortunately it'd have to be mostly repeated anyway... because of that, I figured doing it this way would be better... :)


 * Breaking it down, we're going to have the [pics] section, which is called by default. This section will display the setup and start for picture display... Since it's initial reference is in the main story file, the setting will already be present. The pictures available here will be all image references for the monster girl, as well as the background in which their battle occurs during Monster Girl Quest. They will be viewed 2 files at a time, which allows for the choice command to reference them both as well as a exit / next - previous / next / previous / exit type of options depending on how far into the image set you are.


 * Should be good... :) Currently I'm working on images for the setup, haven't gotten around to them yet and as such can't test how it's working. Will have to get those done shortly and then set it up before really adding a whole lot of script.

Additional Files

 * \slime_away.png

002_SlugGirl

 * This section reflects the folder structure
 * MGQ\MOD\LukaVsAll\002_SlugGirl... It will include the story.ini file as well as any custom stuff required for the folder. (maybe custom graphics and / or sounds...) External references aren't 100% required to be listed here, but I felt it best to inclulde them just incase they happen to exist, and... well, it's good to show how everything works at the same time. :)


 * Like the 001_SlugGirl section, any [section] bracketed off like that is a section within your story.ini file. Pretty much anyway, unless otherwise specified... but yeah, it's organization for your story which you can jump to either with a goto or with var_jump... in the event (which this is) of a battle, the sections are required for the battle to occur, their direct purposes are listed on this page, as well as on the Battle Commands page created by myself and GC345. Awesome stuff, take a look at it!


 * adding a walking away / leaving picture for the Slug girl as well, going to be awesome...

greened section represents file MGQ\MOD\LukaVsAll\002_SlugGirl\story.ini 

Story Stuff - [story], [victory] & [lose]

 * [story]


 * [victory]


 * [lose]

Basic Battle Settings: [data], [ruka], [anno] & [sel]

 * [data]


 * [ruka]


 * [anno]


 * [sel]

Luka's Skills - [hero_skillx]

 * [hero_skill1]


 * [hero_skill2]


 * [hero_skill3]

Slug Girl Skills
This section contains [onedari], [skillx#], and [overkill_x#] for the Slug Girl's battle profile. Like the Slime Girl, I will not be using the entire selection of available battle settings... These 'first' battles, are fairly basic. There were other things added to them in the game story line, but those can't really be replicated 100% in a side story. For instance, in the Slime Girl battle you had Flail Wildly unlock mid battle and Luka had to use that to defeat her... In this battle, Luka needed to use salt... The purpose of these first battles in my side story is more to introduce you to how battle creation works... as the monster's advance, the battle creation will as well...

Again, the [onedari] section is listed here, but really doesn't have a lot to do with skill creation. That said, it's critical to have the skill names match up 100% in the onedari list as the skill creation list, might as well have them together... :) Unless you create a framework for your battle in advance (list out all the skill names you plan to use, set out their sections / etc before starting to tweak and actually create the attacks) it's probably better to do the [onedari] section after you've completed the skill set to be sure that everything's done proper in it. Also you might consider modifying it once you've got your skill list.

[skilla1] - [skilla8]

 * This section is for skills a1 through a8, these are skills that have no real requirements, they can result in a bind but the character is not bound while they're being used.


 * These skills can be very complicated or fairly basic, it really depends on what you decide is required by the skill you're creating. Here, I'm trying to recreate a battle that occurred during the game, it was a fairly simple battle with fairly simple attacks, so there will be nothing overly complex in it. Should be fun :)


 * [skilla1]


 * [skilla2]
 * notes re: @ and \


 * [skilla3]


 * [skilla4]


 * [skilla5]

[skillb1] - [skillb4]

 * This section includes skills for bound attacks. You can also use [skillc1] to [skillc4] for bound attacks, their initiation is a little different though.


 * [skillb1]

Slug Girl Skills: Overkill

 * This section is for overkills associated with the Slug Girl's skills. Overkills are optional ending scenarios assigned to a specific skill. For instance, if you have 4 skills that your monster uses, one of which includes a kiss, another face sitting, another uses a hand job and the last includes penetration, your overkill sections allow you to have a specific ending for each of those attacks should the hero be defeated by that specific attack. Overkills are a great way to customize your attacks and if you're making a side story, really something to consider including.

[overkill_a1] - [overkill_a8]

 * This section is specifically for overkills between [skilla1] and [skilla8]. Though my naming convention is overkill_ax, it's not really mandatory to do that. You could name your overkill whatever you want. SlugTittyFest for instance might be a good overkill section name for one of them... I just felt that for ease of reading and learning listing them as overkill_ax / overkill_bx would be the best way to go... :)

[overkill_b1] - [overkill_b4]

 * This section is for overkill ends assigned from skills between [skillb1] and [skillb4]. These are bound attacks and should really have endings where the hero remains bound, at least in the beginning of the end...