Game
NukeOTron Sucks Collection
11 years ago

Before Dragonian, I tried making an RPG.


Since SOL is associated with the collection, this article is associated with the NukeOTron Sucks Collection.

Before I made Dragonian, anything with ninjas, and even Super Starton, my first completed game, I wanted to make video games. My first project, the first game I ever tried to make, was Staff of Laria.

The history of this game dates back to my early teens, after having a strange dream that became the start of the tale, and the story started.
The original version was on the OHRRPGCE, the Original Hamster Republic RPG Creation Engine. It didn’t get far, but trust me, OHRRPGCE is a very useful RPG maker.
The story back then was shallow.

Later on, I discovered RPG Maker 2000. It was effective. The story is a bit more developed, but not much.

Anyway, since the problem with RPG makers is that you can’t make your own battle system. …which led to the GM version. Personally, my vision for that game was to use FMVs for battle animations. …well, it’s close enough. Also, I would’ve loved it if there were FMVs everywhere. If anything, I’d like it to look like those multi-disk epics that were popular in the ’90s.

Still, perhaps Staff of Laria has (or had) a following. It’s good to see what came before Dragonian. I really do want that game made someday, so communicate if you’re willing to back it up.

For your game-making pleasure, I have for you the original script, extra source code for any one with GM, and original concept drawings.
Just be aware, this isn’t for the faint of heart, or little little kids.

https://drive.google.com/file/d/0B4CjsB0TaO9zV0RtaF9KZUVmSGM/view?usp=sharing

1
4


0 comments

Loading...

Next up

Okay, so I'm doing something either crafty or questionable: drawing the objects with Draw GUI.

It works, doesn't it?

On the plus side, the tile layer ISN'T overlapping, and Draw draws objects.

On the other hand, NOW the tile layer lags during camera movement.

I guess I'd better let everything else lag for consistency (somehow), or fix the lag.

The floor's movement, being a view drawn onto a surface, is still one frame behind.

However, I figured it's more efficient to draw walls separately than to use blocks for indoor segments. They can stretch and keep doing the depth math accurately.

It took a while, but I got rotating flat sprites going.

Technically, it's a polygon, but it works.

If I were to do sprite-stacking, I have a basis, but my primary use for this is rotating attack animations.

The character and movement tests are going well, but...

OH. THAT's what Draw GUI does. It's not crunchy.

Then again, I thought that drawing a view to a surface would work the way I expected, but it ain't.

...huh.

Didn't realize that debug mode was different on that version of Game Maker. Also shows WAY too much for players to use.

You can also click and drag some of those elements.

On one hand, I'm getting there. On another hand, "No, I'm not."

Then again, I probably forgot something important about layering the old-fashioned way, and something about using a view as a texture.

Part one of my zany scheme for a new project worked.

Using two Views, I can draw one squished, rotatable View as a texture, meaning I can use tiles for an isometric perspective.

Now, the tricky part is where everything looks like a pop-up book.

Dang it. I got the math right.

The real trick now is to optimize it. It's easier to do since it's technically all 2D.

Here. Just to give you an idea as to what I'm going for.

The character and GFX are temporary, but they help me realize what I want to do with the engine.