GIAKS'S PROFILE

Thanks Bandito. I originally made the video to help some people on YouTube, but I figured I may as well post it here in hopes that somebody would find it useful. If I can ever assist, let me know :)

author=Rave
How to make it so "current" title screen would disappear after some time so user won't have to press space?

That is a very good question Rave! :) I'm glad you asked. This can be accomplished with 4 very simple script edits...

----------------------------------------------------------------------------------

We are going to start by going back into the Script Editor (F11).

On the left side, scroll down until you see Scene_Title.
We will be working entirely within this section of script.

On the right side, we need to find the * Start Processing section.

Just below that we will find "create_command_window" (it should be roughly line 17).
We need to add a Hash tag '#' in front of it, so the engine does not run that section of the script.

When you finish it should look green, like this: #create_command_window

Now go to the end of line 17 and press enter.
This should add a blank space at line 18. Here we are going to type 'command_new_game'. This tells the script to automatically run the new game command without any user input.

We are half way done, however before you can run it we still need to change up 2 lines of code.

Next find the * Termination Processing section.

In this section, just under the word: super
add the line: 800.times { Graphics.freeze }

This is basically how we get the "Splash Screen" to pause for a few seconds before continuing to the title. It seems that about every 200.times = 1 second. So 800.times = 4 seconds, 1200.times = 6 seconds...and so one. This will be how long your "Splash Screen" will display until moving on.
If you didn't want a splash screen you could leave this line out and set your title graphics to 'None' in the database.

To finish this off, on the right side find the * New Game Command section.
It should be down around line 105ish

Within this section find the line that says 'close_command_window'.
As we aren't running the command window, we can't close it. So put a Hash tag '#' in front of this line to make it appear as a comment so the engine won't run it as code.

It should turn green and end up looking like: #close_command_window

----------------------------------------------------------------------------------

...and that's it! Now you can run a Splash Screen(or not) to your map title menu without the need for any pesky user interaction. I hope this helped Rave. If I can ever assist, let me know. :)

I have to admit I'm sort of flattered about all this.

The law in general is shifty, copyright law being among some of the most slippery. So I won't get into copyright. I will say that as far as this tutorial goes, it is based out of logic...so I would like to believe that anyone could have come up with it, and I personally hold no copyright to it. The 'scripting' I used was provided in the default engine script provided by Enterbrain...so that may have to be taken up with them.

I am pretty confident that no law exists pertaining to the requirements of posting tutorials or the like online. Without getting into the semantics about what the word 'tutorial' means and personal opinions as they apply to the interpretative nature of communication. It seems that the author of anything online has the right to write as little or as much as they feel necessary to portray their ideas, just like the reader has the right to not understand and get frustrated because they don't get it. Sadly I believe this is one such case.

I would also like to point out that there is indeed small print...

author=ME, I wrote this.
Next I have saved the different components of my title screen as individual .PNG images and imported them into the project. The image 'title_para.png' I have imported as a parallax background, 'tut_splash.png' I have imported to Title 1, everything else I have imported as a Picture.

*If you don't know how to import into VX Ace, you may be reading the wrong tutorial.

I have of course enlarged the small print...so it is no longer small, however if you want to read it for yourself, click the button to the second part of the tutorial and presto! You may now see the small print(be it small, it is still print). This can be verified in your video as well. I point this out because it amuses me.

Finally, the law that is prominently subject in this case is about hacking. All this other stuff aside I would caution you as hacking is not so much a slippery slope. I would like to point out that usc title 18 part 1 chapter 47 section 1030 is all about it. As someone with a degree in criminal justice I would have expected you to play your cards a little closer to your chest, and not openly threaten to hack a website. I will close by saying that I do not consent to having this page, or any other page I post on this website or any other website, hacked. I can not speak for anyone else involved in this website, though logic would lead me to believe they feel the same. That being said, it is entertaining thinking that the clock may be ticking...tick tock.

I would like to get the posts on this tutorial back to being about this tutorial, be it opinions about its flaws or questions about...stuff. I rather enjoy discussing stuff.

...as really quick final side note, good luck to Nicholas Power. I hope they will not be infringing on copyright.

author=tx3000
So you're saying to import pictures into RPG maker, but then don't bother explaining the process for importing the pictures.

REALLY!!!

You must have missed the fine print just below that. I will admit I did take a few things for granted, like the reader would know how to create new maps and import resources. If RPG Maker had a text book those two things would be early chapter subjects, this tutorial would be a mid-chapter extra credit type thing(this is of course just my opinion). I can understand your frustration though, and although this tutorial is not a tutorial on how to import resources...

This tutorial is:
HOW TO IMPORT WINDOW SKINS by bigbadke12

Although this tutorial's primary function is to import window skins in RPG Maker VX, with just a little bit of logic you could apply the simple steps laid out by bigbadke12 to import any type of resource in any version of RPG Maker.

If any other questions or comments arise, I'm more then happy to discuss...stuff. In fact I rather enjoy discussing stuff. :)