Page controls, is this all?

[satori]

What can make you pick a page: (In the first book)

1) General text option of 1 or more
2) Dis use, one or more
3) Combat win
4) Combat flee
5) Random Number (can be combined with other options)
6) Solving a puzzle
7) Using an item
8) As per page 147, possibly needs wording changes at times based on previous page.

Edit: 12) Based on current EN value
Edit: 13) Based on number of rounds in active combat.
Edit: 14) Based on number of rounds after combat win.

It that all?

[outspaced]

Also for later books: 9) Rank; 10) Rank+Discipline combo; 11) Monetary transaction (unless that comes under 'Using an item')

[satori]

Quick question, besides the page 147 entry (where the text for 'go back the way you came' might have to be flipped) and the page (I forget the number) where you are told you lose your equpment, but only if you had surrendered to the bandits earlier, are there any other logic issues in book 1?

Thanks
Jacob

edit: You are right (11)$$$ SHOULD be seperate from general items, esp if a decent shopping system is to be coded.

[satori]

I think I have come up with everything an engine would need to know about a combat. Here is a pic from the table view of the DB I am working on:



I have duplicated the encounter options 5 times, is there ever a time when you have to fight more than 5 enemies on a page?

edit: Just realized I missed a few, need to add item/skill check for CS loss. WIll update pic in a few.

Edit2: I also added a poison checker with damage threshold and a timed branch check (after X rounds of combat turn to page xxx)

[satori]

OK! I got all the combat data entered in. Here it is in an xls spreadsheet. It should be sorted with the combat sections up top, if not, just sort for TRUE in the COMBAT field name.

angryclam.com/lone_wolf.xls

[outspaced]

There are also the following possibilities from subsequent books that I can think of:

1) -covered-
2) Ignore damage from opponent for x rounds; also: ignore damage to opponent for x rounds
3) Enemy Type--very important for things like x2 Damage vs. undead for the Sommerswerd, but the New Order books (waaaaaay off in the future) also have other Kai Weapons that give CS bonuses based on opponent/circumstance. Undead, Reptilian, Human/oid, Rock/Stone, Spellcaster, Sea-creature, Winged, Fire-breathers. Additional tags: Daylight, Nighttime, Underground, Underwater.
4) Puzzle! What about the 'find the answer and turn to the relevant numbered section' entries?

Does Enc2Type cover susceptibility to Mindblast (sometimes you get x2 damage vs. susceptible creatures, I think?)

[outspaced]

Bother! Also forgot to add:

5) Previous experiences (e.g. If you have ever been to Gorn Cove in a previous adventure . . . )

[satori]

outspaced said:

There are also the following possibilities from subsequent books that I can think of:

1) -covered-
2) Ignore damage from opponent for x rounds; also: ignore damage to opponent for x rounds
3) Enemy Type--very important for things like x2 Damage vs. undead for the Sommerswerd, but the New Order books (waaaaaay off in the future) also have other Kai Weapons that give CS bonuses based on opponent/circumstance. Undead, Reptilian, Human/oid, Rock/Stone, Spellcaster, Sea-creature, Winged, Fire-breathers. Additional tags: Daylight, Nighttime, Underground, Underwater.
4) Puzzle! What about the 'find the answer and turn to the relevant numbered section' entries?

Does Enc2Type cover susceptibility to Mindblast (sometimes you get x2 damage vs. susceptible creatures, I think?)

2) Good point. And since that doesn't happen in this book, when I add the fields I don't have to redo anything for the existing combat records
3) Each book would have a table of the monsters in the book. This is ref'd to the Enc x Type entry. In each item's record there is a list of enemies the multiplier is effective against. This is already covered (although that IS NOT visible in combat table I posted )
The Situational modifiers I did not know about, and I will need to add those to the item properties.

4) That's listed in #6 in the first post. Right now the only page data beyond combat data is the page number, and 'turn to' values for the page (666 for death, 420 for the win, 0 = nil) so it's not represented in my data so far.

After I code the items in the book, and finish off the player stats page, the next step is going through the pages and adding sub-fields for the 'Point n' values (next page).

This is where dis checks will be labeled, if a page is a 'passthrough' (no choice to make), if you have to win/lose/escape from a combat, if a random number plays a part (in whole or with a combination of other factors), any modifiers that may be made to the random number table pick, if a choice is simply an unmodified player choice (pick a fork in the road).

Puzzles will not have 'turn to' entry, but whenever a player has to make a puzzle choice, a text entry box will be on screen. You don't go to a certain section, it simply checks to see if you got it right. If so you continue, if you don't, well, that would probably depend on the ruleset used.

[satori]

outspaced said:

Bother! Also forgot to add:

5) Previous experiences (e.g. If you have ever been to Gorn Cove in a previous adventure . . . )

I'm thinking in the player stats table there will be a 'history' list. For things like this, and things like losing the crystal pendant, but still being recognized and whatnot.