Jaber's Quest Log v2.1.3
12-11-2009, 07:41 PM
Instructions
And this is the part where your head explodes. There's a whole crapload of stuff you can do with this, so I'll just go over the features and how to use them.
WELL THAT ONLY TOOK THREE HOURS TO WRITE
...
It's really easy to use, but really hard to understand at first.
If anyone feels like writing a better set of instructions, go for it.
Screenshots
![[Image: 16k9s9w.jpg]](http://i50.tinypic.com/16k9s9w.jpg)
Demo
Now with several examples of the various things you can do!
(And it still doesn't cover everything possible!)
http://www.mediafire.com/download.php?zj0lm3nj3fk
Terms of Use
You can use it or repost it wherever you want, just make sure to credit me.
If you complain about the images, I will punch you in the face.
If you refuse to try it because you don't like the images and don't feel like making your own, I will punch you again, only harder.
Lastly, I would love to see the kinds of ideas people come up with for this.
Special thanks to DerVVulfman for support, suggestions, and encouraging me to make something that runs outside of Ninja Penguin.
And this is the part where your head explodes. There's a whole crapload of stuff you can do with this, so I'll just go over the features and how to use them.
Creating Quests
This is done in the Quest Data script. You can see an example of what the data for a quest will look like. You have complete control over everything displayed on the page when the quest is opened. It doesn't even need to be a quest, you could make some text for books, or put together a wanted poster on a wall, or really anything you can think of.
First, to create your quest, you need to pick out a unique key for it. The example quest uses "test quest". No other quest can have the same key, and you can name it whatever you want so it's more intuitive than just giving them numbers. For this example, let's use "wumpus" as the quest key. You'd start by adding the following line to the load_quest_data method:
$data_quests["wumpus"] = Quest_Data.new()
Now you can begin entering the data for your quest. The first thing to enter is the quest's name. This is what will be displayed ingame. We'll call this quest "Hunt the Wumpus":
$data_quests["wumpus"] = Quest_Data.new("Hunt the Wumpus",
The next two things to enter will be instructions for how the quest will look. See the "Instruction Types" section for detailed info.
The first of the two is the description section. The second of the two is the objective section. You don't need to put description only in the description section, and the objective section doesn't need to be used for objectives. Essentially, the two sections are identical, with one difference: The objective section has a 'stage' variable that you can change in-game to hide the objective or change what it does.
For our wumpus quest, we'll keep it simple and just use the first instruction type to write some text, and leave the objectives section blank:
$data_quests["wumpus"] = Quest_Data.new("Hunt the Wumpus", [[0, [0, [4, 4], "YOU MUST KILL THE WUMPUS"]]], []
The next part is for the quest variables. They don't need to be set up here, and you don't even need add this part. This section exists only to set what variables will start at when the quest is started. We'll leave it blank:
$data_quests["wumpus"] = Quest_Data.new("Hunt the Wumpus", [[0, [0, [4, 4], "YOU MUST KILL THE WUMPUS"]]], [])
And there you go, you've got the data for a simple wumpus-hunting quest set up. Or maybe it's just a note, or a flyer, who knows? You can use this for pretty much any kind of visual media in your game, whether you use the quest log functions or not.
First, to create your quest, you need to pick out a unique key for it. The example quest uses "test quest". No other quest can have the same key, and you can name it whatever you want so it's more intuitive than just giving them numbers. For this example, let's use "wumpus" as the quest key. You'd start by adding the following line to the load_quest_data method:
$data_quests["wumpus"] = Quest_Data.new()
Now you can begin entering the data for your quest. The first thing to enter is the quest's name. This is what will be displayed ingame. We'll call this quest "Hunt the Wumpus":
$data_quests["wumpus"] = Quest_Data.new("Hunt the Wumpus",
The next two things to enter will be instructions for how the quest will look. See the "Instruction Types" section for detailed info.
The first of the two is the description section. The second of the two is the objective section. You don't need to put description only in the description section, and the objective section doesn't need to be used for objectives. Essentially, the two sections are identical, with one difference: The objective section has a 'stage' variable that you can change in-game to hide the objective or change what it does.
For our wumpus quest, we'll keep it simple and just use the first instruction type to write some text, and leave the objectives section blank:
$data_quests["wumpus"] = Quest_Data.new("Hunt the Wumpus", [[0, [0, [4, 4], "YOU MUST KILL THE WUMPUS"]]], []
The next part is for the quest variables. They don't need to be set up here, and you don't even need add this part. This section exists only to set what variables will start at when the quest is started. We'll leave it blank:
$data_quests["wumpus"] = Quest_Data.new("Hunt the Wumpus", [[0, [0, [4, 4], "YOU MUST KILL THE WUMPUS"]]], [])
And there you go, you've got the data for a simple wumpus-hunting quest set up. Or maybe it's just a note, or a flyer, who knows? You can use this for pretty much any kind of visual media in your game, whether you use the quest log functions or not.
Category Lists
Quests are added to categories, and categories are added to category lists. You call the quest window and tell it what list to use, and it will display any categories in that list that have quests in them.
Even if you decide not to use the quest log functions, you'll still need to set up a list. They contain all the formatting information required by the script.
Here's how to set one up:
First, go to the quest handling script, and scroll down to the Quest_List class. See the '@lists[0] = Category_List.new' line? That's how you make a category list. There's more to it than that, though. That 0 is the list key. Like the quest key, it's a unique identifier for this particular list.
Now you have a number of different things you can customize for the list, the first of which being the categories it contains.
@lists[0].categories.push(["Category Name", category key])
Will add a category to the list. Category name would, of course, be the name of the category. Category key, just like the quest and list keys, is a unique identifier for a category. However, the categories themselves are not created just by adding them to a list. The list.categories just points towards the categories themselves. Don't worry too much about it, though, because the categories themselves are created automatically when quests are added to them. Any categories without quests in them won't show up, so add whatever categories you'll want to use in the future.
Onto the actual customization portion:
All of the following are accessed the same way, with @lists[key].xxxxxxx, where xxxxx would be the name of the option. So if you wanted to change the title of the list '0' above, you'd use @lists[0].title = ______. Let's begin.
title
This is what shows up at the top of the page where "Table of Contents" is in the screenshots. It's just a string.
font
This contains the default fonts, sizes, and colors for the list. It's set up as
[[Title Font, Size, Color], [List Font, Size, Color]]
background
An array holding the filename of the picture to use, and the x/y offsets for positioning it relative to the text. It's set up as
[filename, x offset, y offset]
windowskin
This is what windowskin the list will use. This pretty much just affects what the cursor will look like. It's just a string.
ipp
This is how many items will appear on each page of the list. If you muck with this, you'll likely have to change the formatting part below. It's an integer.
animation
This will control the page turning animations whenever I get around to making them. Currently it does nothing.
empty_text
This is what will be displayed if you have no categories with quests on the list. It's just a string.
audio
This is an array containing arrays containing the data on what sound effects to play for various things like flipping pages and moving the cursor. I forget how it's set up, but each element of the array is set up as ["Audio/SE/Filename", volume, pitch].
I know audio[2] is for the opening and closing of the list, but I forget the rest. Experiment with it a bit, you'll figure it out.
formatting
This controls the positioning and spacing of the items on the list. It's set up as
[distance between pages, distance between list items, width of one page, offset from top of page, cursor margin]
page_graphics
This is an array holding the filenames of the little arrows in the corner. It's set up as [filename for left arrow, filename for right arrow]
You can check the Category_List class if you need help with how it should be set up. Changing the settings in the actual class will change them for all lists that don't have the options set individually. In other words, they're the defaults.
Even if you decide not to use the quest log functions, you'll still need to set up a list. They contain all the formatting information required by the script.
Here's how to set one up:
First, go to the quest handling script, and scroll down to the Quest_List class. See the '@lists[0] = Category_List.new' line? That's how you make a category list. There's more to it than that, though. That 0 is the list key. Like the quest key, it's a unique identifier for this particular list.
Now you have a number of different things you can customize for the list, the first of which being the categories it contains.
@lists[0].categories.push(["Category Name", category key])
Will add a category to the list. Category name would, of course, be the name of the category. Category key, just like the quest and list keys, is a unique identifier for a category. However, the categories themselves are not created just by adding them to a list. The list.categories just points towards the categories themselves. Don't worry too much about it, though, because the categories themselves are created automatically when quests are added to them. Any categories without quests in them won't show up, so add whatever categories you'll want to use in the future.
Onto the actual customization portion:
All of the following are accessed the same way, with @lists[key].xxxxxxx, where xxxxx would be the name of the option. So if you wanted to change the title of the list '0' above, you'd use @lists[0].title = ______. Let's begin.
title
This is what shows up at the top of the page where "Table of Contents" is in the screenshots. It's just a string.
font
This contains the default fonts, sizes, and colors for the list. It's set up as
[[Title Font, Size, Color], [List Font, Size, Color]]
background
An array holding the filename of the picture to use, and the x/y offsets for positioning it relative to the text. It's set up as
[filename, x offset, y offset]
windowskin
This is what windowskin the list will use. This pretty much just affects what the cursor will look like. It's just a string.
ipp
This is how many items will appear on each page of the list. If you muck with this, you'll likely have to change the formatting part below. It's an integer.
animation
This will control the page turning animations whenever I get around to making them. Currently it does nothing.
empty_text
This is what will be displayed if you have no categories with quests on the list. It's just a string.
audio
This is an array containing arrays containing the data on what sound effects to play for various things like flipping pages and moving the cursor. I forget how it's set up, but each element of the array is set up as ["Audio/SE/Filename", volume, pitch].
I know audio[2] is for the opening and closing of the list, but I forget the rest. Experiment with it a bit, you'll figure it out.
formatting
This controls the positioning and spacing of the items on the list. It's set up as
[distance between pages, distance between list items, width of one page, offset from top of page, cursor margin]
page_graphics
This is an array holding the filenames of the little arrows in the corner. It's set up as [filename for left arrow, filename for right arrow]
You can check the Category_List class if you need help with how it should be set up. Changing the settings in the actual class will change them for all lists that don't have the options set individually. In other words, they're the defaults.
Basic Use
Alright, you've got some quests set up and a category list set up. So how do you start adding quests and all that stuff?
It's really rather easy once you get the hang of it.
First, I'll explain how the data is handled.
The entries in $data_quests don't contain the actual quest data, they're basically just cookie cutters that display the quest. When you add a quest to a category, it creates an actual data entry for the quest in $game_party.quests.quests. This is where the objective stages and quest variables are stored. You can access them any time in-game by using $game_party.quests.quests[quest key].stages[objective index]
and
$game_party.quests.quests[quest key].data[variable key]
You're probably confused at this point, but it's important to understand that before a quest has an entry in $game_party.quests.quests, it essentially does not exist in your saved data, which means you can't do anything with its objective stages or quest variables until it's been added. There's two ways to do this: You can use the 'add' method to add it to a category, or the 'add_quest' function to create just the quest data. More on that later.
Other than objectives and variables, you won't be able to view any quest that doesn't have an entry in $game_party.quests.quests. If you try to open the quest window directly to such a quest, it will explode.
While you're here, there is one more thing you need to do. See that '@settings = [0, 0]' line? That controls the settings for the message codes and instruction types. Specifically, for the drawing of battlers and the displaying of item quantities.
The first number is for item quantities. 0 is for my item grid system. You'll need to set this to 1 so it'll use the default inventory system. Otherwise, youre game will explode.
The second number is for the type of battlers you're using. 0 is for my animation system, and will make your game explode. Set this to 1 for minkoff's animated battlers, or 2 for the default battlers. Currently there is no code for the display of minkoff battlers, so don't be alarmed if it doesn't do anything yet. It'll be added in the next update.
Back to objectives and variables...
The 'objective index' above points to an objective. 0 would be the first objective, 1 would be the second, and so on.
The variable key is, like all the other keys, an identifier for a variable of the quest. You can only use alphanumeric characters for variable keys. If you use anything else, you won't be able to show the variable in the quest description using the message codes. These variables can be whatever you want, you could have say... a "cats ridden" variable that tracks how many cats you've ridden, for example.
It's really simple once you get the hang of it. Not so simple to explain. You'll get the hang of it. Probably.
Anyways, with that out of the way, let's go back to the basics: how to control the quests. There's a number of commands I've made to make it easier, and they handle a lot of the checks and data creation for you.
All are accessed with $game_party.quests._________
Let's begin:
has_quest(quest key)
This will return true if the quest has a data entry. You can use this to check if a quest has been accepted, or to prevent the aforementioned explosion from trying to view a quest with no data entry.
add(quest key, category key)
This will add a quest to a category. It will also create a data entry for the quest if it doesn't already have one. The quest will be viewable from any lists that have the category key in their categories setting.
add_quest(quest key)
This will create a data entry for a quest if it doesn't already have one.
remove(quest key, category key)
This will remove a quest from a category. It will not remove the quest's data entry.
remove_quest(quest key, erase)
This will remove a quest from ALL categories. It will not remove the quest's data entry unless 'erase' is set to true. 'erase' is entirely optional, and not including it is the same as setting it to false.
reset_quest(quest key, create)
This will blank out a quest's variables and objectives, returning them to the default values. It will not remove it from any categories. If 'create' is set to true, this command will create a data entry if called on a quest that doesn't have one. 'create' is optional, and not including it is the same as calling it as true.
replace(new quest, old quest, category key)
This will replace one quest with another on a category. It will take the old quest's spot on the list, so the order will stay the same. It does not touch the quest data at all. Useful for when a quest requires a large update, and you want it to look like the same quest.
erase_list(category key)
This will erase a category. It will not erase any quest data for the quests within. Almost entirely useless, you can use this to veeeeery slightly lower the size of your savefiles by erasing lists that are no longer needed.
create_list(category key)
This will create a category. Entirely useless since this is done automatically whenever it's needed.
It's really rather easy once you get the hang of it.
First, I'll explain how the data is handled.
The entries in $data_quests don't contain the actual quest data, they're basically just cookie cutters that display the quest. When you add a quest to a category, it creates an actual data entry for the quest in $game_party.quests.quests. This is where the objective stages and quest variables are stored. You can access them any time in-game by using $game_party.quests.quests[quest key].stages[objective index]
and
$game_party.quests.quests[quest key].data[variable key]
You're probably confused at this point, but it's important to understand that before a quest has an entry in $game_party.quests.quests, it essentially does not exist in your saved data, which means you can't do anything with its objective stages or quest variables until it's been added. There's two ways to do this: You can use the 'add' method to add it to a category, or the 'add_quest' function to create just the quest data. More on that later.
Other than objectives and variables, you won't be able to view any quest that doesn't have an entry in $game_party.quests.quests. If you try to open the quest window directly to such a quest, it will explode.
While you're here, there is one more thing you need to do. See that '@settings = [0, 0]' line? That controls the settings for the message codes and instruction types. Specifically, for the drawing of battlers and the displaying of item quantities.
The first number is for item quantities. 0 is for my item grid system. You'll need to set this to 1 so it'll use the default inventory system. Otherwise, youre game will explode.
The second number is for the type of battlers you're using. 0 is for my animation system, and will make your game explode. Set this to 1 for minkoff's animated battlers, or 2 for the default battlers. Currently there is no code for the display of minkoff battlers, so don't be alarmed if it doesn't do anything yet. It'll be added in the next update.
Back to objectives and variables...
The 'objective index' above points to an objective. 0 would be the first objective, 1 would be the second, and so on.
The variable key is, like all the other keys, an identifier for a variable of the quest. You can only use alphanumeric characters for variable keys. If you use anything else, you won't be able to show the variable in the quest description using the message codes. These variables can be whatever you want, you could have say... a "cats ridden" variable that tracks how many cats you've ridden, for example.
It's really simple once you get the hang of it. Not so simple to explain. You'll get the hang of it. Probably.
Anyways, with that out of the way, let's go back to the basics: how to control the quests. There's a number of commands I've made to make it easier, and they handle a lot of the checks and data creation for you.
All are accessed with $game_party.quests._________
Let's begin:
has_quest(quest key)
This will return true if the quest has a data entry. You can use this to check if a quest has been accepted, or to prevent the aforementioned explosion from trying to view a quest with no data entry.
add(quest key, category key)
This will add a quest to a category. It will also create a data entry for the quest if it doesn't already have one. The quest will be viewable from any lists that have the category key in their categories setting.
add_quest(quest key)
This will create a data entry for a quest if it doesn't already have one.
remove(quest key, category key)
This will remove a quest from a category. It will not remove the quest's data entry.
remove_quest(quest key, erase)
This will remove a quest from ALL categories. It will not remove the quest's data entry unless 'erase' is set to true. 'erase' is entirely optional, and not including it is the same as setting it to false.
reset_quest(quest key, create)
This will blank out a quest's variables and objectives, returning them to the default values. It will not remove it from any categories. If 'create' is set to true, this command will create a data entry if called on a quest that doesn't have one. 'create' is optional, and not including it is the same as calling it as true.
replace(new quest, old quest, category key)
This will replace one quest with another on a category. It will take the old quest's spot on the list, so the order will stay the same. It does not touch the quest data at all. Useful for when a quest requires a large update, and you want it to look like the same quest.
erase_list(category key)
This will erase a category. It will not erase any quest data for the quests within. Almost entirely useless, you can use this to veeeeery slightly lower the size of your savefiles by erasing lists that are no longer needed.
create_list(category key)
This will create a category. Entirely useless since this is done automatically whenever it's needed.
Instruction Types
For quest layout, that is. Descriptions and objectives use a list of these to put together the quest. For the most part, they're pretty much the same for descriptions and objectives. Objectives just have an added stage variable and a some parts are turned into arrays.
The basic layout for an instruction is as follows:
[type, [data]]
For objectives, there's an added stage variable:
[type, stage, [data]]
'stage' would be whatever you want the stage to start at. 0 is hidden, 1 displays the first entry, 2 displays the second, and so on. Objectives can have as many stages as you want.
And with that, here's the type numbers and data format:
Any options marked with a * are optional.
'page' refers to the pair of pages it will appear on, i.e. 1 would refer to page 3 and 4. This means you can have thigns spanning multiple pages, so you could use it for books and whatnot.
Type 0 - Draw Text
This draws text, obviously.
Descriptions:
[0, [page, [x, y], text, alignment*, color*, size*, font*]]
Objectives:
[0, stage, [page, [x, y], [stage1 text, stage2 text, etc.], alignment*, color*, size*, font*]]
Pretty self-explanatory. The text can make use of message codes, detailed in the 'message codes' section.
Type 1 - Graphic
This displays either an icon or a picture.
Descriptions:
[1, [page, [x, y, zoom_x*, zoom_y*, opacity*], [type, filename]]]
Objectives:
[1, stage, [page, [x, y, zoom_x*, zoom_y*, opacity*], [[stage1 type, stage1 filename], [stage2 type, stage2 filename], [etc., etc.]]]]
'type' is either 0 or 1. 0 will load an icon, 1 will load a picture. zoom_x and zoom_y are multipliers, i.e. a zoom_x of 1.2 will make the image 20% wider.
Type 2 - Draw Battler
This will draw an actor's battler.
For default battlers:
Descriptions:
[2, [page, [x, y, opacity*], [type, id]]]
Objectives:
[2, stage, [page, [x, y, opacity*], [[stage1 type, stage1 id], [stage2 type, stage2 id], etc.]]]
'type' is either 0 or 1. 0 will load actors, 1 will load enemies. ID is the database id.
For Minkoff battlers:
Descriptions:
[2, [page, [x, y, opacity*], [type, id], pose#, frame]]
Objectives:
[2, stage, [page, [x, y, opacity*], [[stage1 type, stage1 id], [stage2 type, stage2 id], etc.], [stage1 pose#, stage2 pose#, etc.], [stage1 frame, stage2 frame, etc.]]]
'type' is either 0 or 1. 0 will load actors, 1 will load enemies. ID is the database id.
If the battler is set up to use a default battler, pose and frame can be skipped.
You can enter an opacity to use, but if the battler is added to MNK_TRANSLUCENT_WHATEVER, then it'll use the MNK_TRANSLUCENCY thingy setting.
Type 3 - Draw Characterset
This will draw a specified character, or an actor's characterset.
Descriptions:
[3, [page, [x, y, opacity*], [type, data], [frames, directions, facing, frame#]]]
Objectives:
[3, stage, [page, [x, y, opacity*], [[stage1 type, stage1 data], [stage2 type, stage2 data], [etc., etc.]], [[stage1 frames, directions, facing, frame#], [stage 2 frames, directions, facing, frame#], etc.]]]
'type' is either 0 or 1. 'data' depends on which type you use:
For type 0, it will use an actor's characterset, formatted like so: [0, actor id]
For type 1, it will use the specified characterset, formatted like so: [1, "filename", hue number]
frames is how many animation frames the characterset has (typically 4)
directions is how many directions the characterset has (typically 4 or 8)
facing is which direction will be displayed. It does not correspond to the actual directions, but to how far down the characterset it is, i.e. on a default 4dir characterset (dirs = [2, 4, 6, 8]), you'd enter 0 for down, 1 for left, 2 for right, and 3 for up.
frame# is what frame of the walking animation will be displayed.
The basic layout for an instruction is as follows:
[type, [data]]
For objectives, there's an added stage variable:
[type, stage, [data]]
'stage' would be whatever you want the stage to start at. 0 is hidden, 1 displays the first entry, 2 displays the second, and so on. Objectives can have as many stages as you want.
And with that, here's the type numbers and data format:
Any options marked with a * are optional.
'page' refers to the pair of pages it will appear on, i.e. 1 would refer to page 3 and 4. This means you can have thigns spanning multiple pages, so you could use it for books and whatnot.
Type 0 - Draw Text
This draws text, obviously.
Descriptions:
[0, [page, [x, y], text, alignment*, color*, size*, font*]]
Objectives:
[0, stage, [page, [x, y], [stage1 text, stage2 text, etc.], alignment*, color*, size*, font*]]
Pretty self-explanatory. The text can make use of message codes, detailed in the 'message codes' section.
Type 1 - Graphic
This displays either an icon or a picture.
Descriptions:
[1, [page, [x, y, zoom_x*, zoom_y*, opacity*], [type, filename]]]
Objectives:
[1, stage, [page, [x, y, zoom_x*, zoom_y*, opacity*], [[stage1 type, stage1 filename], [stage2 type, stage2 filename], [etc., etc.]]]]
'type' is either 0 or 1. 0 will load an icon, 1 will load a picture. zoom_x and zoom_y are multipliers, i.e. a zoom_x of 1.2 will make the image 20% wider.
Type 2 - Draw Battler
This will draw an actor's battler.
For default battlers:
Descriptions:
[2, [page, [x, y, opacity*], [type, id]]]
Objectives:
[2, stage, [page, [x, y, opacity*], [[stage1 type, stage1 id], [stage2 type, stage2 id], etc.]]]
'type' is either 0 or 1. 0 will load actors, 1 will load enemies. ID is the database id.
For Minkoff battlers:
Descriptions:
[2, [page, [x, y, opacity*], [type, id], pose#, frame]]
Objectives:
[2, stage, [page, [x, y, opacity*], [[stage1 type, stage1 id], [stage2 type, stage2 id], etc.], [stage1 pose#, stage2 pose#, etc.], [stage1 frame, stage2 frame, etc.]]]
'type' is either 0 or 1. 0 will load actors, 1 will load enemies. ID is the database id.
If the battler is set up to use a default battler, pose and frame can be skipped.
You can enter an opacity to use, but if the battler is added to MNK_TRANSLUCENT_WHATEVER, then it'll use the MNK_TRANSLUCENCY thingy setting.
Type 3 - Draw Characterset
This will draw a specified character, or an actor's characterset.
Descriptions:
[3, [page, [x, y, opacity*], [type, data], [frames, directions, facing, frame#]]]
Objectives:
[3, stage, [page, [x, y, opacity*], [[stage1 type, stage1 data], [stage2 type, stage2 data], [etc., etc.]], [[stage1 frames, directions, facing, frame#], [stage 2 frames, directions, facing, frame#], etc.]]]
'type' is either 0 or 1. 'data' depends on which type you use:
For type 0, it will use an actor's characterset, formatted like so: [0, actor id]
For type 1, it will use the specified characterset, formatted like so: [1, "filename", hue number]
frames is how many animation frames the characterset has (typically 4)
directions is how many directions the characterset has (typically 4 or 8)
facing is which direction will be displayed. It does not correspond to the actual directions, but to how far down the characterset it is, i.e. on a default 4dir characterset (dirs = [2, 4, 6, 8]), you'd enter 0 for down, 1 for left, 2 for right, and 3 for up.
frame# is what frame of the walking animation will be displayed.
Message Codes
There's three codes for use in quest and category names, and a bunch others for description and objective text. All you do is include the code in the text, and it'll replace it with various things or change various settings.
Quest/Category Name Codes
These control the font for quest and category names. They'll be used in place of the list's default settings. You can use this to, say, use a handwriting-ish font to make it look like a note was scrawled in, or something.
\\fn[number]
This will change the font. You'll have to set up what number goes with what font in the 'title_fonts' method at the very bottom of the Quest Window script.
\\fs[number]
This will change the size of the font.
\\fc[r,g,b]
This will change the color of the font. r, g, b corresponds to red, green, and blue levels.
Description/Objective Codes
These can be used to display a wide variety of data.
\\v[n]
This will display $game_variables[n]
\\s[n,on,off]
This will display the state of $game_switches[n].
If the switch is true, it will display the 'on' text. Otherwise, it will display the 'off' text.
Example: "The gate is \\s[3,open,closed]."
Alphanumerics only, by the way.
\\g
This will display the amount of gold the party has.
\\qv[key]
This will display one of the quest's variables. 'key' would be the variable key, obviously. This is why I suggested only using alphanumerics in the variable keys, as you won't be able to display any that use other characters.
\\item[n]
\\weapon[n]
\\armor[n]
\\skill[n]
\\actor[n]
\\enemy[n]
\\class[n]
These will display the item/skill/class/etc. names. n would be the id.
\\aclass[id]
This will display the name of $game_actor[id]'s class.
\\held[type,id]
This will display the quantity of an item/weapon/armor.
type is 0 for items, 1 for weapons, and 2 for armors. id is, of course, the id.
\\stat[type,id,stat]
This will display an actor/enemy's stats.
For type, enter one of the following:
0: Will use $game_party.actors[id]
1: Will use $game_actors[id]
2: Will use $data_enemies[id]
For id, enter the party index (if you're using type 0), or the database ID.
For stat, you can use any of the following:
hp, maxhp, sp, maxsp, bmaxhp, bmaxsp, atk, str, int, dex, agi, pdef, mdef, eva
It's typed in exactly like that.
For example, \\stat[1,2,bmaxhp] would display Basil's base max hp.
If you look at the code, you'll notice a whole bunch more stats listed. Don't use them or your game will explode.
Also, hp, maxhp, sp, and maxsp will likely not work with enemies.
Quest/Category Name Codes
These control the font for quest and category names. They'll be used in place of the list's default settings. You can use this to, say, use a handwriting-ish font to make it look like a note was scrawled in, or something.
\\fn[number]
This will change the font. You'll have to set up what number goes with what font in the 'title_fonts' method at the very bottom of the Quest Window script.
\\fs[number]
This will change the size of the font.
\\fc[r,g,b]
This will change the color of the font. r, g, b corresponds to red, green, and blue levels.
Description/Objective Codes
These can be used to display a wide variety of data.
\\v[n]
This will display $game_variables[n]
\\s[n,on,off]
This will display the state of $game_switches[n].
If the switch is true, it will display the 'on' text. Otherwise, it will display the 'off' text.
Example: "The gate is \\s[3,open,closed]."
Alphanumerics only, by the way.
\\g
This will display the amount of gold the party has.
\\qv[key]
This will display one of the quest's variables. 'key' would be the variable key, obviously. This is why I suggested only using alphanumerics in the variable keys, as you won't be able to display any that use other characters.
\\item[n]
\\weapon[n]
\\armor[n]
\\skill[n]
\\actor[n]
\\enemy[n]
\\class[n]
These will display the item/skill/class/etc. names. n would be the id.
\\aclass[id]
This will display the name of $game_actor[id]'s class.
\\held[type,id]
This will display the quantity of an item/weapon/armor.
type is 0 for items, 1 for weapons, and 2 for armors. id is, of course, the id.
\\stat[type,id,stat]
This will display an actor/enemy's stats.
For type, enter one of the following:
0: Will use $game_party.actors[id]
1: Will use $game_actors[id]
2: Will use $data_enemies[id]
For id, enter the party index (if you're using type 0), or the database ID.
For stat, you can use any of the following:
hp, maxhp, sp, maxsp, bmaxhp, bmaxsp, atk, str, int, dex, agi, pdef, mdef, eva
It's typed in exactly like that.
For example, \\stat[1,2,bmaxhp] would display Basil's base max hp.
If you look at the code, you'll notice a whole bunch more stats listed. Don't use them or your game will explode.
Also, hp, maxhp, sp, and maxsp will likely not work with enemies.
...
It's really easy to use, but really hard to understand at first.
If anyone feels like writing a better set of instructions, go for it.
Screenshots
Category List
Quest List
Yeah, with 1 quest.
![[Image: 27xdk0p.png]](http://i48.tinypic.com/27xdk0p.png)
Quest Description
I was testing various things, okay?
![[Image: t0nwrd.jpg]](http://i45.tinypic.com/t0nwrd.jpg)
v2.1.0 New Features
Battlers, item quantities, and ability to be called from any scene.
![[Image: vcxonc.png]](http://i45.tinypic.com/vcxonc.png)
Demo
Now with several examples of the various things you can do!
(And it still doesn't cover everything possible!)
http://www.mediafire.com/download.php?zj0lm3nj3fk
Terms of Use
You can use it or repost it wherever you want, just make sure to credit me.
If you complain about the images, I will punch you in the face.
If you refuse to try it because you don't like the images and don't feel like making your own, I will punch you again, only harder.
Lastly, I would love to see the kinds of ideas people come up with for this.
Special thanks to DerVVulfman for support, suggestions, and encouraging me to make something that runs outside of Ninja Penguin.
