Going-Ons of Tadukoo

I recently talked about my new goal being the Tadukoo Bible Project , and that things should either be reconciled to the new goal or stopped. This post is about how I can reconcile things to the new goal. Regarding TAG (the game I've worked on programming and have posted about multiple times), to reconcile it, I'd simply have to give it a good moral message (or multiple). Any other games I would make would also need a good moral message or to be specifically about God. The API and Engine I've been designing don't really need reconciled, because they are tools to use to make other programs. Minecraft with Tadukoo would change in some way that I'd talk about God or His knowledge and wisdom in the videos as the main subject. Minecraft: Order of the Stone: A Retelling of the Cave Game would change so that I not only talk about the history of Minecraft, but events from those days in a Christian worldview and potentially my life in those days. Any other YouTube series wou...

 The purpose of this post is basically to say what my current status is for a bunch of plans I have and where I plan to go with those plans. This is not to be a detailed list of all the plans, just a summary of the plans. Likely posts will be made in the future detailing specific plans more. TAG With TAG, I have done the Tengdev v.0.0.7.0 update, which was to add the remaining Prologue areas that were planned for the game and setup the passages to go between them. That was completed on time on July 31st. Since then, I have simply been updating the game to newer API and Engine versions. The Player Select Menu is still planned for the end of this month, and the More Sounds/Halloween update, Certain Animations/Thanksgiving/Anniversary update, and Debug Improvements/Christmas update are still planned for their respective dates. The "Hacking" Basics update is now planned for January 31, 2017. I have plans for 14 more updates from February 28 to July 10, 2017, which I will discuss ...

 This post is to talk about my current plans for games. I'll start by going over the plan for TAG and any changes to it, then into the other games, and a little bit about the current API and Engine plans. TAG The goal with TAG for the end of June was to finish the API, Engine, and Game separation, which was Pre-Alpha v.0.0.6.0 of the game. I did separate them, but the meaning of that changed. The original idea was that the API and Engine would be completed (for now at least), which did not happen. There are about 20 changes to the API and 3 changes to the Engine that I'd like to make in order to complete them (when I say complete, I mean get them to a point I'm comfortable with for now, there will of course be more changes in the future). I will consider the API and Engine to be in Beta when I get them to that point. Since v.0.0.6.0, I've been pretty much only working on the API and Engine, and all updates to TAG were simply to update to the newer API and Engine version...

 Just as a note before we get started, I always have to type and delete "so" at the beginning of every blog. "So" is my go-to word to start a sentence after thinking about it for a bit. If you see the word "so", I probably thought about that part of the post for a while. Anyway, last post  I talked about the resolutions I made at the start of the year and the updates to them. There's just one thing I forgot. I forgot about the separation of API, Engine, and Game leading to the possibility to create more games and programs easily and that I wanted to make new games and programs in order to improve the API and Engine. That's why in the original resolution ,  I had the section to create two games using the API and Engine. In the current one, I simply said I'd like to make games, but I'm not sure when. The reason I'm bringing this up now is that I've been inspired by Minevolution  (a minecraft cookie clicker-type map), the Upgrade Compl...

 My current plan with my game (and beyond) is to get the API, Engine, and Game separation finished. That would get it to v.0.0.6.0. Also, then I would have an API and Engine upon which I can build various games. My plan at that point is to make one simpler game (like maybe some Pacman-type game or something). Then I can use that simpler game as something to show people if they ever ask what I've made. Also I can finally say I made my own game from scratch (because the API, Engine, and Game itself would be my own making). Ultimately with the API and Engine, I'd like to have them set-up so that I could make any program using them. So I could make a text editor if I wanted to, or a decoder for some code system I make up. I'd also like to eventually make a program that you can use to create programs from the engine and API. Like it gives you access to the API in order to use it correctly when developing your program, but the engine code is obfuscated at the time. Then when you ...

 When I first set out to develop an API for my game, I figured it wouldn't be that hard. I wasn't even thinking about separating the engine as well. When I realized I wanted to separate the engine, I thought I could just continue developing the API and the engine would drop out of it. But it's not that simple. See, first I started with an Object API, making a TangibleObject upon which all in-game objects are built off of. Then I made the Event API to go along with the InteractableObjects in the Object API, and I had to change things in the Game/Engine mixture so that the Events would properly happen. Then I made Location API, which further affected the Game/Engine mixture, forcing a Game API class before I was ready for one. At that point, I decided I'd make a Drawing Engine. As I made the Drawing Engine, I realized that every single API class had to be changed to fit the Drawing Engine and a new base Object API class had to be made (DrawableObject). I also had to make ...