Interview with Aura

A painting by Aura

The first time when I saw A Lill’ girls Tale by Aura, I was amazed by how beautiful the levels are. And her game has to offer even more. A nice story, and some real game puzzles. You definitely need to check out her game. But first, an interview…

Can you tell us a bit about yourself? How old you are, where you live, how you spend your days, etc?

I am 24 years old. I’m living in Germany and I love to paint, write, sing also. So currently my art is what I’m living of…

Read more…

Release 0.21: Let characters walk

Finally I have the release that everyone is waiting for: characters that walk! And not only NPC’s. You can let your hero or even monsters walk to a certain location.

This functionality opens a lot of cool possibilities, such as letting a guard block an entrance, and moving him out of the way once you have a certain item or password.

Screenplays can also become more dynamic by letting characters move to certain locations.

So how do you use it? Like this:

Actor1 walks to 5,-2

Which means: Let Actor1 walk 5 tiles to the right and 2 tiles to the top.

The first number is left and right. If it is negative, you walk to the left, if positive, you walk to the right. If you don’t want to walk left or right (only down for example), it must be 0.

The second number is up or down. If it is negative, you walk up, if positive, you walk down.

To give you some examples

  • Walk 2 tiles left: Actor1 walks to -2,0
  • Walk 3 tiles up: Actor1 walks to 0,-3
  • Walk 1 tile right, and 3 tiles up: Actor1 walks to 1,-3

Just experiment with it a bit and you will get the hang of it! :).

In the future I will make this way easier (just selecting the position you want to go to with the mouse). But for now this is it.

Release 0.20: Pixel movement

Wow, it took more than a year to finish this release. But don’t worry, it’s finally here! And I promise that the next release will be finished faster.

So why did it take so long? Well, I completely rewrote the movement of the characters. They can now walk with pixel precision, instead of being bounded to walking on the middle of a tile. I also improved the camera movement so it’s way smoother now.

I used the Box2D physics library for this. Which also enables some other cool stuff for the future. For example when you would hit an enemy, it can be swiped back and push other enemies aside.

Why do we need this?

Well, pixel precision movement, and 2D physics, open a lot of possibilities for the future. The most important one is probably making cool, modern action combat. Like in the game CrossCode shown below:


Why do we need it now?

Because it had to be in place to support other functionality, such as letting NPC’s walk to another location. This last feature has been requested by a lot of you. But before I implemented that, I fist needed to put this pixel precision movement into place.

So what is next?

The features you have been requesting so many times: new actions!!!

  1. Make NPC’s walk to a certain spot
  2. Make NPC’s disappear
  3. Lock doors
  4. Let the player choose a response

So head over to and check it out!

Fight Scenes


A lot of our members of our community want to be able to hold fight scenes. So naturally, fighting, or “battles,” are important to include in your game. Unfortunately, RPG Playground does not have any sort of fighting function yet, and that discourages a lot of people who want to make a game. While we hope that one day we won’t have to find roundabout ways to include this, it still is possible for at least one fight scene.

A few quick notes, though. This method is heavy in the scripting department, and takes a lot of play testing to guarantee it is the way you want it. Also, none of the NPCs can move or “die,” which causes issues if they are blocking the path. My advice is to make one final boss, which can only be defeated if the character has the right equipment.


mom says “Take this dagger – you’ll need it to protect yourself in the woods!”

invisible-actor says “You received a +1 dagger!”

hero receives token “dagger1”

This is a really simple way to have your character receive a weapon or armor. An invisible actor can always be used to tell the player that they had gained or lost something, so it is something that will appear often in these scripts. As the character gains a stronger weapon, make the “stat bonus” higher, regardless of the weapon. A quick note is to not make two different weapons with the same stat boost.


if hero lacks token “longsword2”

    invisible-actor says “You open the chest and get… a +3 Shield and a +2 Long-sword!”

    invisible-actor says “Unfortunately, you cannot carry more than one weapon. You lost all other weapons and/or armor.”

    hero loses token “dagger1”

    hero loses token [list all other weapons and armor that they might have acquired.]

    hero receives token “longsword2”

    hero receives token “shield3”


    invisible-actor says “The chest is empty.”

Of course, there are a few problems with this. First of all, if the hero goes to another chest, loses his new Longsword, he can come back and re-use the chest. For the ambitious people out there, the quick fix is to make another if/else statement resulting in more tokens. Once again, this is just the “Easy” way of doing this. If any of you would like me to describe how to fix any of the problems with the script I describe, just leave a comment below.


boss says “Fight me!”

hero says “Bring it on!”

    if hero has token “axe10”

        if hero has token “armor5”

            invisible-actor says “You fight! He swings his sword, but you dodge easily. You swing at him with your ax, cutting him in the shoulder! He strikes back, but his blow bounces off of your armor! [Etc…]”

            invisible-actor says “You defeated the boss! You gain 100 gp and can move on to the next level!”


            hero says “If that sword strikes me, I’ll die. Maybe I should grab some armor first…”


        invisible-actor says “You fight! He points at you with his finger and shoves you aside quickly, and you fall in embarrassment. ‘You are unworthy,’ he says.”

Here, we use a more complicated if/else statement. The more factors, and the more descriptive you get, the better the fight scene will be. Unfortunately, you cannot give the player a choice of what to fight with, or what moves to use. You can use tokens, however, to give the player a choice of the character’s preferred moves. This, of course, takes a lot of effort on your part to create a scenario for every ability.

In addition, you can use a token to give the character actual (token) currency, which may be used later. I also recommend creating a token for defeating the boss. This way, when the character moves forward in the game, he cannot act in the next level unless he has that token.

There are many other things you can add to your fight scene, making it into a better game. If you have any suggestions for another post, another piece of script, or anything else – leave a comment! I’ll try my best to clear everything up!

A Love-Hate Relationship with the Base-Attack Bonus

Hey, guys! It’s someone different this time. My name is Sean, I’m the best, et cetera. But enough about me! I’m here today to talk to you about a system in the popular role-playing game Dungeons and Dragons: The Base-Attack Bonus. And oh boy, do I have a lot of opinions on this thing. Let’s delve deep into the world of third edition Dungeons and Dragons and all of its… uh… quirks. I’m… I’m so sorry.

First, in order to understand the Base-Attack Bonus, one must understand the rules of Dungeons and Dragons combat. So, we start off with an explanation of the combat rules of Dungeons and Dragons.

In Dungeons and Dragons, at least in any edition that uses the d20 combat system (sorry, THAC0, but you’re too convoluted for your own good), any given creature has what is called an Armor Class. This is determined by the armor of that creature, whether it be the plate mail of a knight, the scarlet scales of a dragon, or the sweater that one NPC’s mom made. To make a long story short, an Armor Class is a number that represents how hard it is to damage a creature. In combat, when attempting to damage a creature, the aggressor must make what is called a “to-hit roll.” This is a roll of a 20-sided die with static modifiers added on. If the result equals or exceeds the target’s Armor Class, then the attack hits. If it does not, then the attack fails.

A d20

The Base-Attack Bonus is a static number that is added to the to-hit roll. The number is determined by your class and level, i.e. a more combat-oriented class’s BAB grows more quickly than a more utility-oriented class’s. When a class’s Base-Attack Bonus grows to 6, they get a second BAB. They now have access to the ability to attack twice in one turn. The to-hit roll of the first attack has the first BAB added on while the to-hit roll of the second attack has the second BAB added on.

In-universe, this system can be explain by the character gaining experience. Maybe the character has gotten so good at doing one attack that they have began experimenting with a two-hit combo. The second hit just isn’t as well-practiced as the first, that’s all.

Now, that seems like a perfectly sound system, both mechanically and in-universe, right?


The answer, dear reader, may surprise you.

The answer is “eh.” Other acceptable responses are “meh,” “kinda,” “sorta,” and “well…”.

At first, the system is impeccable. The second hit isn’t so much less accurate than the first that it’s unusable. The fighter can, conceivably, swing his sword twice in the span of 6 seconds (the amount of time a turn in D&D represents). However, the BAB doesn’t just cap at 2 hits. At higher levels, some classes get to attack a ridiculous number of times. Sorry, monks, but it’s hard to believe that you can punch someone harder than the fighter can swing his 7-foot greatsword eight times in 6 seconds. Mechanically, the system becomes completely neutered, too. In order to compensate for the bonuses (BAB, stat modifiers, magic weapons bonuses) alone eventually having a value greater than that of the highest roll achievable with a d20 roll, the game designers had to make monsters with Armor Classes so ridiculous that the initial +30 to-hit attack could have a chance in hell of missing. In doing so, they made the monster have such a good armor class that the other hits, ironically enough, now don’t have a chance in hell of hitting. Slow clap.

So, every hit besides the first eventually become effectively useless.

You can theoretically hit this guy four times in one turn, just like how I can theoretically survive being shot in the head.
You can theoretically hit this guy four times in one turn, just like how I can theoretically survive being shot in the head.

This problem began in third edition and was never corrected in subsequent versions of third edition. It eventually even carries on into fourth edition.

Ah, you thought that this would be a paragraph about fourth edition, did you? Well, since we don’t talk about garbage in this household, this paragraph will instead be about how 5e made everything in the world right again. How did it manage to save a system so horrifically eviscerated by its own designers? Acquire a copy of the 5th edition Players’ Handbook and find out! Open up to any one of the classes and look at the Base-Attack Bonus! Huh? You can’t find the Base-Attack Bonus, you say? Of course not, because it’s not there. Knowing that saving the Base-Attack Bonus would be like saving a pig already in the oven (read: damn-near impossible), the designers just ate the metaphorical delicious roast pig, learned from their mistakes, and tried a new approach.

Meet the Proficiency Bonus, basically the older brother of the Base-Attack Bonus. Now, I have a bone to pick with this guy, too, but for right now, in this post, it is the lord and savior, as well as the messiah. It might also get honorary Buddha status. I’m not sure yet.

The Proficiency Bonus is a static number added to all rolls that a character makes with “proficiency,” basically performing a task he or she is good at. This includes attacking using weapons with which the character is familiar. Instead of having the clunky-looking +20/+15/+10/+5 of third edition’s Base-Attack Bonus, the Proficiency Bonus is a single number, ranging from +2 to +7, depending on the character’s level.

And what a world of difference this makes!

Instead of making the designers give monsters Armor Classes so astronomically high that Lil’ Wayne would be impressed, the designers can now give monsters Armor Classes that make sense. And instead of telling the combat classes to shove off and deny them the extra attacks they had in earlier editions, 5e just gave all of the extra attacks the ability to use the full Proficiency Bonus. Huzzah! Now your second hit actually does something.

You can actually hit this guy four times in one turn now! Rejoice!

To top it all off, because the Proficiency Bonus allows the characters to keep the feeling of their character slowly getting better with time while also allowing them to attack more than once a turn, none of the in-universe explanations have been lost, while fixing the broken Base-Attack Bonus system.

Even while multiclassing (having one character be multiple classes, say, part fighter and part ranger), the Proficiency Bonus– Wait.

Could this be?

Dear readers, I’ve spent around 1000 words bashing the Base-Attack Bonus and raising the Proficiency Bonus to a pedestal it only kind of deserves to be on. But can it be that I have something positive to say about the Base-Attack Bonus?

It’s better for multiclassing because the extra attacks in 5e are class-exclusive features. There.

As it stands, the Base-Attack Bonus is not bad… in concept. Much like how communism sounds really hype on paper but in practice leads to, more often than not, tears and misery, the Base-Attack Bonus sounded like a good idea at the time, but ended up being the most horrendously broken thing in third edition… is what I would be saying if magic in Dungeons and Dragons did not have the ability to bend the entire game system over its knee and spank it raw. Still, with a little bit of fixing, say, having the BAB cap out at a comfortable +9/+7/+5/+3 bonus, the system could work. Just please don’t let them bring back the old THAC0 nonsense.