Adding a New Activity:
Follow these instructions to add new activities to the database.

1. Select the Activity Type you want to add (Perform, Receive, Favor, After Game Gift or Drinking Activity).

2. Select the gender that the activity will be appropriate to by changing the Player Sex control. Note that the Player Sex selection always refers to the current player (or player_up) regardless of the activity type being added. If the activity will be appropriate for both players, use the "Any" option.

3. Select the Explicitness Level of your intended activity. It should be noted that explicitness levels go along the lines of this: 

Level One; Mild: No sexual contact, although other body parts may be touched, caressed or etc.

 Level Two; Moderate: More intimate, and perhaps some contact with the more "sexual" parts of the body.

 Level Three; High: Intimate and explicit adult interactions.

4. If alcohol is involved in your interaction, change the Alcohol control to "Yes". Otherwise, leave this at "No".

5. If your activity will last for a specific time period, enter this now. Otherwise leave the Activity Duration at "0".

6. Check the interaction categories that your activity will involve. If the categories do not seem to fit your activity then leave them all unchecked.

7. Check the clothing status required for the activity. These controls (player_up Clothes and opponent Clothes) ensure that activities in the database will suit the clothing condition of the players. If clothing is not an issue for your interaction, you can leave this control at "Any".

 Note: Sometimes, especially on low levels of gameplay, players can be wearing clothing for a long time. A nice idea when adding interactions at low explicitness is to leave the clothing controls set to "Any" but to instruct players to work through any clothing they might be wearing.

8. Now type in the description for the activity you are adding, paying particular attention to add the relevant player_up and opponent tags. .

9. If any fetish is associated with this interaction, select the Fetish tab and choose the fetish you want. 

Note:  If you'd like to associate a sound file and / or picture with this interaction you should load them using this tab. Make sure you set the relevant options in the Game Options > Multimedia page to ensure that your multimedia are presented during gameplay.

10. If any accessory (sex toy or etc.) is associated with this interaction, select the Accessory tab and choose the accessory you want.

11. If this interaction is for a player in a predicament, select the Pre Cond tab and choose the predicament you want.

Note: The Pre Cond tab stands for "Pre Condition" and represents player_ups current state (ie., the condition they are in before this interaction). This will usually be normal. Setting the Pre Condition to "Any / Doesn't Matter" means that the player_up will be able to perform the interaction regardless of their predicament.

12. We recommend setting the Post Cond (Post Condition) to match the Pre Cond, as otherwise the player will be put into a predicament as a result of the activity. If this is what you want, feel free to set the post condition as you desire.

13. Press the "Add" button to insert your new interaction record into the database.

Using the Prune Control:

The Prune function is used to remove sets of activity (ie., the contents of the search list). When you perform a search as described above, the search list will fill with the results. The Prune control deletes all activities returned by a search. It is extremely useful for removing activities created by a specific user, activities with a common error or any other type of activity you do not want in the database.

1. Use the search functions described above to retrieve a single activity or a set of activities.

2. Press the "Prune" button to delete all the activities in the search list.

Note: The Prune function is extremely powerful and should be used with care. It is not recommended to remove a great deal of the built in activities as the game is "data driven" and requires a large database to run correctly.