G'day everyone,
It's come to a stage where most things are implemented to facilitate creating the game's main levels. This has been held off for a while as changes to movement or mechanics would write-off these levels had they been designed previously (though previous iterations of "first" levels have been made in the past).

Beyond gameplay changes, aesthetically I wanted the first level to have a simple and readable style to get players acquainted with the mechanics first and foremost, but a visual style that's still initially attractive. For this there needed to be all of the visual components to make the level happen, so I added the necessary missing components that were needed like the pillars to go along with the glossy ceramic tiles, the background tiles that act as a sort of railing, the waterfall background, the tropical plants, and the blossoms ambient particle effect.

The level serves as the first level players will get their hands on (assuming they don't go straight for custom levels!) so it has some basic tutorial signs and scenarios, including introducing adding and subtracting a single colour.

https://www.youtube.com/watch?v=ob3RS19WLgw

With the first level, will come the next few, at which point I'll connect them together in the UI and that will mark the completion of the game's UI; main menu, settings, pause menu, editor, and level select screens.

G'day everyone!

This is the 2nd look at some of the development of Huecube, read on if you are curious about some of the thoughts that go into the additions of Huecube!

- - -

Huecube's wiring system in the editor is extremely versatile, and allows you to do just about ANYTHING you could imagine, but it's a little bit cumbersome if you're attempting to make something advanced that needs to keep track of numbers.

While levels absolutely don't have to, there are times where creators may want to track values for more advanced segments -- like making a door open after a button has been pressed a certain number of times. This could be done by using a chain of logic gates, but I felt that the convenience and power unlocked by adding a proper counting system would be well worth it.

Now in Huecube there are a dozen items that can be used in the Editor to define and manipulate named numbers, called "Counters". There's also an item that can output a signal if one or multiple conditions are met with counters.

The positive side-effect of the introduction of Counters is they can be used to receive information that otherwise wouldn't work well with the existing systems. I wanted there to be a way of tracking things in the game that normally couldn't be effectively, like for instance jumping:

Jumping can be tested for by using proximity sensors to tell when the player was off of the ground, but it wasn't fool proof because it's possible to trigger that off by other means that couldn't be detected. By adding the "Event Watcher", I can have it send out a pulse of power when the player jumps, which could be used to do trigger other things off.

The issue with this is the matter of how to translate jumps being detected into usable input, because having a single pulse of power won't work if two events occur during the same pulse. So perhaps I could make the power state of the Watcher alternate every time something is recognised? Well it's a possibility but makes it more difficult to work with as a level creator, and still doesn't solve if it happens at the same moment in time as it would toggle on and then off again, making nothing be detected.

The solution was to have the detections made by the Event Watcher be reported numerically somewhere, where it can be decided by the level creator how to deal with it. This means if you want to simply detect a jump, you could check if a number increases above 0, then set it back to 0. If you wanted a pulse to occur for every event detected, you could have a counter that decrements as a power output toggles until it is depleted. This also helps with things like Rubble, where multiple can be broken at once, as no Rubble gets missed because the counter would increase to match.

By using counters and the Event Watcher, you could make breaking Rubble in an area act as a sort of "objective", this is a video demonstrating that idea in a short level.
https://www.youtube.com/watch?v=OFEqdQC5zoY

Be sure to join the Discord[discord.gg] if you want to be more involved in the early discussions of the game, you can ask any questions you want there or provide feedback and ideas if you'd like!