Game
A Day In The Life


6 years ago

Sometimes with random generation you'll get some nice results. Others you end up with weeds all over the place and no easy way to get rid of them. Just another annoying bug that's been fixed.


1


0 comments

Loading...

Next up

I know updates have been slow but there really isn't much to talk about when you're just tidying up existing code. We're looking at updating the art style to be just that bit nicer. The crop system working with an overhaul to interactions with tools.

Wall height is being adjusted to accommodate things such as stages and lighting while also giving animatronics more breathing space.

Finally, I've had some time to do some more work on the recode. There is hardly anything to see except for this utilitarian clock which can be swapped to 12 and 24 hours in settings. The lighting again changes through the day too.

I'm currently working on a new game with a team of people. Here's a mannequin being assaulted for test purposes. Gotta do what you gotta do for your damage systems.

Buttons ver 2- jumpscare Test

Asking the big questions today. We won't support changing your characters outfit or gender but you can give our beloved testguy a name. Character customization will come later, as it will take planning to get it as versatile as we want at the moment.

Lightweight object recoloring test. This test is looking at coloring defined areas with as little excess data as possible and uses NO mask maps, alternate materials and does not break object batching (won't melt the PC when you have hundreds of swatches!)

Finally, you can sell the fruits/veg of your labour. :)

Quick update on the project, Dialogue system has been rewritten from the old version of the game, functionally the same but a lot easier to use. The camera has been worked on and the inventory is being expanded with things like drag and drop.

Light menu is still undergoing it's refit, some behind the scenes code changes making it easier to edit multiple lights. A light will also toggle on/off depending on its intensity. So custom events don't need to be loaded with two different commands.