$TEST Overwrite

Features:

So, as some of the more advanced may already know, the $TEST variable holds the boolean for whether your game is being playtested or not.
 

As other may know, by using the 'command ine' to open an rpg maker game, you can add the command 'test' that will begin playtest mode. This obviously is not ideal as regular players could potentially use this to gain access to areas of the game they should not be permitted.
 

Anyway, this script changes the value of $TEST.
 

When using this script your game will not be in $TEST mode unless a specific command line argument is supplied. This can be any phrase you wish. There is also the option to automatically add this argument to your command line -WHICH SHOULD BE DISBALED FOR YOUR GAMES RELEASE !!
 

I have also introduced a new value that can be checked as well. This value is DEK::gm? and will return true / false based on whether the GM_Argument is specified.
 

Screenshots:

Notice, the command line arguments are more than just 'test'. This is because new argz are being provided to the game at runtime that change the value of $TEST.



How To Use:

Plug 'n' Play

Demo:

Can be found HERE.

Script:

Can only be found from demo link above under the script page 'DEK::$TEST' - also requires 'DEK::AARRGG'.

FAQ:

None Yet.

Credit:

Dekita / DekitaRPG

Notes:

Remember, this will overwrite the value of $TEST - so if the new vaue of$TEST is not true certain information may not print to the console and you will not be able to use features such as 'hold ctrl to go through stuff'

You don't just have a script on pastebin or something you can link to? I don't really want to download a demo just to see this.


If the purpose is to stop players adding a command line value to put $TEST on, couldn't you just add a $TEST = false in main for the release version? I was going to take a look at how you did it before asking that, but ... demo.

Sorry dear, I am trying to avoid having to upload single scripts now as I always end up with loads of bits of code here and there. I feel housing it all in a simple demo will be much easier for me to manage.

Also, cause this script requires my command line arg script as well its best to supply within a demo (imo). :)

But yea, you could just put a $TEST = true, how my script allows you to specify a new $TEST arg - which you could use after distribution to play your game in test mode. :)

Edit:  Demo's tiny in size anyway :) (2.88MB)