Fragmented Post

I'll be posting on a few different subjects in this post, so scroll to the bolded area that interests you.


Game Optimizing Tip: Conga Loading

Adding and removing objects from a game can cause a bit of lag. This is evident when dealing with numerous objects that need to be loaded/unloaded. This is why I usually just move existing objects around, like raindrops or particle effects. The bigger problem comes from objects that have to be swapped out, like NPCs or monsters. You don't want enemies milling about hundreds of units away from the player, and capping the spawn rate makes this worse. Still, removing all those unrendered  monsters and adding fresh could cause a dip in frame rate. Why not deal with them singularly?

The idea is to connect signals between the monster and a router node. The router node can be anything, but it needs a script to handle signals and connecting them. Signal connection via script is a bit tricky, so I won't go over it here, but it is a great skill to learn.

When the monster/NPC need to be unloaded, or a node needs to load an entity, it first polls the router with a signal containing itself and a request for the action. The router then adds this node to a list of either incoming, or outgoing. While running, the router swaps between out or in (boolean value) every tenth or twentieth of a second. If there are nodes queried,  then a signal is sent allowing the node to either add something, or remove itself. This allows for a single-in single-out entity loading system, reducing load.

To do something every second, or second-fragment, use a delta timer. This is just a variable that has the delta, or frame time, added to it. Once it reaches a specific amount or greater, an if statement allows some code to be run and the timer variable is reset to 0.

Who Duolingo: Tips for Duolingo

I use the Duolingo app to learn Spanish. While it won't make you a pro, it will give you the skills to converse a bit in another language. Here are several tips and things I've noticed.

Start with small daily goals until you get used to the app. Daily goals can be changed in the app settings, usually a gear or those three dots. I started small and worked my way up to the highest amount.

Double mint lingots.With a few exceptions, you get lingots when you meet daily goals or complete a level. You can sometimes watch an ad to double those lingots. When on wi-fi, go ahead and double the lingots. On data I don't watch the ad unless I am doubling two or more lingots. Lingots are useful for doing tests, getting a few extras, and getting more lingots. If you have plus, lingots lose some of their value. I think you can also give lingots to others by upvoting their comments on a lesson (the speech bubble when you complete a lesson).

Gotta do my stories. Sometime around the second section, I unlocked the stories.These are short stories that are easy and short. They tend to give over twenty XP for each one and usually take a few minutes. Since you can re-do the stories, this is the bet way to get plenty of XP. However, reaching the daily goal this way will NOT earn any lingots. Using it to get close, then doing a lesson or practice for the remainder, will give you lingots. XP boost does not work with stories.

Double XP may not be free. Occasionally, the shop will allow you to get double the XP from your lessons, but it is a bit complicated. Reaching your daily goal under this juice won't net you any lingots. reaching another level will get you lingots. Using the XP boost doesn't work on stories. I'd avoid using the XP boost until you have reached the daily goal, to maximize points and lingots.

Testing 1-2 testing 1-2. When you start a lesson, or course, there is a light-bulb and a key. The light-bulb opens a primer on the lesson, giving you tips. The key allows you to take a test and level-up the course. For just five lingots (or zero with plus) you can level up your skills. This is useful if you are good at a course and are getting bored, but sometimes it is better to do the entire course instead. A successful test nets twenty points, failure nets a disappointed Duo. If you fail, either finish the course normally, or try again later (like a day or more).

The hard easy is an easy hard. You may notice that some lessons are harder than others. Tests are no exception, so it is better to take a test after a hard lesson. This gives a greater chance that the test will be a bit easier. There is no guarantee, but it can help.

Slow and steady wins the test. Slowing the dialog on lessons that have dialog may be annoying, but don't take chances during a test. You may think you have the listening skills down cold, but some vocalists are better than others and I've let my pride fail me a few times. Personally, I'd take every hint that Duo gives, especially when I'm a little unsure. Since tests don't have many hints, I'd slow the dialog for a slight edge.

You know nothing, and the birb knows it. Each section has several courses. At the end of a section, there is a test. In my foolishness, I assumed I knew some Spanish. From ZERO to TEN I chose one and was promptly put in my place for my pride. Starting at zero, especially for the first section test, is advisable.

Report it. Duolingo isn't perfect. Sometimes it gives you wrong hints or an answer you give should be accepted. At the end of a lesson, you can ether see user's comments (text baloon) or report a problem (flag). If there is a problem, flag it and explain it. Together we can make Duolingo better. Try to be respectful, unlike me; I tend to have a temper.

Green and red. Correct answers get a green popup while wrong answers get a red popup. Those popups can obscure your answer, hindering learning. Touch a blank area of the popup to slide it down. Now you can check how wrong you were and learn from it.

Play for me, Little One

I had a plan to finish Little One by the end of 2019. That didn't pan out like I had hoped. Most of the items left to add are minor and I could add two or three per day. Since there is another project I wish to get started upon, I'll probably default to adding an item to Little One each day and focus on my next project. For now I'm just trying to make sure Little One is in a beatable form before the next update. The ending will be sparse, and I'll add both it and the opening later, but it should be completable.

My plan is to rest for New Years (eve, day, and day after). I'll try to upload a build on the last day of 2019, but I have to pick up some medicine that day and this post won't be tweeted until that day or after. On the days I'm resting, I'll flesh out the plans for my next project. The ending scenarios are planned, so I'll work back from those. Mostly, I'll be listing the mechanics and writing pseudo-code for them.

The openings and endings of my project may be done with vector art. It seems easier to make several panel images and flip through them like a book. Text will probably accommodate the images. Since I'm doing this alone, and some days are better than others, I'll take the route of least resistance.

Aside from the story images, there are a few things to add before Little One is feature-complete. The critters need animations and additional coding. Beasts need to be planned, modeled, ect. Several parts will need models and textures before being added. Part droppers need to be coded and added. Player damage, sleeping, and recovery needs to be coded. Several props and a couple dialog elements are still missing. I'm going to try getting the vacucell to suck up other liquids, and the critters will bring several items to the game. Many of the building upgrades are unfinished as well, and need models, textures, and programming.


Better as of late than never.


 Yesterday (12-29-19) I felt like I was moving through molasses. I managed to get the material droppers done and in the game. These drop a few materials daily to assist with building and part creation. After a nap I felt much better, but I usually relax after I take my meds at six.

I've added quite a few things to Little One. Mostly the parts and upgrades crafting. The upgrades seemed to work well without any extra coding in other areas. Sometimes I'll go to add something just to learn it's either there already, or I've done the preliminary work; making a feature easier to add. Keeping future and related features in mind as you program will help you add the needed functions and code to support future additions. Planning can help immensely as well, and I should have planned Little One a bit more.

Everything is burnt.

The wired mouse I normally take with me is failing. It could only be used on flat surfaces, but now it keeps disconnecting. I'm currently using a wireless mouse, but its middle button doesn't really click with me. There is another wired mouse at home, but I don't want it to fail. Either I'll have to acquire a new mouse, or deal with the wireless one when I'm in town.

I haven't been doing much on Little One these past two days, mostly my fault. Pushing myself too hard in any endeavor causes chest pains and burns me out. A health-protecting system my subconscious uses to prevent this pain is just to use burnout and depression against me. Sure, the pain isn't good, but I want to finish Little One this month.

The NPC accessories, animations, and textures are mostly done. Importing and assembling won't take long, but the dialog should still be written. Saturday I'll rest a bit, but I'm just going to ignore my body's protests and slowly pick up speed. The real problem is getting started, once I get momentum, I'm near-unstoppable.When my coding reaches 88 lines per hour, you're going to see some serious bugs.

I'll probably do a ton of planning on my two-month project this weekend. I'll have to get the planning done on that by month's end as well. Normally that would add more work and stress, but zero-sort is another stress reduction method.

Zero-sort operates on high-low impact balancing. If something causes higher stress than benefits, ignore it or break it down. Low-impact (result) options can also be chucked. When the value isn't worth the effort, postpone or chuck the idea. Bundle many smaller tasks into a relaxing time of fixing things. This is the low-stress low-value tasks that seem too small until enough pile up; it's like dusting off crumbs.Blog posts are low-stress but can have a nice impact. Rushing a few features to get a timely release is high-stress. If you have been regular with your updates, skipping one isn't a big deal.

This method is useful in decisions or cleaning/sorting items. Mainly, make any indecision into a specific answer, like yes or no. If I'm undecided, I almost always choose NO. When cleaning/sorting keep the things you want and get rid of the rest. If you just get rid of the things you don't want, you'll have a lot of maybe items that take up space. If it's clearly useful, keep it. If someone else can use it, pass it on.

I may be my own worst enemy, but I'm one of the few people I can fully depend upon, even if I cant always understand myself.

AE :: My cat does not eat dead trees

While I have implemented the battle system within the game, it is still very simple. There is only one kopii (Fluppii) and one attack and the player cannot battle yet; but the player controls are there. I have been doing minor cleanup an reorganization within Adventures' Edge to make it easier to edit later on. I still have a lot to do, and here is the todo list.

* Allow player control of kopii
* modify death and return states of kopii
* modify trained kopii AI and make them tougher
* allow NPCs and player to update their looks
* make player preview in menu
* create save menu
* create NPC AI
* create "in battle" state for NPC and player
* create build system
* create obstacle types
* modify item menu
* create player stat menu
* create kopii party menu
* create kopii swap menu
* modify catalyst script
* create growing system
* edit sun and moon
* edit level loading system
* create remaining buildings
* create attacks and effects
* create kopii
* create remaining maps
* create minigames
* create shopping and vending systems
* create velocity script
+ handle daily worl modifications
+ handle NPC death
+ handle ***** *****
+ handle *****
+ handle NPC movement

I am probably forgetting some things, but that is a rough estimate.