Sunday Night Lazy DevBlog - 9/14

    Few things to update you on this time around. This week on the demo, I added:

• Some searchable offices for the player to ransack.
• A whole new floor with what can barely be called a puzzle.
• Lots of character. 

    In all seriousness, the new demo is coming along a little slowly because I've been having fun with level design. It's be interesting to take a three path fork and cut it up different ways to make each path feel unique, add some distinct art to an area so players can orient themselves, make things arbitrarily longer.

    I've also been trying to pull design inspiration from and old Tomb Raider game I have been playing in my spare time. Before, I was making very small rooms filled to the bring with loot and searchable things and all clustered together. It made sense to me based on how I would design the space if I were actually using it as an office (or evil lair), but I've noticed in Tomb Raider there are these long, winding paths and tunnels that lead to big, elaborate spaces with something like a single health pack. 

    It doesn't feel like a waste of time somehow as a player. After all, you get to explore and get an item at the end, but I would be incredibly aggravated to have a 20 ft hallway between my sink and where I keep the dish soap. I am trying to keep that in mind while I make the floors. Make everything bigger than it needs to be and don't forget to reward the player, even if it's a small thing like a useless health pack or a cool mosaic.

    Also, I made a stupid, little fortune teller game that you can play for free on Itch.io. I call it Tarrot, pronounced like "Carrot." Give it a whirl and get your fortune told. 

    That's all for this week. Later. 

Micro Tutorial: Mass Messaging with AoT Lists

 

 

 

    As is tradition with the Micros, let's jump right into it.

     

    This bit of script sends out the message "Trigger" to every object on the AoT List named "Trigger_List" which can all be seen on the left side of the top image. I've linked up "Trigger_List" to a For Each Loop block on the input side. So, this loop will fire once for every item on the AoT list. In this case, five times. 

    It will also cycle down the list during each loop. So, you can see I've linked the output "Item" from the For Each block to the target object on the Custom Event block. This will make sure the message is getting sent to a new item on the list every time.

 

     On the other end, I have a simple Custom Event Arguments block waiting on each target object on the AoT list to receive their orders. (If you need a refresher on Custom Events, check the micro-tutorial here)

 

    If this tutorial was helpful to you, consider throwing me something on Ko-Fi or checking out some of my games. Either way, be back later with more.