As some of you might know, Fuzeboy’s project scope changed considerably during its development. There’s been an overhaul of features, specifications, goals and deadlines.
Originally thought to be a quick mobile only game, we then shifted our vision a bit to make it playable on desktops as well; now we decided to abandon the mobile world altogether to focus exclusively on the Desktop platform.
This opened up a ton of possibilities as we’re not limited to touchscreen inputs anymore. The very essence of the game changed, as we made changes to game mechanics, enriching and expanding the world of Fuzeboy.
Fuzeboy’s going to be a full fledged, complete platformer game for desktops (Win, Linux, Mac) but we’re not yet ready to show anything new to the world as I’m rewriting it from scratch in GameMaker Studio 2 while Darftey is reviewing (and adapting) all of the graphics.
We’re also starting a new project. Not because we suffer from shiny object syndrome (basically a disease of distraction) but because rewriting Fuzeboy from scratch, made it possible for us to reset our mental state.
Although far from a possible Fuzeboy-induced burnout, our mental state was then set for something new; different. That not only applied to Fuzeboy, but to both of us as a game development team. We took a step back and looked at our future as team Blocksword. And we saw things…
As we reviewed and re-started Fuzeboy, we reviewed our plans, projects and priorities as well. And we saw this…
Due to the overwhelmingly positive feedback we received, we’re now thinking about making it our primary focus. We’re also considering funding as I didn’t plan to live off of my savings for this long without publishing a commercial title.
Two projects, two options
Should we decide to crowdfund the new game, we will have to define a clear project scope and commit exclusively to that for the time it will take to ship it. In that case the development of Fuzeboy will be put on hold (let’s say we will change it’s queue priority). As of now this is the most probable scenario.
Should we decide to keep going without funding (or fail at funding), we’ll suffer from a bit of a slowdown. I will have to seek a part-time job (or something) while working on both games at our discretion (we would have zero deadlines and relatively more freedom in the way we manage and evolve our own projects).
All of this might annoy someone; especially those who were waiting for Fuzeboy anytime soon this year. Especially if they were waiting for a mobile game. We know it and we don’t like when people get annoyed because of us; we will make up for it.
To sum it up: we’re working on the new Fuzeboy while defining the scope of this second project and defining the resources we need to allocate to each of these projects. Just know that we could completely shift our focus toward this new RPG game very soon (we’re evaluating feedback).
Yet another official announcement: Fuzeboy is now being rewritten in GameMaker Studio 2.
After getting familiar with the new UI and the new GML functionalities, I’ve realized it made little to no sense at all to keep using GM:S 1.x. I’m already rewriting Fuzeboy from scratch so I might just use the new, improved IDE. I need a faster workflow and GameMaker Studio 2 definitely improves the workflow.
Coding with the new intellisense code-completion and making levels in the new room editor is just fantastic.
Since I’m working on a 1366×768 13″ notebook, I set the DPI scaling of GMS2 to 80% (76 DPI) so it doesn’t feel claustrophobic working in it.
I already feel better when coding Fuzeboy in GMS 2.
Me and Darftey have been developing Fuzeboy for five months now. We met in late Novemeber 2016, experimented a bit with prototypes and then started serious development in January 2017.
It all started as a small mobile game (you can see the touch controls in the image above) but soon it was clear Fuzeboy was no small game anymore; the mobile world isn’t fit for him. He’s bigger than that.
So here we are today officially announcing to the world that Fuzeboy will be developed uniquely for Steam (PC, Linux and Mac). A mobile adventure of Fuzeboy is still being planned but we’re not actively working on it (and it will be a different game).
In fact I am rebooting the development of Fuzeboy. From scratch. Still, I’ll be using GameMaker 1.x but this time the whole project will be PC oriented. We’re letting go of the many mobile limitations to expand on the gameplay mechanics.
While I’m starting to rewrite the engine from scratch, Darftey is already at work to come up with exciting new elements and ideas for the game. It’s going to take time and effort. It’s going to be exciting. It’s going to be big.
Fuzeboy's still in development so it's only natural that sometimes I take time to rewrite stuff, to fix things, to experiment and so on. We try, we break, we fix, we extend, we change. We evolve.One issue we faced from the start, is the game resolution. What we knew was that we wanted pixel perfect scaling no matter what. Remember that this game will be both for mobile and desktop.Here's my solution as of today.
Though parts of this article are still valid, we're no longer actively developing Fuzeboy for mobile. Indeed we're targeting the PC platform.
Not only that; I also wrote about a different way to scale surfaces in such a way I can avoid Pixel Decimation and achieve near perfect results with no notable distortions.
Fuzeboy cares about its height. The width depends on the monitor aspect ratio (within reasonable limits). The ideal height of Fuzeboy is around 240px. Keep this in mind.
Pixel Perfect, Full Screen, No Black Bars (didn't work)
This approach was the first I used. Since not every device has a vertical resolution that's a multiple of 240px, I allowed different devices to show more or less "game world".First I get the display vertical resolution. Then I cycle from 200px to 300px to see which one fits perfectly the device vertical resolution. If I don't find a perfect fit, I give up and just use 240px.
Fuzeboy on Devices, method 1
Game Vertical Resolution
Amazon Kindle Fire 7"
1024 x 600 (600)
Samsung S3 Mini
800 x 480 (480)
Asus MeMO Pad 7
1280 x 800 (800)
This doesn't work. It's pixel perfect most of the times, there are no black bars... but you might end up seeing an unplayable 200px vertical resolution on a 7" tablet.Let's have a look at an Amazon Kindle Fire 7"There's a huge 100px difference in height from the Asus to the Kindle. The Fire users would have been able to see 50% more game world than the Asus players. That's wrong. Especially since Asus has a higher screen resolution than the Amazon Fire.
Pixel Perfect, Black Bars (in use as of today)
First of all I decided to restrict the range of vertical resolution of the game. Now it's from 230px to 260px. Still a 30px difference but it's bearable.So I still ask for the device vertical resolution, of course. Then I check which number, from 230 to 260, fits best. By that I mean it either fits perfectly or has the lowest remainder.This is the initialization script. It goes inside the create event of the very first object created in the game.I also leave the view settings in the room editor as they are. Disabled. I enable them via code.
// Let's disable the drawing of the App Surface
dw = display_get_width() // Device Display Width
dh = display_get_height() // Device display height
ar = dw / dh // Aspect Ratio
min_h = 230 // Minimum Height
max_h = 260 // Maximum Height
height = min_h // We start from the minimum
fract = frac(dh / height) // This is the fractional part
mult = floor(dh / height) // This is integer multiplier
// We cycle from min_h to max_h
for (var h = min_h; h < max_h + 1; h++)
var new_fract = frac(dh / h)
var new_mult = floor(dh / h)
// If we have a lower remainder, we store
// the multiplier and the height we're testing
if new_fract < fract
fract = new_fract
height = h
mult = new_mult
// This will show you the found resolution in the debug console
show_debug_message("Found resolution: " + string(height))
// Width gets decided with a simple division
width = floor(dw / mult)
// And made divisible by 2
if width mod 2 != 0
SET THE VIEW AND THE PORT FOR ALL ROOMS
var i = true;
var rm = room_next(room);
room_set_view(rm, 0, true, 0, 0, width, height, 0, 0, width * mult, height * mult, 0, 0, -1, -1, -1)
if (rm == room_last)
i = false
rm = room_next(rm)
// Resize the application surface
surface_resize(application_surface, width, height);
// Let the GUI layer be as big as the device screen
gw = display_get_gui_width() // GUI width variable
gh = display_get_gui_height() // GUI height variable
// We'll need these to figure out the touch commands coordinates
wscale = width / (dw / mult)
hscale = height / (dh / mult)
// Let's figure out the App Surface offset (we want it centered)
Xoffset = floor((dw - (width * mult)) / 2); // Horizontal Offset
Yoffset = floor((dh - (height * mult)) / 2); // Vertical Offset
/// Go Fullscreen on desktop
if os_type == os_windows
Then we need to draw the App Surface. So in the game controller object, I have the following code in a Post Draw event.
///Draw the App Surface with correct offset
// This line prevents strange artifacts in Fuzeboy.
// The real drawing.
draw_surface_ext(application_surface, Xoffset, Yoffset, mult, mult, 0, c_white, 1);
If I run the game on the Amazon tablet, the result is this:
Fuzeboy on Devices, method 2
Game Vertical Resolution
Black bars top/bottom
Amazon Kindle Fire 7"
1024 x 600 (600)
Samsung S3 Mini
800 x 480 (480)
Asus MeMO Pad 7
1280 x 800 (800)
Now the game scales much better.
Let's fix the Touch Controls.
Those touch buttons share the obj_touch parent so I can do this in the controller Begin Step event.
// Add these in the display init script
xoffsetmult = (Xoffset / mult)
yoffsetmult = (Yoffset / mult)
// Touch Controls
for (var dev = 0; dev < 4; dev++)
touch_dev = dev
var _xpos = (device_mouse_x_to_gui(dev) / mult) + view_xview - xoffsetmult
var _ypos = (device_mouse_y_to_gui(dev) / mult) + view_yview - yoffsetmult
var this_button = instance_position(_xpos, _ypos, obj_touch);
if this_button != noone
if device_mouse_check_button(dev, mb_left)
if device_mouse_check_button_pressed(dev, mb_left)
if device_mouse_check_button_released(dev, mb_left)
As of today, I still experiment with the resolution of the game. I haven't found a perfect way to scale low res pixel graphic fullscreen with no black bars and no distortion... simply because such a way doesn't exist.Things change frequently around here, so we'll see if I'm going to stick with this method or not. Feel free to let me know your ideas on this matter.
In November 2016 I met Denis (@darftey). He’s a pixel artist. One of the best I’ve ever met, actually. We teamed up to develop Fuzeboy.
It shouldn’t come as a surprise that since then, the development of KREN has been put on hold indefinitely.
We’re pushing hard on this mobile platformer game.
There is still no official release date but we’re making progress 24/7 on every front. From music and sound to gameplay mechanics, from platform specific issues to minor graphic details.
Lots of care is being put into making this game as fun as possible. We care about details. We care about story and gameplay. We are in love with this game and we’re making sure everything goes the way we envision.
Stay tuned for more Fuzeboy news in the near future.
A well developed metroidvania game should start with a solid planning phase. One of the first things to figure out is the character movement. I’m not talking about physical variables such as speed, friction and acceleration. I’m talking about figuring out what are the movements we want the Player to be able to execute during the game.
Can the character crouch? If so, should it crouch only when standing still? Can the character crouch in mid air or does it simply aim downward? Is it possible to walk while being in the crouching position?
These are serious design considerations that should be carefully planned and addressed well in advance as they define the feeling of the game. The player will act and react based on what movements are available. It’s the absolute first response to player’s inputs.
Crouching: Metroid Zero Mission vs Axiom Verge.
In both games, you can crouch. But while in Metroid you stay in that position even if you let go of the down key/button, in Axiom Verge you get up as soon as you let go of the key/button.
Also, while in Axiom Verge you can walk while being in the crouching state, you cannot do so in Metroid Zero Mission. Yet if you press the down key again, you morph into a ball.
The mechanics are different and so is the gameplay. Plan carefully what you intend to create and plan it well in advance. If you can, plan it all out even before any test level you might be tempted to sketch.
It will greatly simplify the overall development cycle (i.e. you won’t be rewriting big chunks of core mechanics code again and again, risking to break previous works).
My primary objective would be to prototype the game with graphics.
I still don't know if this is going to be a commercial project or not. Should it become a viable commercial game there could be many options. Here are just some of them
Prototype's used to get funding. Then...
The artist remains the same, becoming the final game artist. Gets what is due to him/her, plus revenues shares.
The artist changes; prototype art won't be used; he/she will get no revenues shares but will get what is due to him/her.
Prototype's not a prototype anymore and is ready to market; no more funding necessary. Artist remains the same so revenue share model apply.
Project gets cancelled. No one gets anything (this should not happen! at all costs!) Artist is free to use his/her art however he/she sees fit.
Project is released as freeware (unlikely). Same as above.
The project is going for the commercial route. It's now a revenue share work relationship.
Right now I'm unable to test the mechanics, to think about what works and what doesn't; to imagine the game world. I need to quickly place things in the levels, test them and get an emotional response as to what works and what doesn't.
That statement is a dramatic exaggeration. But you get the idea.
As of now, everything you see in the image below, except the blocks tilesets, were drawn by me. Ideally, this should change.
Right now I'm working full-time on this project.
I will be trying to help the artist as much as I'm able to, given my limited artistic skills.
The game will have a resolution of 384 x 216.
Player will be more or less 36px tall.
The current game art won't be used as a basis (thank god!)
Beware: the game videos/images are only there to show collisions and other tech aspect. The overall feeling of the game is going to differ drastically. Think Super Metroid (there, I said it).
This won't be an action packed game. In fact, when I think about it, I think about words like
If you would like to collaborate, have comments or want to share your thoughts, leave a comment or get in touch via social networks etc.
This post is outdatedThe following (quite naive) ideas and methods have now been replaced. This post was written when I was just starting out with game development (I was learning GameMaker Studio).
Player now has data (like energy, starting_x and starting_y positions, starting direction and so on) and a nice inventory of permanent upgrades. I've called it inventory for the sake of it. It's just an array (it really is) of stuff you can get through the whole game. Permanent stuff. Stuff you can get only once per whole game.
In every room (level) there are a number of different objects (like enemies and items). Most of these items will simply respawn once the Player gets back into the same room. Again and again.
This way it doesn't matter how many times you killed the enemies in the room. As soon as you exit and re-enter the same room, all those enemies are just there. Again.
This is fine. Almost essential in some situation (believe me, there will be times when you'll need more enemies to refill your energy or ammo levels).
So what's with the level specific items? If you already acquired the high-jump ability, you won't find it again in the level. This is where the inventory comes into play. And this is what I've coded today.
By the way I'm not using maps. I'm using simple arrays. I just defined a couple of macros so I can use my global array like it's a key/value map. I get the added benefit of speed and code autocompletion in GameMaker. The only thing I made sure of, was to initialize the size of the whole array.