Skip to main content

DevBlog #17 - Game

     These past couple of days have been exceptionally rough. I accidently destroyed my temporary file backup system for the game, and pushed the bad code to GitHub. I then spent 20 hours trying to get everything back. Olex and I where up until 1 in the morning trying to fix everything. Then we shut it down, picked it back up at 6 and continued work. We finally got everything working again, but it was a grind. I then had to redo all of the work and progress that I had made in the past week and a half. In the end though we got it back, and I learned a lot about source control.

    I also made a bunch of progress on the card effect manager script, and realized something about scriptable objects.

    Firstly, the card effect manager. I created a system that would allow us to in the editor customize the exact impact and effect the card would have on the player, and on the board. Then I created a system that would track how long the cards where active, then remove them once they had completed their effect duration.

    Lastly, I also realized a really big plus, and a really big negative about scriptable objects. They can not used the way that I was originally planning on using them. In order for me to use them the way that I wanted to I had to duplicate the scriptable object, then I had to manipulate that duplicate. This would allow me to have the system that I wanted. Since if I adjusted or manipulated the data of the scriptable object, it would remain forever changed and set to that value. This means I create the data in the editor on the scriptable object, then I duplicate and adjust the data if need be.

    Although, just duplicating it was not the only change. In order for the system to work, I needed to rewrite 3 of the other back end systems to accommodate these changes. Furthermore, I rewrote the tech tree to duplicate and adjust the techs, so as not to alter any of the original data. This then changed the way that I was checking required techs and if they where researched. I needed up adding the names of the techs that where researched to a list, then checking to see if the required techs button's tech scriptable object element's name was inside of the list. Sorry for that really ugly statement, I tried :).

    I also fixed some bugs relating to the tech tree spin system, and fixed the closing and opening of the tech tree. I rewrote how terrain objects where deleted and separated them by frames to make the checks function properly. This reduced the terrain anomalies, but did not solve it so I am going to have to go back and check to see where exactly I went wrong.

    In the end, a lot of progress and setbacks, but that is what programming is all about. Bye and see you later!

Labels:

Comments

Post a Comment

Popular posts from this blog

DevBlog #4 - Fintech Platform

Progress Update (Life): 1) Just a quick update, nailed my forensics test (Monday) with a 93%. 2) Nailed my Calc exam (Applications of Derivatives: 92%, Function Analysis: 82%) 3) I have my AP Macroeconomics tomorrow with AP Psych right after that. 4) Next week I have finals for AP Mirco, AP Calc, AP Psych, AP Computer Science A, Forensics, and Langauge Arts. 5) What this means is that progress updates are going to be taking place at irregular intervals until everything settles, so sorry in advance. Progress Updates (Fintech Platform): 1) I have the connection to MongoDB established and have data being added to the DB from the signup forms. Data is taken from the forms, encrypted, and then sent to the database for storage. At the moment only the password is encrypted but I might change that. This means that I can begin moving to the next thing. At least once I fix a small little bug. Currently, it goes to a test DB and not the DB for this current project. I am going to have to figure ou...
Post a Comment
Read more

DevBlog #23 - Game

      Today, a lot of cool things happened that have a drastic effect on the game and its systems. You can now add several effects to a single card. Each effect has their own duration, amount, type, requirements, etc. All one incredible system. This required me to rewrite a bunch of the cardEffectController script but was worth it. I now also have cities seeing and recognizing their effects and the buildings effects on them too. In addition to this, I also added the population growth system and the population feeding system. This allows the cities to grow and prosper.     I have added some more cards, and have been adding in all of the effects that the cards have on the world.      Pretty neat stuff.      I am going away to camp for 3 weeks so I don't know if I will be able to post or even work on it, but I will do my best to keep you updated on the game and on any changes as they come.     Thank you so much, bye...
Post a Comment
Read more

DevBlog #19 - Game

      Today, I made a huge amount of visual progress. However this visual progress was easy to implement, so very little back end progress, as I had built it in a way to easily implement this new feature.     I have made building possible. I have also made all of the buildings and their effects happen in the game. It is response, and works very well in the MVP demo. However, I am going to change how it looks from a system where you drop the card and then your done, to a system pops up and allows you to build it. This system will show you a green, transparent, ghost game object for you to place, then once it has been placed it will turn int the real thing. You will also be able to drag and drop from the UI bar at the bottom the buildings that you an construct from the card you have chosen. This will look really intuitive and pretty, but will be simple and easy to implement.     This is a pretty big day as now I can actually do things on the...
Post a Comment
Read more