Difference between revisions of "Coding Additions"

Revision as of 22:26, 10 April 2012

This page still needs to be created. It will contain general information on how to create your own content for the game, setting up Inform 7 and GIT, etc... For now, here are some links and general tips that will probably be broken down into sub-pages as this section is built up.

Setting up Inform7 and Git: Check out my outline on the Dev board here: Inform7 and Git GUI Putting Inform7 and Git on your computer aren't necessary for simple projects, but you'll want to be able to beta-test your own creations if they're elaborate in any way.

Please Note: If you don't feel capable of coding the additions you want to make, but are able to write the content for the scenes/creatures, these can be forwarded to NukuV or the game developers and put into the game. More complex creations are harder to do this way, as there is more variations and content to write and parts may get missed and have to be filled in by the developer, making it more difficult.

Getting started:

• Begin with some basic ideas. I recommend a simple creature to start. Use the template that has been made as a basis. It contains some examples of how to use if statements with for different results to account for player gender, libido and so on.
• Look at a couple of other creatures which use a similar mechanic to what you want to create. With over 100 creatures in the game, there is a lot of variations you can look over and draw techniques from.
• If a creature does something unusual, try a few variations with it in the game to see what happens. Then take a look at its code to see what may be prompting those to occur. I recommend playing with the creatures first so you don't ruin the surprise of experiencing it first hand.
• Putting out partially completed content is acceptable, but should be done when there is a good portion of gameplay available. If that event or character has some gameplay ready to go and a hint of more to come, then it adds to the game. As some content can be quite large, it is reasonable to put it out in this manner so it can be enjoyed while the next section is being prepared. Notes mentioning where content is forthcoming are appreciated as it cuts down on a player's frustration with trying to accomplish a goal or bed an NPC which doesn't have that part ready yet.
• Learn the basic player and monster properties and what they mean and how they can be utilized. The template is a good starting guide for this, but here is some more information:

• • The player's body parts are controlled by these main attributes. The names of the sections are saved as 'facename', 'bodyname', 'skinname', 'tailname' and 'cockname' of player. The appearance of these parts are 'face', 'body', 'skin', 'tail' and 'cock' of player. They must always be referred to as 'facename of player' and 'tail of player' when using them in the code, to specify that you are referring to the player character.
  • The player's gameplay stats such as 'libido', 'morale', 'hunger', 'thirst', etc... can also be read/manipulated. These must also be referred to as 'libido of player' in the code when used. These can be checked for if statements to make branching results. They can also be adjusted by the events occurring in a scene. When adjusting these, make sure to keep the adjustments reasonable to level of effects in the game while still achieving your desired effect. Add a statement like ' if libido of player > 100, now libido of player is 100; ' when making these manipulations to keep the results within the normal limits. Check what adjustment other similar or equivalent effects have on the player to help you scale your effects accordingly.

• • For monsters, they are all listed as part of a table, known as the 'table of random critters'. Some creatures, events and effects specifically call up the table to select a random or specific creature from it. This is what the fights and infection sources do, by calling up a random or specific creature and then running operations based on the various table entries. Some entries of note are the 'name entry' which gives the creatures name and is the main way to call it up from the table if needed. It is also what is copied into the player's various body part name variables when infection occurs. The 'face entry', 'body entry', 'skin entry', 'tail entry' and 'cock entry' contain the description of that strain's infection on that specific body part. It is what a player will see in their description when they look at themselves. Those entries are formatted to mesh into existing sentences, so take care with the formatting specifics of each one. The 'face change entry', etc... are the descriptions of how that body part is changing when an infection occurs. Again, these are attached to pre-existing phrases and so formatting them to match is important to get a properly looking transformation.
  • The various stat entries (str entry, dex entry, etc...) represent the values the player character will move towards over the course of multiple infections. As such, these stats should try to reflect what they do the player character and not the creature itself. Only the 'dex entry' is currently used in a combat capacity, also counting as the monster's dexterity for combat calculations. Keep in mind that 10-11 is meant to be human average and a player's specialized starting stat will be 17.
  • The hp entry, lev entry and wdam represent the monster's starting hit points, it's level and average damage (80% to 120% of this number at random each hit). If possible when adding a new monster to an area, look to find a level suitable for your creature which will also fit well with the levels/genders of the other creatures around it. Having a even variety of levels makes the game more balanced than having the creatures clustered at a few power levels or having large gaps between them.
  • The sexual transformation related variables can be used in several combinations. The basic value, the 'sex entry' represents the gender the monster is trying to make the player through infection ("Male", "Female or "Both" - with that formatting). This does not have any relation to the gender of the creature itself, which is simply represented by the various descriptive text entries. If the 'sex entry' is "Male", then only the cock-related entries are used. Similarly, if "Female" is used, then the breast and cunt specific entries are used. If "Both", then the cock, cunt and breast entries are all utilized. Where this knowledge comes in useful is below in the 'Advanced Techniques' section.
  • The 'cocks entry' and 'cunts entry' represent the number of these organs which the creature will try to give the player. They need to be at least 1 if pushing the player towards that gender. The width and length entries are representative of inches in size, so keep that in mind when selecting their values. The 'cock width' is a special value, as its was re-purposed into being the size the player's balls will grow towards (and cum output thereof for some scenes). A value of 3-5 is considered average in the game, with 6-11 being lemon-sized, 12-15 being orange/baseball-sized, 16-19 is grapefruit-sized and larger than that is cantaloupe-sized. The breast sizes count up in cup size from 1 for an A-cup, 2 for a B-cup and so on, maxing out at 26 for an impossibly huge Z-cup.
  • The libido entry is the minimum level of lust a player will move towards from infection by a creature. If their libido is below this value, their libido will go up by roughly a third of the difference between the two values. If they are over this number, they remain above it.
  • The loot entry and lootchance entry affect monster drop items. If the creature has no drop item, leave the loot entry as ""; (blank) and the lootchance at 0.

Advanced Techniques: (hopefully to come later)

• Multi-level enemies
• Special variation enemies
• Gender-swapping monsters
• Creature with a variable gender target
• Item creation
• Simple event creation

Super-Advanced Techniques: (hopefully to come later)

• NPC creation
• Location creation
• Linked/series event creation (quests)