Ever get those times where you create a brand new shop in your game, decide to go test it out, only to realize you forgot to give yourself any gold since you’re doing a play test?
Or maybe when testing out a new area only to forget you haven’t given them any items to use? Or weapons? Or armors?

Yeeeaaaaaaaaaaaaaaaaaaaaah… We’ve been there a lot, too

Sure, it’s only a few more minutes of clicking away to create a new Autorun Run event each time, but those tiny moments of forgetfulness add up.
That’s why we’re going to present to you a new tip that will help you save your valuable time!

Inside the VisuStella MZ Core Engine (which you can download from our Sample Project!), we have a special plugin parameter that runs a Common Event only during play test sessions! You can find that plugin parameter by going here:

Plugin Parameters => Quality of Life Settings => New Game > Common Event

Let’s change this setting to a Common Event in our database! We will use Common Event 1 for now, but you can pick whatever you want.

Inside that common event, let’s give ourselves a bit of starting gold, basic batch of potions, some gear, and a few levels each time we start a new play test session:

As mentioned before, this common event will only run during a play test session! This way, whenever you are testing out new shops, locations, or dungeons, your player character won’t be stripped of preparation! This common event will not run on a finished and deployed game so don’t worry about that bit at all!

Hooray! We can test shops without empty wallets now!

This can help save you a lot of time when debugging your game as it cuts down on the amount of preparation work needed to be done when testing new content.

Now then...

For the more advanced users who would like to add in every item, weapon, and armor at once, there’s a script call function you can utilize to save yourself some clicking time! We’ll provide you the snippet here:

Copy/Paste Code:

const items = $dataItems.concat($dataWeapons).concat($dataArmors);
const quantity = 10;

for (const item of items) {
if (!item) continue;
if (item.name.trim() === '') continue;
if (item.name.includes('-----')) continue;
if (item.itypeId === 2) continue;
$gameParty.gainItem(item, quantity);
}

For those wondering, this code will exclude and filter out any items with empty names, have ----- in the name, or is a key item.

Your common event should look something like this:

Now, when we run the game through play test mode and go to our items menu, we should see 10 of each item! Minus the above mentioned filters of course.

Yayifications! That’s awesome! So much time is saved and we have everything we need for play testing!

We understand that during play testing, not everything goes according to plan so it never hurts to have resources available at all times to make sure every other situation is prepared for. We hope this tip will help you speed up your playtesting sessions and allow you to focus on creating the content you want with less frustrations!

Happy RPG Making!

‍