Engine Driven Mechanics.

Tried adding critters to Little One. The critters were supposed to use rigid bodies and get sucked up by the vacuum. Unfortunately, rigid bodies are hard to control. Most functions that move them ignore rotations, and the ones that allow rotations ignore collisions. So the critters; like the enemies, NPCs, and player; will use kinematic bodies. You'll gather eggs and incubate them to hatch the critters. Then the critters will produce resources and ammo for the player.

Why not just use kinematics for everything?

Kinematics need their physics programmed and tend to act like static objects when not moving. Their scripts would also have to run constantly, while rigid objects could be controlled by the vacuum when collected/shot. Having hundreds of scripts running all the time isn't such a big deal, but I'd have to re-do the mechanics already present. So I've chosen to just alter how the characters are used instead.

Can't have lag from adding objects if you don't add objects.

There are many sources of lag in games. Most notable is skeletal animations. Loops, print statements, and loops with print statements can also add up. One thing most new developers don't notice, is that adding and removing objects can get heavy for lots of objects. Sometimes you have to add objects, like critters and bombs.

Of course, some objects warrant particle effects or sound effects when they hit. Objects, like bombs, don't usually stick around to play audio or particles.Removing objects early can truncate these effects, and programming a wait timer is something I'm too lazy to do.

You could always add the effect or sound objects and remove them after, but let's keep them in the scene. Better yet, add about 5-10 of these setups to the scene; inactive. Make a global variable in a pre-load script to keep track of which FX setup you are going to use. Before the attack/grenade/ammo is removed, move the current FX setup to the current object and activate it. Leave it there and update the current FX variable for the next FX setup.

By the time you loop through the setups, the first one should be done and inactive. Keep moving and using the setups as needed. Shuffling objects or setups can help for anything and reduces load since you don't keep adding these objects. You could even shuffle raindrops around the player for the illusion of rain if particle effects are unavailable or unusable for rain (some don't handle collisions and rain could clip indoors).

This option works for any kind of visual effect, from gunshots to bullet holes. Keep several in the scene and move them around / make them visible/active as needed.

This Post Sucks.

I was going to enter Adventures' EDGE into the fragment jam, but it does not qualify. None of my unreleased projects could be made ready in two weeks; except one. Using simple vacuum mechanics and a first-person view, this project could see a simple demo quickly. After, there will be enough of a mechanics base to quickly flesh a small game. There is a private collection on open game art just for this project.

The idea was to take some simple mechanics and a few things from AE and prototype a game. Then I'd use the curated collection from OGA to quickly pull together maps and content. After release, I'd upload any assets I'd made to OGA and make the collection public. There is a problem though, two actually.

My project qualifies for an unofficial OGA jam and stress causes chest pain. Add a busy week to that and I'm not sure how much I can get done. Yes, I want to see how much stress is debilitating, no I haven't got the resources for medical help. I'll shamelessly plug my Patreon page here, in case anyone wants to support my endeavors.

This year's plans include:
Completing Both games
Getting health insurance
Attaining some kind of income
Removing the useless things in my life
Or removing the life from the useless things

Actually, the vacuum mechanics are done and I'll be working on storage, water, and plant growth.

Map Hatter

The majority of the maps have been made for Adventures' EDGE. Since the player is in every map, I had to position them at the correct entrance. Therefore, I grouped the exits in pairs. Both exits to and from a map share the same group and have a node that I place the player at on map load.

First I gave each exit a letter in an exported variable, then I grouped them based on that letter (Groupa, ect.) and renamed the variable to the group. As you go through the exit, it will set the current map and exit to the values in the exported varables.

Export variables show up in a nodes properties, so you can edit them as needed without making several scripts or massive if statements. I'm only going to save the map exit/entrance data instead of the players position. That map will load on start and I'll avoid players getting stuck in walls if I have to modify the maps.

These will be implemented in the indev 1.00 version as they are ready for the build.

Future plans include
NPC generation and loading
more NPC features
Completion of current lazuna families
New lazuna families
A basic story intro (very basic)

Boot up the door locks

I'm focusing more on Adventures' EDGE. Mostly I'm testing how much stress causes my chest to hurt. Not the greatest plan, but it's for science. The doors are now working well, and will be found in buildings on the next update. The map enter/exit system is mostly done and the player is placed at the proper entrance (mostly). Now I just need to finish putting the towns together and set all the exit destinations. Then I'll work on making specific doors lock at night. Mostly I'll group them and exclude the player from being noticed by the door during those times. If the player gets trapped, I'll have the floor warp them somewhere (map entrance, I'm being lazy). Don't expect door locks on the next update.

Most of the maps are done, but some town data must be programmed and generated. Then I'll start working on the story some. I'll have to make more Lazuna and modify the skills. Sounds must be created and added. The title screen might get some changes, not sure what. Plenty to do.

Sounds Raw

There are many ways to create sound effects. Recording different sounds and actions, vocalizations, Digital Audio Workstations (DAWs), sfx generators (Bfxr, LabChirp), and sound editing. One option most people are unaware of in importing files as raw data. This is easiest is Audacity.

Once you have installed and opened Audacity, choose 'File > Import > Raw Data' and choose a file on your computer.

There are some things to keep in mind.
Any file can be used, even video and audio files.
Avoid opening files larger than ten megabytes.
Files around five megabytes seem to have the best results.
On average, one megabyte of data equates to about 4-10 seconds of audio.

You'll usually see something like the image below.

This is mostly noise. You'll have to remove the noise to find any potential audio gems. Select a small sample of the noise with the selection tool. The selection tool looks like a giant "I" under the Analyze menu. Now chose with 'Effect > Noise Reduction'. A new  window will open.

Click 'Get Noise Profile' then reopen the noise reduction window. Copy the settings, or choose your own, then click OK.Next use 'Effect > Repeat Noise Reduction' or use Ctrl + R. You'll want to reduce the noise 2-3 times for best results. The noise reduction takes an average of one second for every ten seconds of audio.

The first file I used yielded no results, so I tried a second file.

Installation files and jar files seem to give the most sounds. You'll usually get chirps, horns, beeps, squeaks, rumbles, and heartbeats from this. 'File > Export' the audio as Wav format to work on later. Now you can split and modify the separate sounds to something you find useful.

Your results and mileage may vary.

The walls are closing in

I finished modeling the buildings last week, but I've been busy with other things recently. The meshes have been imported int Adventures' EDGE and I'll be assembling the parts into the final scenes. Afterward I'll assemble the maps and code in the NPC loader and start wrapping things up.

It is slightly discouraging to work so long without any support. Maybe I'll look over my page and see if I can boost traffic to it. Perhaps I'll ask individuals for support. Just need something big enough to turn heads.

After building the maps, I'll have to code NPC loading. Then I'll start working on a basic save/load system. I'll fix some minor problems and modify the AI and battle systems a bit. Once those are done, I'll be adding more lazunas and making the skills look unique.

I've made a random word generator to help generate creature names. You past a list of words in and it uses two methods to generate a list of words. There are a few minor things I need to add before it is finished (bigger font, instructions, graphics) and I'll want to make sure it doesn't crash from someone adding too many words. It will be on my itch account once done. Check later today (5-23-2019) or next week, I have a few errands to run.