The goal of creating an engine is simple. I have said this many times before and I will continue to say it. The reason that it seems like not much right now, is because I am slowly coding it to perfection, laying down the perfect framework for adding more things easily first and then adding in all the features like jumping and guns and armor and medieval knights. This is going to be a long project and it is going to appear as if it is not always making progress, but I am working hard. To make this video, I did not want to have an empty level with a small missing texture placeholder dot as a character, so I took the levels and assets from Cataclysm, my original project, and plopped them into a copy of the engine so I could demonstrate the features. Things like doors, jumping, and the gun do not work because those things have been removed in the engine, so that they could be recoded to work better and interact with the so called planar system, which will allow the player to be at different elevations in the level. These features and many more are coming soon I assure you. In the mean time, check out this video.
My Co-Developer, who I think is going to be, "Mechanics Programmer," in the credits, "LeanHydra", has just joined me on this project. We will use GitHub. My repository will be purely the engine.
I will constantly make updates to this GitHub repository, updates that have to do with engine features, not music, levels, or assets. However, "LeanHydra" has a forked version of this repository on his account.
This repository will contain everything that is in my repository, but it will also contain the actual game, the levels, the music, the assets, the whole playable thing. When I make a strictly engine change to my repository, I will send him a pull request on GitHub and he can merge those changes into his code. When he makes a change to the code, he can send me a pull request, and I can selectively merge the code only into, not the assets and stuff, back into my repository, so the code in our repositories are always up to date with each other, but my repository stays pure of assets and levels. Also, we have a Trello board.
The way this works is one of us sees something in the To Do column that we think we could do, and we drag it into our Doing column, make the changes to our repository, send a pull request to the other person, and once it's al done and merged, move that card into the Done column. This is better than the GitHub projects tab.
And I will not be using that tab any more.
Comments
Post a Comment