Introduction Read! A script that makes your players read something you like! Make books or scrolls with any picture program and make them appear, ready to be read!
Features v1.0
Make the player read a picturebased book.
v1.1
Fixed bug with amount to go forward.
v1.2
Added sounds setup.
v2.0
Read_A_Book! > Read;
No more stupid pagessize input, no more stupid .png or .jpg input;
Read a scroll, instead of a book;
Now a book/scroll can also be read without returning to the itemmenu;
Sound setup disapeard!? (will not be included until request);
More easy and shorter callscript functions.
v2.1
Bug fixed, background is disposed now when a scroll or book is closed.
v2.2
Some more easy use of pictures, as well as some extra functions (useing spreads for example).
v2.5
Code can be placed in the itemnote field and will be executed;
Automaticly read if the code comes from an itemnote;
A more clear code;
Some extra call script functions.
To come features - Only on request.
Script Read.txt ( 18.23K )
Number of downloads: 314
For the variables "book" and "scroll", you'll have to set the name of the book/scroll ('picturename'). For the variable "back", you can setthe name of the back images of a book. If you leave it for what is, it'll use the default settings from the script-setup ("BACK_PIC"). For the "draw_style", you can change the way of how you've set up the pictures. This variable is optional. You do have to set "back" if you want to use this. If you leave it empty, it'll use the default you've set in the script-setup ("DRAW_STYLE"). For the variable "from_item", you can set if you want to return to the item window when you close the book/scroll. But if you leave it for what it is, it'll see for itself if the code came from an item or not (recommented).
Use correct filenames for your book! First of all check the script-setup and make it to how you want it before making your pictures. Look at the "BOOK_MAP", this is the place where you're going to put your pictures. Now you can make the pictures... Though be aware! You need a to make a background for your pages to show on. Size it (max) 544*416 and name it whatever you want. Go to the scriptsetup and put the name of that background after "BACK_PIC". Next you are going to make the pages with your text and/or pictures and all, that's all up to you since they are pictures, so everything is possible. Just go and start making your pages with any size you like (change the "DRAW_STYLE" in the script-setup to your style). Every page should have it's own picture! When you're done with a page, and you're going to save and name it, set the name like this; 'bookname-pagenumber'. So if you just created the 2nd page of your book called 'ghost', the name of the picture must be 'ghost-1'. Make sure you see that the second page of the book, has the number 1. So the first page has the number 0. For the scrolls, first check in wich map the pictures need to come. After that, just go and make some nifty looking pictures that will be shown and can be scrolled by the user in all 4 directions. PS: RPGMakerVX only supports png/jpg/jpeg picture-files.
The last 3 settings of the setup; CENTER_OFFSET, NEXT_PAGE and PREV_PAGE, are explaind below. {CENTER_OFFSET} The center_offset setting defermens the y-offset of the pages from the middle. So if you want your pages not to be drawn at the very middle of the back-picture, you'll have to set the center_offset to any given number you want the pages to be offset from the middle. For example if you have page-pictures that are sized 270*412, and you want them to be shown, not directly on the center of your background, but in the center of each half, you want to set the center_offset to 2 since this will center them out on every half. {NEXT_PAGE} This setting determens wich key needs to be pressed to move the pages to the next. You can only use known inputs by the game. Though, you can extend this by useing various other scripts that will allow you to use all inputs from your whole keyboard. {PREV_PAGE} This is actualy the same as the next_page setting, only this will bring the reader to the previous page. For the scrolling part of the setup, the 4 SCROLL_directions and SCROLL_SPEED remains. {SCROLL_UP/DOWN/RIGHT/LEFT} For the directions, just changes the input to what you prefer, though the default are the most usefull (in my opinion). {SCROLL_SPEED} The scrollspeed, is the amount of pixels the scroll moves when the player presses one of the directionbutons once.
Installation Put the script above main. Customise the script to your needs. Credit me pls.
FAQ Comming soon.
Terms and Conditions Credit me with site, and the script is free for use in NONCOMERCIAL projects. If anyone want some changes, please pm me or post it here, I'll track the topic.
For the past couple of months I've been learning RGSS and I've got the basic stuff down such windows, variables, conditional statements, ect. But, I can't see myself making big scripts such as a jumping system or a side view battle system. I was wondering how you learned to script because I really want to know how to script really well.
Thanks in advance.
Hey there,
Well I don't make battle neither though I can still teach you some things :)... The way I've learned to script is by reading other scripts for the most part. I've allways been interested in other peoples work but this time I though I had to try to make something myself...and it worked!! The most importand thing when you go scripting is (at least in my case) that you want to make something to help an other wich can't script. You also need to feel the competition that's around in the scripting-community. Cause, I have to say, if you get pushed to get a sertain request done before an other scripter does, you feel POWERFULL!! :P So that's an other thing... You also don't need to be afraid to learn from others or helpfiles. When I write my scripts, I actualy always have the helpfiles open to look things up I don't know or remember. Then, you must be calm, cause you need to try the script a lot of times. When I write a script, I test it after almost every changes. First I set up the major structure. Like when I make a window-script or part of a script I start with something like this:
CODE
class Window_Name < Window_Base def initialize(x,y,width,height) super(x,y,width,height) refresh end
def refresh self.contents.clear draw_contents end
def draw_contents draw_something(with, some, parameters) end
def update refresh if @something != @what_it_should_be end end
So that's also very important. Then, the biggest thing I learned scripting from is TRIAL AND ERROR. That's the most irritating way to learn something, cause it's more ERROR than TRIAL, but it does the trick realy good.
So that's it how I did it. Now it's up to you. Do some requests (if I didn't do it allready :P) and learn from them.
Hope that helped you out a little. If not, keep your eye on the Scriptology-topic (see my sig) where I'll be updating for my scripting(video)tutorials. Perhaps they're going to be usefull for you one day ;)
For the past couple of months I've been learning RGSS and I've got the basic stuff down such windows, variables, conditional statements, ect. But, I can't see myself making big scripts such as a jumping system or a side view battle system. I was wondering how you learned to script because I really want to know how to script really well.
Thanks in advance.
Hey there,
Well I don't make battle neither though I can still teach you some things :)... The way I've learned to script is by reading other scripts for the most part. I've allways been interested in other peoples work but this time I though I had to try to make something myself...and it worked!! The most importand thing when you go scripting is (at least in my case) that you want to make something to help an other wich can't script. You also need to feel the competition that's around in the scripting-community. Cause, I have to say, if you get pushed to get a sertain request done before an other scripter does, you feel POWERFULL!! :P So that's an other thing... You also don't need to be afraid to learn from others or helpfiles. When I write my scripts, I actualy always have the helpfiles open to look things up I don't know or remember. Then, you must be calm, cause you need to try the script a lot of times. When I write a script, I test it after almost every changes. First I set up the major structure. Like when I make a window-script or part of a script I start with something like this:
CODE
class Window_Name < Window_Base def initialize(x,y,width,height) super(x,y,width,height) refresh end
def refresh self.contents.clear draw_contents end
def draw_contents draw_something(with, some, parameters) end
def update refresh if @something != @what_it_should_be end end
So that's also very important. Then, the biggest thing I learned scripting from is TRIAL AND ERROR. That's the most irritating way to learn something, cause it's more ERROR than TRIAL, but it does the trick realy good.
So that's it how I did it. Now it's up to you. Do some requests (if I didn't do it allready :P) and learn from them.
Hope that helped you out a little. If not, keep your eye on the Scriptology-topic (see my sig) where I'll be updating for my scripting(video)tutorials. Perhaps they're going to be usefull for you one day ;)