In the May post, I mentioned I should talk about the 'plugin-based gameplay' thing I was doing. I'll talk about that now.
Mega-Risk is not meant to be a static game. It's intended to have as much community-created content as possible. Why? So that there can be as many maps, game modes, and various customizations as possible.
I described the settings system in April. The main purpose behind that was to allow players to tweak every facet of Mega-Risk possible to make every game a little different.
Along with this, I'm trying to make it easy for people to add their own custom content. I've already started to plan a content-creator/map editor when(or if) the base game gets 'completed'.
I was having a hard time trying to figure out how to make stuff made in this map creator into Mega-Risk when I found out Unreal has a built-in mod system (Plugins).
I have since decided to use this in the development of Mega-Risk. Everything outside of the base functionality (territories, multiplayer handling, etc.) will be built as a plugin. This includes any base maps or other assets that would be included in the main game. By doing this, players will be able to completely replace the main Mega-Risk stuff with their own.
That's basically all there is to say on that.
Friday, July 29, 2016
Well, there goes summer
I believed this summer would be all about putting Mega-Risk together and getting everything done 80s montage-style.
I was wrong. I was so very wrong.
For those of you who do not know me personally, I will be moving to Seattle this August to attend the Academy of Interactive Entertainment for the next two years before (hopefully) being trebuchet-ed into the hectic world of Video Game programming where I'll be paid to transmute caffeine into code.
The key word in that statement is moving.
I have never moved before in my life and my parents have not done so in about twenty years. Furthermore, none of us had any experience finding a home in a major market like Seattle. We had no idea how much that, as well as all the other things having to do with starting college, would dominate our lives.
So, in between apartment hunting and filing out paperwork and scheduling meetings with school people, I have not had 24/7 to develop Mega-Risk as I had hoped. Also, to be honest, some days I have spent some of my free time away from the project for good and bad reasons, taking in my last true gulps of free summer before the eternal cycle of adulthood becomes my life.
Anyway, enough about me and my excuses, let's talk about MEGA-RISK.
For the most part, I've been making that 'glue' that I talked about last post, connecting some of my disconnected code bits and adding some more multiplayer implementation.
I've also been reading about a lot of concepts I'm not too familiar with. Specifically, I've been looking into file manipulation (having the game do stuff with other files, for config purposes mainly), the built-in save game system, plugins(mods), and a lot of stuff on how to make a multiplayer game run without imploding or breaking immediately(this is the hard one).
Also, for the last month, I have taken a kind-of break from the main Mega-Risk project. Another IRL Mega-Risk thing is happening over here and The Creator is trying out a Westeros-themed board and ruleset with a ton of RPG-like mechanics.
After realizing how hard it was going to be to keep track of everything, I decided to make a Mega-Risk companion app of sorts that holds tracks stuff like how many territories/continents people own, current diplomatic statuses between players, and (now) all the Westeros-RPG stuff.
I also want to have it do some of the more tedious things like calculating reinforcements or letting us know when to play a special event card.
I've used this as an excuse to try out some of the more abstract features I want in Mega-Risk like save games and diplomacy and config files.
So I haven't strictly taken a break from Mega-Risk, but I have paused work on the main project itself. I don't want to make an promises about when I expect to be able to add a bunch of new stuff, especially with game school just around the corner, but I do hope to get back to the main game soon.
I was wrong. I was so very wrong.
For those of you who do not know me personally, I will be moving to Seattle this August to attend the Academy of Interactive Entertainment for the next two years before (hopefully) being trebuchet-ed into the hectic world of Video Game programming where I'll be paid to transmute caffeine into code.
The key word in that statement is moving.
I have never moved before in my life and my parents have not done so in about twenty years. Furthermore, none of us had any experience finding a home in a major market like Seattle. We had no idea how much that, as well as all the other things having to do with starting college, would dominate our lives.
So, in between apartment hunting and filing out paperwork and scheduling meetings with school people, I have not had 24/7 to develop Mega-Risk as I had hoped. Also, to be honest, some days I have spent some of my free time away from the project for good and bad reasons, taking in my last true gulps of free summer before the eternal cycle of adulthood becomes my life.
Anyway, enough about me and my excuses, let's talk about MEGA-RISK.
For the most part, I've been making that 'glue' that I talked about last post, connecting some of my disconnected code bits and adding some more multiplayer implementation.
I've also been reading about a lot of concepts I'm not too familiar with. Specifically, I've been looking into file manipulation (having the game do stuff with other files, for config purposes mainly), the built-in save game system, plugins(mods), and a lot of stuff on how to make a multiplayer game run without imploding or breaking immediately(this is the hard one).
Also, for the last month, I have taken a kind-of break from the main Mega-Risk project. Another IRL Mega-Risk thing is happening over here and The Creator is trying out a Westeros-themed board and ruleset with a ton of RPG-like mechanics.
After realizing how hard it was going to be to keep track of everything, I decided to make a Mega-Risk companion app of sorts that holds tracks stuff like how many territories/continents people own, current diplomatic statuses between players, and (now) all the Westeros-RPG stuff.
I also want to have it do some of the more tedious things like calculating reinforcements or letting us know when to play a special event card.
I've used this as an excuse to try out some of the more abstract features I want in Mega-Risk like save games and diplomacy and config files.
So I haven't strictly taken a break from Mega-Risk, but I have paused work on the main project itself. I don't want to make an promises about when I expect to be able to add a bunch of new stuff, especially with game school just around the corner, but I do hope to get back to the main game soon.
Thursday, May 19, 2016
CONRAD STARTS HIS BLOGGLES
SO, CONRAD HERE, let me fill you in on what I've recently been doing.
1. TERRITORIES. basically I've been fiddling around with C++ trying to create voxel terrain out of an image. in short, VERY COMPLICATED. Annoyingly, I could not wizard my way into making this work. however just yesterday(?) (the 18th of may) I figured out a way to do this with my specialty. materials. WHOOO and it works. I can generate a terrain out of any (heightmap) image! so I currently have the regular mega risk map, Mata Nui from Bionicle, and some Skyrim map that Shmid sent me. but the skyrim map just died for unknown reasons so I have to redo that :/ but that will take approximately 5 seconds to fix so you can assume that works.
well that's the main thing. me blogs if there is anything new and wizardy happening.
1. TERRITORIES. basically I've been fiddling around with C++ trying to create voxel terrain out of an image. in short, VERY COMPLICATED. Annoyingly, I could not wizard my way into making this work. however just yesterday(?) (the 18th of may) I figured out a way to do this with my specialty. materials. WHOOO and it works. I can generate a terrain out of any (heightmap) image! so I currently have the regular mega risk map, Mata Nui from Bionicle, and some Skyrim map that Shmid sent me. but the skyrim map just died for unknown reasons so I have to redo that :/ but that will take approximately 5 seconds to fix so you can assume that works.
well that's the main thing. me blogs if there is anything new and wizardy happening.
It's time once again for the monthly BLOG POST
I never intend to make one post a month, it just happens that way. Approximately once a month, a decent development is made. Every time I end on an optimistic note, saying that I hope I can get to writing about actual gameplay soon. I suppose last time I did the settings, this time the other major hurdle has been cleared.
I'm talking about multiplayer.
Although all of the functionality isn't there and the whole thing has yet to be tested thoroughly, I can proudly say that I seem to be able to host an online game, get a list of online games (through a 'join game' menu) and then join that game.
If you've been keeping up with us for the entire time, you'll know this is a huge accomplishment for us. We poked around with the Unreal's limited Blueprint multiplayer support during the prototype, but after a couple of infuriating weeks, we gave up on that aspect with the conclusion that the available Blueprint stuff simply wasn't able to give us what we wanted.
AND NOW IT WE HAVE WHAT WE WANTED. I really do hope that everything is working as well as it seems. I also really need to thank roomon1 on the Unreal AnswerHub for being awesomesauce and basically making this happen. Here's the question-thread that led to this post.
So now that that tremendous headache's out of the way, we can jump right into the fun stuff! JK, I still have some holes to patch up in the MP system and I have to glue everything I've currently got (a little bit) together.
By that I mean I have to make sure that all of the backbone stuff like multiplayer and settings and the plugin-based approach I'm taking to this (oh right that I have to talk about that too) all work in a cobbled-together way.
But finally I can finally see the part where I'm not working on infrastructure anymore and am making stuff I can take screenshots of. Hopefully something can be put together before I leave for game dev college in August. That's somewhat of a mini-deadline for me since I know that after that starts up I'll have school projects to worry about and won't barely be able to put any time into this. Hopefully I'll have it to the point where my partner Khan can take over.
Speaking of him, he's been doing some really cool stuff recently (and in the past as well). I should get him to post things here...
Anyway, see you in a month (or less if something cool happens).
I'm talking about multiplayer.
Although all of the functionality isn't there and the whole thing has yet to be tested thoroughly, I can proudly say that I seem to be able to host an online game, get a list of online games (through a 'join game' menu) and then join that game.
If you've been keeping up with us for the entire time, you'll know this is a huge accomplishment for us. We poked around with the Unreal's limited Blueprint multiplayer support during the prototype, but after a couple of infuriating weeks, we gave up on that aspect with the conclusion that the available Blueprint stuff simply wasn't able to give us what we wanted.
AND NOW IT WE HAVE WHAT WE WANTED. I really do hope that everything is working as well as it seems. I also really need to thank roomon1 on the Unreal AnswerHub for being awesomesauce and basically making this happen. Here's the question-thread that led to this post.
So now that that tremendous headache's out of the way
By that I mean I have to make sure that all of the backbone stuff like multiplayer and settings and the plugin-based approach I'm taking to this (oh right that I have to talk about that too) all work in a cobbled-together way.
But finally I can finally see the part where I'm not working on infrastructure anymore and am making stuff I can take screenshots of. Hopefully something can be put together before I leave for game dev college in August. That's somewhat of a mini-deadline for me since I know that after that starts up I'll have school projects to worry about and won't barely be able to put any time into this. Hopefully I'll have it to the point where my partner Khan can take over.
Speaking of him, he's been doing some really cool stuff recently (and in the past as well). I should get him to post things here...
Anyway, see you in a month (or less if something cool happens).
Monday, April 11, 2016
It feels like it's been longer than a month
It's time again for another month-apart update.
This time, I am able to say that NOT EVERYTHING IS BROKEN ANYMORE. I was able to essentially remake Mega-Risk and get everything locked within the vaults of source control. Over Spring Break, I was able to get a theoretically correct multiplayer setup going, but was forced to stop when, after getting all the code to compile, I could not make the in-game server list show any servers.
So I decided to get a settings system working. It may not have been made obvious in previous posts, but customization is a huge part of Mega-Risk. In real-life games, the rules are often tinkered with from game to game (and sometimes mid-game as well). Everything from the ability to trade territory cards to the number of troops that can be raised in a single turn to existence of unbreakable alliances are all things that are decided upon in each and every game. As such, I've been trying to figure out a fast and easy way to implement an ENORMOUS amount of game settings, with the ability to add more whenever we need to without any headaches.
My prayers were answered in the form of spreadsheets. Luckily for me, Unreal Engine supports the use of Excel Sheets to create data tables*. After a long night of getting the required framework in, I had pretty much created a system in which a central 'Settings Sheet' can be used to hold every single game setting in Mega-Risk. Even better, I found out I can edit this sheet in-engine once it's been imported into Unreal for the first time.
Actually hooking this data up to a set of variables took a bit longer. To get into the details, I had to make a set of menus that categorizes all settings into a neat little settings screen and then have every setting correlate to a variable in my GameInstance (basically a place where all settings and game-wide data is kept).
Thankfully, this system seems to be working now and I can try to get multiplayer working. Well, when I say that I mean I can now help my partner with the problem he's having with source control so he can try and solve the problem because I can't figure it out for the life of me.
All-in-all, Mega-Risk is chugging along at a steady-ish pace and I think we're almost ready to make all the fun, cool stuff like actual gameplay soon. ;D
This time, I am able to say that NOT EVERYTHING IS BROKEN ANYMORE. I was able to essentially remake Mega-Risk and get everything locked within the vaults of source control. Over Spring Break, I was able to get a theoretically correct multiplayer setup going, but was forced to stop when, after getting all the code to compile, I could not make the in-game server list show any servers.
So I decided to get a settings system working. It may not have been made obvious in previous posts, but customization is a huge part of Mega-Risk. In real-life games, the rules are often tinkered with from game to game (and sometimes mid-game as well). Everything from the ability to trade territory cards to the number of troops that can be raised in a single turn to existence of unbreakable alliances are all things that are decided upon in each and every game. As such, I've been trying to figure out a fast and easy way to implement an ENORMOUS amount of game settings, with the ability to add more whenever we need to without any headaches.
My prayers were answered in the form of spreadsheets. Luckily for me, Unreal Engine supports the use of Excel Sheets to create data tables*. After a long night of getting the required framework in, I had pretty much created a system in which a central 'Settings Sheet' can be used to hold every single game setting in Mega-Risk. Even better, I found out I can edit this sheet in-engine once it's been imported into Unreal for the first time.
Actually hooking this data up to a set of variables took a bit longer. To get into the details, I had to make a set of menus that categorizes all settings into a neat little settings screen and then have every setting correlate to a variable in my GameInstance (basically a place where all settings and game-wide data is kept).
Thankfully, this system seems to be working now and I can try to get multiplayer working. Well, when I say that I mean I can now help my partner with the problem he's having with source control so he can try and solve the problem because I can't figure it out for the life of me.
All-in-all, Mega-Risk is chugging along at a steady-ish pace and I think we're almost ready to make all the fun, cool stuff like actual gameplay soon. ;D
Monday, March 14, 2016
Progress update: everything is broken
HELLO AGAIN, any and all who read this! It's been over a month, so I figured I'd give a status update. As the title mentions, everything is, once again, broken. How broken, you ask? Well, let me tell you.
Over the last month, I've learned a very valuable lesson: if you EVER mess around with your UE4 project files using Windows Explorer, there's a good chance you will permanently and irredeemably break your project so bad that it will either never compile again or the project will be unable to load.
After implementing basic forms of all of the infrastructural files in C++, I received some very weird compile errors. After some searching, the only help I could find was a suggestion that I delete some of the folders in my project, namely Build and Saved. I'm not 100% sure what these do, but I think Build handles all the files that are generated when the project is built/compiled and Saved is mainly backups and whatnot.
SO, I deleted these two under the impression that it was similar to clearing my cache.
I was very wrong.
On my next build, I got even more errors and suddenly Unreal would not load the project, giving me a minimal crash report for which there was no help. Frustrated, I deleted the entire project (I hadn't put too much work into it at this point) and started over.
This process repeated itself to some extent over the following weeks. One time, I was even able to get the Invasion mechanics coded before it flopped and burned.
Over the past two weeks, most of my time has been spent working on a research paper for my history class (school is still a thing that exists) and trying to find some scholarships to apply for. Mega-Risk was not opened at all during that time.
I'm back now, and I'm going to try to get this puppy stable and not running into a pit of spikes like a rapid Super Meat Boy every ten seconds.
Wish me luck.
Over the last month, I've learned a very valuable lesson: if you EVER mess around with your UE4 project files using Windows Explorer, there's a good chance you will permanently and irredeemably break your project so bad that it will either never compile again or the project will be unable to load.
After implementing basic forms of all of the infrastructural files in C++, I received some very weird compile errors. After some searching, the only help I could find was a suggestion that I delete some of the folders in my project, namely Build and Saved. I'm not 100% sure what these do, but I think Build handles all the files that are generated when the project is built/compiled and Saved is mainly backups and whatnot.
SO, I deleted these two under the impression that it was similar to clearing my cache.
I was very wrong.
On my next build, I got even more errors and suddenly Unreal would not load the project, giving me a minimal crash report for which there was no help. Frustrated, I deleted the entire project (I hadn't put too much work into it at this point) and started over.
This process repeated itself to some extent over the following weeks. One time, I was even able to get the Invasion mechanics coded before it flopped and burned.
Over the past two weeks, most of my time has been spent working on a research paper for my history class (school is still a thing that exists) and trying to find some scholarships to apply for. Mega-Risk was not opened at all during that time.
I'm back now, and I'm going to try to get this puppy stable and not running into a pit of spikes like a rapid Super Meat Boy every ten seconds.
Wish me luck.
Sunday, February 7, 2016
THIS IS STILL A THING
I'M BACK. It's been exactly two months since the last post. In that time, winter break has come and gone and now winter quarter is half way done. In that time I'll admit that I have been neglecting Mega-Risk. Unreal C++ scares me.
But over the last two weeks I finally took the time to finish (?) a Game Dev Document and start writing a small amount of code. I'm still very unfamiliar with the UE4 API and at this point I have no idea what is going to work. The basic plan here is to essentially port the majority of the prototype blueprints (especially the infrastructure stuff) to code and then use Blueprints for some simple stuff. Thankfully, Unreal has multiple example projects that I've been studying to see how to blend C++ and blueprints.
Since I've already got most of the stuff plotted out, it hopefully won't take too horrendously long to get everything up to the point of the prototype. I personally would like to see the project get there by summer, but who knows what will happen.
Hope to be back here soon with a good, solid update.
P.S. We finally got source control working! WOOOOOO
But over the last two weeks I finally took the time to finish (?) a Game Dev Document and start writing a small amount of code. I'm still very unfamiliar with the UE4 API and at this point I have no idea what is going to work. The basic plan here is to essentially port the majority of the prototype blueprints (especially the infrastructure stuff) to code and then use Blueprints for some simple stuff. Thankfully, Unreal has multiple example projects that I've been studying to see how to blend C++ and blueprints.
Since I've already got most of the stuff plotted out, it hopefully won't take too horrendously long to get everything up to the point of the prototype. I personally would like to see the project get there by summer, but who knows what will happen.
Hope to be back here soon with a good, solid update.
P.S. We finally got source control working! WOOOOOO
Monday, December 7, 2015
Kback(ish)
Figured I'd pop in here for a quick update. Fall quarter is about done so Mega-Risk production should resume in a few days. In the mean time, I forgot to post about one very important development: AI works. I forget how it was made to work, but it works. Also, since both Conrad(?) and I know C++, I figured we'd start on THE REAL VERSION.
If I haven't said so before, this whole thing has been a prototype. With a team of seasoned professionals who know UE4 inside-out and spend all day working, all the work cataloged in this blog probably would have taken a month or less. Unfortunately, we are none of these things and this has taken about a year.
THE REAL VERSION will use both C++ and Blueprints and will be released to people to download and put on their computers and use. I think I'll start that up after fall quarter ends. I know multiplayer never got prototyped but it is supposed to be done in code so I'm hoping our C++ will make it work.
If I haven't said so before, this whole thing has been a prototype. With a team of seasoned professionals who know UE4 inside-out and spend all day working, all the work cataloged in this blog probably would have taken a month or less. Unfortunately, we are none of these things and this has taken about a year.
THE REAL VERSION will use both C++ and Blueprints and will be released to people to download and put on their computers and use. I think I'll start that up after fall quarter ends. I know multiplayer never got prototyped but it is supposed to be done in code so I'm hoping our C++ will make it work.
Sunday, November 8, 2015
STATUS UPDATE
I don't have any actual progress to show off. Nothing has happened in the past few weeks. Conrad has been trying out a bunch of new ideas and has started planning out another game with Ethan (if you don't know who that is he knows lots about programming but doesn't actively work on Mega-Risk).
Meanwhile, I have had school things. Homework has gotten more intense and on top of that I have to compile a portfolio for a college interview comign up at the end of the month.
So, basically, I don't see any new stuffage being done for M-R anytime soon. I'll keep this thing updated if an unexpected development develops.
Meanwhile, I have had school things. Homework has gotten more intense and on top of that I have to compile a portfolio for a college interview comign up at the end of the month.
So, basically, I don't see any new stuffage being done for M-R anytime soon. I'll keep this thing updated if an unexpected development develops.
Sunday, October 18, 2015
Hi
Hello, all you nonexistant people! It's time for another post!
Basically all that's gotten done in the way of central Mega-Risk development is that I've gotten 2/3 Castle Cards working. Reinforcements, check. General, check. Marshal, not check. Why not marshal? Well, to put it simply, it's nearly untestable right now.
The way marshal works is that a defending player can play the card during a single battle to increase his highest die roll by one. So if he rolled a 4 and a 6, the 6 would become an otherwise-impossible 7 and nothing would happen to the 4.
In order to do this, I'd have to give the defender a chance to play a marshal if he get's invaded. As it stands, there's no way for the player's territories to be invaded. The AI is broken to the point of unusable and multiplayer is in a similar state. So, I'll hold off on developing that until one of those things starts working.
P.S. I mentioned that this was the only thing that's happened in central development. Conrad has conjured up a system that can basically generate random maps with landmasses containing multiple territories. It's still rough around the edges but it's very promising. Hopefully we'll see a fully-fledged random map generator in the future?
NEXT TIME: Probably AI or Multiplayer. I mean it this time, too. If you head over to the Trello page you'll see those are basically the only major things left to do unless I decide to set up game stats.
Thursday, September 24, 2015
On the Matter of Inactivity
To those of you who might be reading this blog and are expecting a new post soon, this is it. This is the post. It's a post to tell you that there will be no post, which doesn't make any sense but it exists anyway, questioning all laws of logic.
Anyway, school started up again and on top of that the I'll be taking the SATs next week. This means that cramming is a very real thing that actually happens. On top of that, the entire family is currently helping Dad recover from a back/hip injury.
All that stuff adds up to a lot of time not being spent on Mega-Risk. I should be back in comission in another week or so, maybe next Sunday, but until then Conrad will probably be the main guy working on stuff.
However, I won't leave you with zero status updates. Stuff has been worked on since the start of the month. Specifically, I've been trying to get Control Territories/Continents (my term for Pirate Islands and RGB Islands) to exist and Conrad has been trying to find a way to make that magical thing known as multiplayer to work. The two of us have also been taking turns trying to get the AI to function properly.
So at least the last few weeks haven't been a total loss.
Friday, September 4, 2015
NEW MAP (Mega-Risk v.Proto_0.0.4)
My god, making the full Mega-Risk map took forever. Two straight days of cutting up the map meshes, inserting all of the territories, manually creating all of the borders, and setting up the adjacents for every one of the 200+ territories in the map.
But now the full map is done.
I also managed to add continents and those UI tweaks I talked about in the last post. Also, Conrad made a bunch of seriously amazing looking sea-lines. Now all that's left is some sort of playability in the form of AI or Multiplayer. Conrad's made some headway in the MP department so I'm not sure what will be done first.
Once one of those is done, I suppose it'll be time to upload a downloadable release for testing purposes before we dive into all the Mega-Risky goodness.
Here, have some screenies:
Here, have some screenies:
Since a substantial amount of working thigns have been added, I suppose it's time for a new pseudo-release.
Mega-Risk v.Proto_0.0.4
Changelog:
- Made new 'Proto2' map
- Added Continents
- Added Sea Lines
- Added Fortresses
- Added Fortresses
- Tweaked Whirlpool texture to make it more realistic
- UI adjustments
- A couple more bug fixes
Saturday, August 29, 2015
Territory Cards
After the greatest headache since Invasion, there are now Territory Cards in Mega-Risk. Everything but the troop scaling is in there, mainly because I haven't taken the time to find out what formula Risk uses for that thing. Everything else works, though.
I'm hoping to get a full playable 'release' (with possibility of actual downloadable release) out in the next couple of weeks. On the todo list for that to happen is:
Screenies/GIFs probably coming later.
I'm hoping to get a full playable 'release' (with possibility of actual downloadable release) out in the next couple of weeks. On the todo list for that to happen is:
- Finish the AI (if we can't get multiplayer working we should at least finish that)
- Make some UI adjustments to make everything look nicer
- Fix that months-old minor Invasion bug where the virtual dice won't roll twice. (?)
- Sea-Lines
- More territories and continents.
So, basically, a bunch of easy stuff and the AI. :D
I'm really looking forward to getting all this base stuff finally done and out of the way so we can finally do what UE4 was made to do and make everything look PRETTYFUL.
Screenies/GIFs probably coming later.
Monday, August 3, 2015
Turns and Disaster Cards(Mega-Risk v.Proto_0.0.3)
Some more stuff happened last month! After grappling on and off with the problem known as multiplayer, I realized that I don't necessarily need to get that done right away.
This epiphany led me to question the nature of the entire project. I eventually found myself slightly revamping THE ENTIRE INFRASTRUCTURE (again) after I found out that instances (the thing we had been using to handle UI and a bunch of other stuff) are new, poorly documented, and didn't do what I wanted them to do. So, I deleted ours and put all the code it contained in other places, which fixed a buttload of problems.
A few minor bugfixes later, and I was ready to implement the myserious things known as TURNS. As of right now, I've put in the reinforcement and attack stages of Risk as well as the first fully Mega-Risk concept so far: DISASTER CARDS.
For those of you who've never played the original Mega-Risk, disaster cards are in-game events that happen every so often in-between turns. They grab a random territory and do something to make the owner (an sometimes all adjacent territory's owners) suffer. They could be anything from a lightning storm that halves the troop count to a deadly doomsday device that reduces everyone's troop count to 1.
I've got those working now.
So, all in all, the project is coming aloong nicely and, should the bug gods be kind, may be in a "playable" state before school starts!
OH, and I suppose this warrents a new 'release'. It's time for:
Mega-Risk v.Proto_0.0.3
Changelog:
- Removed GameInstance
- Added turn-locked territory selection
- Added reinforcement stage
- When a territory is selected, its troop count goes up by one.
- Added Disaster Cards/Events(I like that name better)
- Happen at the end of a round
- Select a random territory and affect its troop count in some way
- Added Top Bar
- Displays a variety of info including player's team, total troops, and other stuff
- Holds constantly-available buttons such as End Turn and In-Game Menu
- Added post-invasion troop movement
- Widget spawns after victory that lets players move a number of troops from the attacker to attacking territory.
Hmm, looking at that changelog it appears I added some stuff I didn't mention. Oh well.
I was going to post some GIFs but my screen recorder is giving me some problems. Once it's fixed I'll update this post.
This epiphany led me to question the nature of the entire project. I eventually found myself slightly revamping THE ENTIRE INFRASTRUCTURE (again) after I found out that instances (the thing we had been using to handle UI and a bunch of other stuff) are new, poorly documented, and didn't do what I wanted them to do. So, I deleted ours and put all the code it contained in other places, which fixed a buttload of problems.
A few minor bugfixes later, and I was ready to implement the myserious things known as TURNS. As of right now, I've put in the reinforcement and attack stages of Risk as well as the first fully Mega-Risk concept so far: DISASTER CARDS.
For those of you who've never played the original Mega-Risk, disaster cards are in-game events that happen every so often in-between turns. They grab a random territory and do something to make the owner (an sometimes all adjacent territory's owners) suffer. They could be anything from a lightning storm that halves the troop count to a deadly doomsday device that reduces everyone's troop count to 1.
I've got those working now.
So, all in all, the project is coming aloong nicely and, should the bug gods be kind, may be in a "playable" state before school starts!
OH, and I suppose this warrents a new 'release'. It's time for:
Mega-Risk v.Proto_0.0.3
Changelog:
- Removed GameInstance
- Added turn-locked territory selection
- Added reinforcement stage
- When a territory is selected, its troop count goes up by one.
- Added Disaster Cards/Events(I like that name better)
- Happen at the end of a round
- Select a random territory and affect its troop count in some way
- Added Top Bar
- Displays a variety of info including player's team, total troops, and other stuff
- Holds constantly-available buttons such as End Turn and In-Game Menu
- Added post-invasion troop movement
- Widget spawns after victory that lets players move a number of troops from the attacker to attacking territory.
Hmm, looking at that changelog it appears I added some stuff I didn't mention. Oh well.
I was going to post some GIFs but my screen recorder is giving me some problems. Once it's fixed I'll update this post.
Monday, July 13, 2015
Multiplayer.
As of right now, multiplayer is the bane of my existance. It is necessary for moving the project forward, yet it refuses to work. On the plus side, I am able to host a game and have other clients connect to it (under very specific circumstances).
That's where the working part ends. Everything that follows joining a game is ENTIRELY BROKEN. The amount of problems led me to make a Bugs list on the Trello Page.
Fortunately, our magic code man Ethan will be BACK IN BUSINESS after his six-month computer hiatus ends on Wednesday. Maybe he will have a magical solution to this.
Labels:
Complications,
Game,
Multiplayer,
Prototype,
Shmid,
Unreal
Sunday, June 14, 2015
I'M BACK. (Mega-Risk v.Proto_0.0.2)
It's basically summer so I can now at least try to keep this thing updated regularly. There has been some progress on Mega-Risk since I last made an update over a month ago. Namely, I implemented teams (pretty much). All players (or, since there is no multiplayer, the player) are only able to interact with territories of their color-faction.
I've made a GIF showing off theese thigns. I should do this from now on. BEHOLD, MY GIF-MAKING POWERS:
Now that I've gotten to a point where all of the features work, I think it's time for a new version. Thus, I dub the current stage of Mega-Risk:
Mega-Risk v.Proto_0.0.2
Changelog:
- Revamped GameMode
- Added foliage to map
- Added teams
- Territories all are assigned to a team, which determines their color.
- Players are also all on teams.
- Players can onl interace with territories that belong to them, unless they're invading, in which case they can also interact with territories adjacent to the attacking territory.
- Added Main Menu
- "Play SP" button enters main map
- "Settings" button enters currently functionless settings menu
- "Quit" button closes game
-Updated to Unreal 4.8
Next up: pseudo-turns (I say pseudo because they won't be real turns until multiplayer works).
I've made a GIF showing off theese thigns. I should do this from now on. BEHOLD, MY GIF-MAKING POWERS:
Now that I've gotten to a point where all of the features work, I think it's time for a new version. Thus, I dub the current stage of Mega-Risk:
Mega-Risk v.Proto_0.0.2
Changelog:
- Revamped GameMode
- Added foliage to map
- Added teams
- Territories all are assigned to a team, which determines their color.
- Players are also all on teams.
- Players can onl interace with territories that belong to them, unless they're invading, in which case they can also interact with territories adjacent to the attacking territory.
- Added Main Menu
- "Play SP" button enters main map
- "Settings" button enters currently functionless settings menu
- "Quit" button closes game
-Updated to Unreal 4.8
Next up: pseudo-turns (I say pseudo because they won't be real turns until multiplayer works).
Sunday, May 3, 2015
Invasion (mostly) works!
Yes, you read that right. I've finally gotten Invasion, the cornerstone mechanic of any Risk game, to a somewhat working state. I say somewhat because, basically, I can't get the game to compare more than one set of dice per roll.
To put this into perspective, say the game rolls [6, 4, 2] for the attacker and [6, 1] for the defender. Because of the bug, the game will compare the two highest rolls (the 6s) but afterwards it won't move on to compare the second highest numbers (the 4 and the 1). It will instead compare the two highest numbers twice. This causes nearly all invasions to bring both the defender and attacker's troop counts down into the single digits most every time.
I'd probably have been able to fix this over the past couple days, but I've been trying and failing to reinstall Windows onto my new SSD and I'm the sort of person who is unable to focus on anything once he comes across a difficult problem.
Hopefully I can get this thing to work soon so I can go back to Mega-Risk dev.
To put this into perspective, say the game rolls [6, 4, 2] for the attacker and [6, 1] for the defender. Because of the bug, the game will compare the two highest rolls (the 6s) but afterwards it won't move on to compare the second highest numbers (the 4 and the 1). It will instead compare the two highest numbers twice. This causes nearly all invasions to bring both the defender and attacker's troop counts down into the single digits most every time.
I'd probably have been able to fix this over the past couple days, but I've been trying and failing to reinstall Windows onto my new SSD and I'm the sort of person who is unable to focus on anything once he comes across a difficult problem.
Hopefully I can get this thing to work soon so I can go back to Mega-Risk dev.
Sunday, April 19, 2015
Multiplayer Thigns
Well, I tried to make it a weekly thing. And I failed. And I'm sorry.
Not much has happened over past few weeks. After I found that the storage site we were using would only let us store 1GB of stuff on it I told Conrad that I would look for an alternative. I am now using the recommended Perforce client and running a server myself, but Conrad and I are getting the same timeout problem we were with Subversion. So there's that. :/
On the actual dev side of things, I've been figuring out how to make multiplayer work because, for the most part, all of the remaining basic features will requre some sort of multiplayer functionality to work (turns, disaster cards[which happen in between turns], and some UI stuff). However, I found that our entire character setup is basically wrong. So I had to remake everything. Then I came across problem. As of today, I have posted my problem on UE4's AnswerHub and am waiting a reply.
So that is the state of the game. Hopefully the next time I make an update I'll have everything in a more working state.
Not much has happened over past few weeks. After I found that the storage site we were using would only let us store 1GB of stuff on it I told Conrad that I would look for an alternative. I am now using the recommended Perforce client and running a server myself, but Conrad and I are getting the same timeout problem we were with Subversion. So there's that. :/
On the actual dev side of things, I've been figuring out how to make multiplayer work because, for the most part, all of the remaining basic features will requre some sort of multiplayer functionality to work (turns, disaster cards[which happen in between turns], and some UI stuff). However, I found that our entire character setup is basically wrong. So I had to remake everything. Then I came across problem. As of today, I have posted my problem on UE4's AnswerHub and am waiting a reply.
So that is the state of the game. Hopefully the next time I make an update I'll have everything in a more working state.
Friday, April 3, 2015
A POST.
Spring break is nearly over and this is the first post during that time. :/
Although not as much got done as I had hoped, some very important stuff happened:
- Unreal went free, allowing Conrad to go full-on dev.
- We (kind of) got a form of source control was set up, and although there is a problem with it now, it will allow us to practically work on the same project all at once.
- I got invasion practically done. All that is left is to fix a bug or two.
Conrad has been great adding in details that I've been too busy with the main stuff to do. He's added in better camera controls, foliage, a main menu, and some music (although that was mainly lost in the great source control calamity).
I, meanwhile, have been figuring out invasion code and trying to get source control working. Speaking of which, I should explain why Mega-Risk didn't get a Minecraft-sized update these past couple of weeks. It happened in an event I like to call:
THE GREAT SOURCE CONTROL CALAMITY
About a week after the last blog post, Conrad and I had finally got source control working via an online repository hosting site. I had my project hooked up to it and all of my files were in there. Conrad had hooked his project up as well.
Conrad had more changes, but the changes I had made were more complex, so instead of either of us merging the source control files with our (and thus wiping out all of our progress), we decided that Conrad would copy everything I had done into his project and then upload his files, which I would download. I don't remember why, but Conrad ended up with a broken territory class. We tried fixing the problem in a variety of ways, but they all made everything worse until Conrad's project was completely broken and he had lost a lot of his work, including the music setup.
Fortunately, Conrad had uploaded some of his entirely new files to source control and I had added them to my project. Also, he had taked screenshots of some of his stuff and has been able to rework some of it from those. Nevertheless, it took us at least five days to get to a point similar to before the calamity.
But despite that, I'm proud to say that I should have invasion fully functional by the end of spring break on Tuesday and I can announce the next version.
I might have made more posts since two weeks ago, but at the end of any one day it never felt like we got any concrete set of stuff added in and I didn't want to say something like "we mostly got this and that done, but it's not done yet".
I realize I'm doing this here with invasion, but a number of things led to this today, including us having an actual meeting where we discussed things (:O), Conrad and I finally getting our projects synced and ready to source control again (once I fix an issue with logging in to the server), and Hank DLing Unreal (woo!).
I HOPE TO BE BACK SOON.
Thursday, March 19, 2015
kback
THE FINALS ARE OVER. SPRING BREAK HAS BEGUN. TWO WEEKS OF GOOD THIGNS.
At(or near) the top of that list of thigns is Mega-Risk dev. I've got plenty of time to work on this thing and start to morph it into something that looks less like a couple of morons flopping about with high-end software and more like an actual game.
Among planned features to be added over the next two weeks are(in no particular order):
- Full-fledged, dice-based invasion
- Multiplayer
- Ownership of territories by players
- More UI happiness
- Events(disaster cards)?
- Turns ???????
Invasion comes first, though. I've got Spencer's dice rolling program sitting on my computer, waiting to be rewritten in C++. Once I find out how to access code functions from UE4 blueprints, I'll hook the dice up to the invasion thing I have and then there will be a party or something.
After that's done IDK.
Also, since it's late and I couldn't start code conversion but I wanted to do something, I made a Trello board. The board is public so anyone can see it even if they don't have a Trello account. I'll try to keep that thing updated.
TRELLO LINK.
Also, since it's late and I couldn't start code conversion but I wanted to do something, I made a Trello board. The board is public so anyone can see it even if they don't have a Trello account. I'll try to keep that thing updated.
TRELLO LINK.
I'll be back soon with good, happy update stuff. :D
Subscribe to:
Posts (Atom)



