Going-Ons of Tadukoo

 When I first started the blog, I was doing two posts a day. I thought that I would end up doing two posts a day everyday. Unfortunately, that is not going to happen. The reason I was able to do two blogs a day in the beginning was because there was a lot of information I wanted to share at that point. I should've spaced it out to at least one post a day, so that there wouldn't have been such a gap until now. Anyway, I'd sort of like to make one post a day, but I know that won't happen. So right now I'd like to make one post a week at minimum, preferably two or three per week. We'll see what happens.

 I made the base engine that I planned on doing when I last talked about developing the game. I'm currently working on Pre-Alpha v.0.0.5.22R152 DEV of the game, and I've been thinking about the future of it. The goal of v.0.0.5.22 is to get the game back to working again by making the Controls part of the Engine (/Game within the new Engine?). So far the only thing I need to do yet is to get the Player to display again and get the movement of him down in the Controls. After that, I'm going to remove the old engine stuff (Framework and such), and make sure all of it ended up in the new Engine in some way (no feature loss). From there, I'm going to separate the model and controller stuff in the API, then the Engine (if any), then the Game. After that, I'm going to improve a few classes to be better in the API. Then, I'll make it so that ultimately, everything drawn to the screen is an extension of DrawableObject and that basically all of the API extends from that ...

 As I mentioned in the New Year's Post , I plan to work on bringing Proving Creation to my YouTube channel this year. Proving Creation is a series that I had planned since February 2015. I had originally thought about it beforehand, but February 2015 was when I started forming the basic progression of the series. The plan eventually became: Prove that a god/gods must exist. (Defeat Atheism and Agnosticism) Prove that there is only one God. (Defeat polytheistic religions) Prove that God is personal. (Defeat monotheistic religions that have a non-personal god) Prove that the God of the Bible is the true God. (Defeat monotheistic religions that have a personal god, excluding Judaism, Christianity, Islam, and Mormonism) Prove that Islam is wrong (Prove their god is different from the Christian God) Prove that certain denominations have God wrong. Show other evidence that confirms the Bible. I also had a way I planned to create/prepare the content for the series, but that may be for ano...

 As I normally do at the new year, I try to make plans for where I'd like to get this year with stuff I'm working on. In this post, I'll be showing my plans for the year for programming and YouTube. Please note that all plans may be changed throughout the year (not in this post), and this only reflects the current plan as of 1/1/16. Plans that have dates closer to the end of the year will probably receive the most change of all. Programming TAG For TAG, I'd like to finish the API, Engine, and Game separation by the end of March. By the end of April, I want to get to v.0.0.7.0, which would put all the Areas from the Prologue into the game. This doesn't mean the Prologue will be complete, just that you can go to all the rooms in there (at least main storyline rooms). By the end of June, I'd like to get to v.0.0.8.0, which would see a Player Select Menu when starting a new game (so you can choose other player sprites if available and choose Markiplier mode once aga...

 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 ...