AgentPaper

Awesome. I should have a chance to try it out later tonight.

Ah, I see. Anyways, I'd prefer the method that just requires commenting out a section of code once I'm ready to release, rather than needing to find and delete data files whenever I change something.

That sounds fine, though if the .data file is inaccessible, how would I get to it to delete it? Edit: Actually, I think I've come up with an easier/more secure version: Add a section of code that runs when the game starts, which looks for .txt files for all of the lore items, and then creates .data files for each of them. Then, once I'm done adding lore items, I can comment out that section of code. Simple, and hassle-free.

Ok, finally got around to looking at it. I see you've got it set up so that it shows both the list of lore items and the window which I assume will eventually show the text both showing at the same time. Instead, I'd prefer it if those were two separate screens, so that each of them can take up the whole screen if necessary. Then, you can have the list of lore items be 14 tall and 4 wide, and if there's more than 56 lore items (and there will be), it scrolls left and right to show more, rather than up and down. Example: ! Lore Item 1 & Lore Item 15 @ Lore item 2 * Lore Item 16 # Lore item 3 etc... $ Lore Item 4 % Lore Item 5 ^ Lore Item 6 etc... Then, the lore text itself would have it's own full-screen window, which shows the text and such, and they can change pages with left and right, and scroll through text with up and down.

Awesome, I'll test it out later tonight. for changing pages, simply left and right arrows should work fine. For the text field, I'm not sure what you mean, so I can't say which of those choices I'd prefer. Just use your best judgement I suppose Having the ability to scroll sounds good too, I can use that for some and multi-page for others. For the text data itself, a separate .txt file seems the simplest and easiest way to handle it. The text files should be named based on the order they'll show up in the lore file, and then other information like the title, any pictures to include, font, and so on would be set in the text file itself, using whatever format is easiest to implement.

1) Windowskin. I may want to add a background to various lore objects, but that should be handled by the picture-adding program. (I'd simply add a screen-sized image at 0, 0, set to display below text) 2) It should cover the full screen, just like the other menus. 3) If the player doesn't have any lore items, the Lore button in the menu should be grayed out. Items that haven't been collected should show up as a line, (IE: ---------) so the player can see if he's missing any. 4) No need for a background on the lore menu. And thank you very much for helping me with this. If you don't have much time, don't worry about most of the complex features, at least at first. Just a simple version that's functional without icons or pictures, formatting, multipage, etc. would be very useful.

I need a script that will allow the player to peruse various books, sticky notes, infospheres, scraps of parchment covered in blood, ancient runes, picture vases, or whatever other kind of strange information-carrying object I decide to implement. In the most basic terms, what I need is a script that adds a new option to the menu screen called "Lore", which shows you a list of all the lore items you have collected so far. When you select one of the items (IE: Abdul's Log, Page 4), it brings up a bunch of text that you can read through. Each lore item shouldn't actually be a item you can see through the normal item menu, but just a switch that gets turned on in the lore menu when you find that item. Optional additional features: - Display an icon next to the lore object similar to normal items. - Add the ability to display one or more pictures in the text, using x/y coordinates. - Add the ability to choose whether the picture shows above or below text. - Some way to automatically format text to fit around the aforementioned pictures. - The ability to create in-line pictures. - The ability to control the font, size, and color of text, and also to bold, italicize, and underline text. - The ability to scroll through text. - The ability to control whether pictures scroll with the text or not. - The ability to have multi-page objects. - Extensive comments within the code so I can see how it works and tweak it as needed. - Any other features you're awesome enough to think. For doing this, you will be rewarded with credit in my map and my everlasting love and devotion. Also a kitten.

Great updates. Nothing overly fancy, but it's the little stuff like this that make a game feel really polished and well-made. Glad to see you're still working on this.

I've got a script that looks like this: class Interpreter def BH_Load_Map # Do stuff end end Then, in a auto-run event, I have this: Script: BH_Load_Map From what I know, this should run the BG_Load_Map script. However, instead I get an error: NameError occurred while running script. uninitialized constant Interpreter::BH_Load_Map This seems like a really simple thing to do, but apparently I've ***ed up somewhere along the line and I can't for the life of me figure out where. Any help? Edit: Nevermind. Apparently you can't capitalize method names. It's working now. (well it's not, but it's a different problem now, heh)

Ah, that's simpler than I thought. I got thrown off because of the multiple lines. Anyways, I still prefer the other method, just because it's easier to see what's going on, and where. I'm not really worried about the length of my code right now. Thanks again for all the help, the code is working perfectly now. It might be nice to know why I need to divide by 10 instead of by 100 to get the correct result, but that's not really a big deal.

I'd favor the current sorting method. I think of it like this: If someone is interested in a RPGXP tutorial, they almost certainly won't be interested in a RPGVX tutorial, because that's not the system they're using. However, someone who's looking at a RPGXP tutorial could certainly be interested in also looking through RPGXP support, or RPGXP scripts, because they're very closely related to each other. Essentially, RPGXP scripts and RPGXP tutorials are more closely related than RPGXP tutorials and RPGVX tutorials. So, it makes sense to put the things that are more closely related into the same subforum. I don't think there's any real problem with having a lot of sub-forums, as long as the groupings and progression is logical and easy to see.

I'd love to enter a mapping contest. I don't think I'd win, but it'd be a good way to practice, get feedback, and see what other people are doing that I can borrow from.

@ForeverZer0: I think that script is a bit above my head, haha. I'd prefer to use a script I understand, even if it's not the best one, just so I can change it if I need to. Thanks anyways, though. @diagostimo: Thanks, I think I'm on the right track now. I've actually got SDK up, and I'd eventually like to be able to release this as a script for others to use as well, basically a unified stats and combat mod, since the default stat system seems pretty terrible. With that in mind, I made the following: class Scene_Title def main_database # Load database $data_actors = load_data("Data/Actors.rxdata") $data_classes = load_data("Data/Classes.rxdata") $data_skills = load_data("Data/Skills.rxdata") $data_items = load_data("Data/Items.rxdata") $data_weapons = load_data("Data/Weapons.rxdata") $data_armors = load_data("Data/Armors.rxdata") $data_enemies = load_data("Data/Enemies.rxdata") $data_troops = load_data("Data/Troops.rxdata") $data_states = load_data("Data/States.rxdata") $data_animations = load_data("Data/Animations.rxdata") $data_tilesets = load_data("Data/Tilesets.rxdata") $data_common_events = load_data("Data/CommonEvents.rxdata") $data_system = load_data("Data/System.rxdata") # Calculate actor stats calc_stats # Make system object $game_system = Game_System.new end def calc_stats # Constant used to determine rate of inflation. # EXTREMELY sensitive. Do not increase above 1.1. c = 1.055555 # Cycles through each actor for actor in 1..$data_actors.size # Cycles through each stat for stat in 0..5 # Calculates each level's value based on the level 1 value of the stat. # Set initial stats to 1-999, with 500 being midline (starts at 5). base = ($data_actors[1].parameters[stat, 1] / 100) for level in 1..99 equation = base * 0.25 * (level + 3 * (c ** level)) $data_actors[1].parameters[stat, level] = equation end end end end end However, this just ends with all of my characters stats being set to 1. The initial value of my character's stats is around 500, or 5000 for HP, which should result in a base of 5, or 50 for HP. It's definitely running though, because my character, who is starting at level 28 for now, has their stats set to 1 when their default level 28 stats should be 52. Any idea what might be causing this? Did I get the formula wrong? Also, any tips on making this more compatibility-friendly, in case I do end up sharing it? I'll most likely be releasing a SDK and non-SDK version, so tips for each would be great. Edit: Ok, turns out the problem was that I needed to divide the level 1 stat by 10, rather than 100. No idea why that is, but it's working perfectly so oh well. :P I still would like help with making this more compatibility-friendly, but for my purposes at least this is working great. Thanks for all the help, guys. Once I get the numbers set up a bit better, I'll post the scripts in case anyone else wants to replace the old combat system too.

Ok so I have this: class Stat_Mod def main c = 1.055555 base = 5 for a in 2..5 for level in 1..99 equation = base * 0.25 * (level + 3 * (c ^ level)) $data_actors[1].parameters[a, level] = equation end end end end But it doesn't seem to do anything. I specifically set my Dex stat to be 1 at level 28 so that it could be set to the correct value, but it stays at 1. Do I have to do something to make this run when the game starts?

Oh. Then, how would I do that? I haven't used Ruby for anything before, only C++ and RPGXP scripts. Edit: Also, I figured out that the reason for my other bug was that the script was rounding everything into integers. I think I've fixed that now.