Successful Migration to Android Through Google Play

You can access the “Beta Testing” version of the project by the following link:

The game has not approached “true” beta status, but instead, it shows the reflection of safety found in Google’s protection of its customers.  Normal searching through Google Play will not find the software, because it remains un-finished.  While my description of the software on Google Play lacks much in detail, that should alter after Cycle 4 wraps up.

I must admit, I have a lot to learn when dealing with 3D graphics.  I have maintained a balance between coding the game and learning the intricacies of Blender.  The picture below shows the head I continue with in my practicing.  The source originates at Blender Market from BGShop.

Yes, the single “hair strand” looks funky!  Apparently, changing the structure of such a “bezier” shape requires a bit of setup.  I have not finalized the decision, but I might make the cartoonish hair unique to Sylveria and realistic hair representative of Saphirel.  It would serve the purpose of learning.

Finally, my most recent progress furthers with adding special effects to the ability buttons.  Since I have limited resources when concerning “screen space”, I wish to add more flair that contributes to a player’s button choices.  Also, if you desire, you can find the current selections of music by pressing the Pause button located in the lower-left of the battle screen.  This option reveals itself when playing the game, of course.

Thanks for reading, and I hope you have a good day!

Progress Toward Google Play

The Android build now comes in two separate files:  the main file that launches everything and its expansion.  I added support to the Android side for properly recognizing the expansion file, which holds collections of both animations and sounds.  Google places limits on an app’s size, but for the game, the available space remains fine.

Google provides a “Downloader Library” that intelligently downloads the larger file.  I presently need to include that library as a core part of the software.  It stands as my next goal to achieve.

I also spent some time scoring progress with Blender as well, but I honestly have quite a distance to go.  As just a test, I was able to take the items below…

… And make them into this image below.


The second image looks more realistic with the lighting, but it comes at a cost of the flat circle’s original details.  While I am not currently sure how to mediate that problem, the modifications for the change consisted of black, white, and various grays.  I thought it might look weird if I made hair glow like the sphere in the pictures.  Anyhow, these make up some of my hobby’s results.

Thank you for your spent time.

Slowly Under-going Progress with Android

I have successfully added the ability for this project to communicate with the Android operating system for handling phone calls during a battle sequence, among other things.  I will most likely need to adjust the code in parts as other features get smashed cozily into the project, like upgrading characters and roaming the insides of an explorable level.  I still need to add a Button to the “Sound Test” window, which will probably under-go a name change, for erasing the temporary “save game” that gets created after the software commits to an exit or pause.  For the moment, the battle sequence continues properly beyond just when interrupted.

In further regard to Android, I have to move a bunch of the visual resources, like explosions and music, into a separate file for downloading, so that the primary file will remain small enough for Google Play.  For this project’s size,  Google Play allows the storing of a “relatively” large amount of resources into a secondary object, which they call an APK Expansion file.  However, the main file, which focuses on the contents that fuel the core of the game’s operation, must maintain a small size limit just below 100 MB.  While LibGDX makes the process easy for adapting the APK Expansion file to the Android side of the software, I personally require learning  new things, so that this project can understand what the insides of an un-compressed ZIP file looks like, which mainly makes up the Android packages.

Anyway, I have lots of ideas, and on this particular Cycle, I desire to develop mainly visual art.  Since I have not recently exercised that muscle, I aspire to adjust a 3D model through Blender.  You can view the link I am working with HERE for learning the creation of hair in this portion of my journey.  I never before thought that “bezier curves” could serve something in a way so interesting!!!

Thanks for your time!

Transitioning to Cycle 4

Everything I can think of that I set out to do for Cycle 3 has been completed.  As part of the transition to this next Cycle, I again will need to gather what core points I would like to focus on.  While last Cycle included the addition of Android support, I still need to add the feature of pausing for when the Android operating system calls for it.  The “Pause” button in the bottom left of the game itself allows the player to manually stop the game action and allows for the experience of a few upcoming features.  However for example, if a phone calls happens, the game will effectively crash on Android.  To my knowledge, this does not pose as an issue on desktop and laptop systems.

I would finally like to focus on art somewhat.  I have some resources for transitioning 3D resources to a 2D model.  I take this path, because I am not completely fluent with human anatomy.  By keeping with a 2D environment, older devices should still maintain reasonable gaming performance.

I would like to put together a skeleton structure for adding upgrades to characters.  I originally intended on using the ‘Gleaned’ music set for this purpose.  I desire a relaxed aria for a moment of strategy.  This music set rests as available when the “Pause” button in the bottom-left corner inside the game becomes pressed.

I also want to build the beginnings of random story encounters.  Key events of the story line will remain the same, but battling “story bosses” would influence the story in different array of ways.  I may also take a similar approach with potentially hostile environments, instead playing out a bit like a board game with the advantage of real-time elements.  In a standard table-top game, each player must wait for his or her turn to participate.

Several other items need reviewing.  While the details listed above in this post will likely survive to make Cycle 4, I must also consider the possibilities of other issues.  The toughest barriers to progress this last Cycle included revising limitations in the code and the previously thriving need to focus on school.  At least for now, school no longer demands attention.  Updates to my goals for this project reside in the Airtable chart, which pulls up from the “Progress Status” button found at the top of this page.

Thanks for your attention span!

Cycle 3 – Complete

I am satisfied with the level of protection on the software for now.  Everything seems smooth so far, and I have yet to find a bug with it.  The tech support at Allatori performed very well at their duties as I requested help.

I will need to post the ready results of Cycle 3 on this site and update the Licensing page for the new songs.  I eventually need to also add the licensing details into the game itself, since the project presently stands mature enough.  While I intend on posting the MacOS version, I can not presently test it.  The Android version of the software will initially arrive on this site and remain available for a time.  My intent includes placing the game on Google Play, but the current file size limit on that service requires that I delay that action for the moment.  I need to break up the game into smaller pieces for a more gradual process of downloading, which I will likely initiate sometime in Cycle 4’s middle.

I would like to entertain more the thoughts of enhancing the art in the game.  The Saphirel and Scorpibot animations carry an age that approach the length of a decade.  It is time for some new stuff!

Thanks for reading!

Cycle 3 – Almost Done

I have finished the basics that I required for this Cycle.  I still need to run the code through Allatori to see if that properly works.  It has been a fun and long run these months, but I am ready to move this project into different directions.  I have graduated school, and I need new direction for myself as well.  Hopefully, this testing process ends soon.

Battle System Re-design and Other Progress

With Android added to the supported platforms, I quickly face the need for adding a pause feature to the game.  This comes in two flavors:  an ability for the player to pause upon a whim and the capability for the device’s operating system to safely place the software on hold.  For example, the game’s current state will cause accepting a phone call to either crash or reset the software.  I have placed effort already into the process, but I came across a limitation when testing.

As mentioned several posts ago, I introduced ScheduledThreadPoolExecutor.  It works quite well for executing tasks based on the concept of timers, but it does not allow the capacity to monitor whatever existing timers that may previously count down in its queue.  I can still access the job items though.  The system driving the progress bars seems to not express any trouble with my current attempts for pausing.  I would like to mimic the success of the progress bars with the battle system.

I desire to take advantage of the moment and expand the battle system.  As of this posting, it only supports Scorpibot and Saphirel.  I would like to add the capability of handling more than two characters, plus I aim to throw in a dash of randomness towards the notion of who initiates attacking first.  Basically, that comprises the essential idea of “auto-battle”.  I want to roughly personify each character as an object in a list of characters that each possess a timer statistic for tracking “initiative”.  As far as auto-battle goes now, Scorpibot and Saphirel just exchange blows every four seconds.  In other words, I prefer to swap the handling of timers by the ScheduledThreadPoolExecutor to a List of character objects instead.

The game’s download size will increase somewhere under a measure of 100 Megabytes when I eventually post its next version, because I added new music.  This prepares for the slow integration of Sylveria into the software.  Also, the game now randomly chooses from one of three random backgrounds to present for the sequence of battle.  As another added feature, Saphirel’s own health bar keeps track of his survivability.  I put in place a way to check a single opponent’s health, but I intend on later mixing it with an individual test ability of Saphirel to help promote its usage.  I will wrap up Cycle 3 when I obtain successful test results with Allatori as the last step.

Thanks for reading!

Android Conversion Complete and Compatibility Issues with Apple

It took a while, but I finally managed to migrate the project’s code base to also work with Android.  It took some effort to fit the action into smaller screen “real estate”, and the font size still needs some serious attention.  I also obtained a developer’s account with the Google Play Store, so eventually, the Android version will become available on Android phones and tablets.

It might be at least a few months before I can address iOS.  On top of that, the chief leaders of LibGDX, the game frame-work I use for this project, do not currently pursue keeping compatibility with Apple’s new approach to gaming.  In this article, you can read how Apple decided to drop OpenGL in favor of its proprietary solution:  Metal.  Apple never put much effort into keeping it a secret, sort of like how the business refused to invest much into OpenGL.  Apple tends to treasure the proprietary stuff that it owns in much higher regard, and while Metal has the capacity to create both a better and more efficient gaming environment, it sort of isolates Apple systems even further.  Either way, Apple proves repeatedly that it knows how to arouse profit in that specific type of arena.

On the good side, I think I found an open source solution for maintaining compatibility between Android and iOS / MacOS.  I applied this effort for the purpose of building non-gaming software in a professional way.  The Multi-OS Engine, a project of Intel, keeps a valid avenue available by using “native code” instead of keeping a reliance on OpenGL.  While Gluon and Codename One still appear to need OpenGL for Apple stuff, I expect those businesses will adjust as necessary.  I will need to acquire a different Mac for future testing, since a currently supported MacOS stays essential for building iOS software.  I will likely attempt to integrate the Multi-OS Engine with LibGDX in my game project for the future, just for learning’s sake.  While OpenGL remains on MacOS for now, “deprecation” inherently means that it will no longer receive updates.  That includes no longer receiving patches that will help it function should it accidentally stop working.

Cycle 3 – A Few Updates

I decided to review some Kanban stuff, which is meant for keeping things organized for projects.  The idea involves keeping notes under three different categories:  “To Do”, “In Progress”, and “Done”.  I wanted something with a nice web presentation.  Many of the sites I experimented with did not offer this option, though some did have good layouts.  After reviewing 30 or so web sites, I narrowed the choices to and  When I tried a basic layout with Trello on my mobile phone, a rather “large” menu covered most of the screen.  With Airtable on mobile, it instead just groups everything into one large column of different colors.  I have chosen Airtable for now, just because it remains a bit more readable.  You can now find this project’s current progress by clicking the “Progress Status” button in the top menu.

I have migrated the project from the Eclipse IDE to IntelliJ IDEA Ultimate.  I tried reasonably to run the project with both Eclipse and Android Studio.  With Gradle, it could work with just Android Studio alone, and I am aware that developers exist who correctly pull off the technique.  Android Studio poses as a unique form of IntelliJ, tweaked by Google.  Either way, I had to give up on Eclipse, and I do not desire to focus on Gradle for Android Studio’s sake.

In some other news, the Android side of the project now works!  The entire project kept hanging on the database part.  I use SQLite in this case.  Android runs well with Java, but the SQLite part of it functions very differently from the Desktop / Laptop side of things.  To get it working, I utilized a recently updated version of SQLDroid to spoof Android into thinking that it could work like Desktop / Laptop.  The secret lays hidden in SQLDroid’s code and not any of my workings, plus it consists of open source stuff if that “floats your boat” in some way.  I still need to fix a bit of code in my project to make the Desktop / Laptop side work again, but it fortunately should not require much.  Lastly, I will need to re-size the animations.  I think it brings in the need for LibGDX Viewports.  I believe that my animation software, Spine, naturally prevents re-sizing in Android, so the characters appear considerably smaller among the other items.

Thanks for your time!


Great!  Now I need to figure out how to fill my time.

I am experimenting with to help organize the mess that can make up a video game.  One major item I desire to test includes converting the project’s current source code to be compatible with Android.  I would need to create a fresh template with the ” gdx-setup.jar ” file from LibGDX.  This project did not originally use that template for the sake of personally comprehending the code better.  I originally tweaked the Super Spineboy example from Esoteric Software as this project’s starting point, pulling animation resources from this project’s really old Lua version.

I am considering the process of taking a 3D character inside Blender, converting it into a 2D model along with its skeleton info, and then animating the results with Spine.   I have experimented with a 3D model,  and the Python script for capturing the layout of the bones works with the Rigify add-on of Blender.  However, I lean towards using BlenRig instead of Rigify for the work flow, because it possibly allows a better layout for the model’s skeleton.  The Python script I found might not function with BlenRig, so I will need to test it.  The whole purpose involves the possibility of mixing 2D with 3D for battle scenarios.  I have the models I want, but I am focusing on the male version for the present time.