I'm going to keep this short and sweet. Here's a link for downloading Hail to the King - A Prologue:
http://rg.to/file/c3cc5116beb662e0c2355264a4febe3c/HttK-APvers1.2.zip.html
Hope you enjoy!
Yours,
Minterlint
Saturday, March 14, 2015
Wednesday, March 11, 2015
What to expect when you're expecting...an AIF game.
First, an update: Beta testing is (mostly) complete and I'm planning on releasing the game close to this weekend. Hooray, rah-rah, fina-fucking-ly, bravo! And all that jazz.
Second: I wanted to talk a little bit about what to expect from this *airquote*game*/airquote*. A better description--one that a couple of my beta-testers pointed out--is an interactive story that you follow along and make various choices at. That's not to say there aren't challenges and hidden things to find, they just aren't the main focus (or point) of this little prologue. Everything in this mini-game is designed to propel you into my next one, meaning there is no true resolution at the end; so I guess you could call this little experiment the AIF equivalent of blue balls (although I sincerely hope none of the gentlemen who play actually experience this--or the ladies and their version, either (blue cunt, vaginal wilting, pussy interruptus?). Some may be turned off by this style, while others will enjoy it, and either way, I'm good with that.
For me, it's been a success no matter what. I gained quite a bit more knowledge of different ADRIFT tools and techniques, this will serve as a good lead in for Hail to the King and, perhaps most importantly, it's helped me move through the sophomore doldrums. They can be a lot worse than people give them credit for. How often have we seen a first time author release a game and then...nothing? You have a lot of energy for that debut game, you think you've got a great idea that a lot of people will enjoy, it's exciting to finally release your creation to the rest of the free world and then comes the question, 'Now what?' The adrenaline and enthusiasm wears off and you're left staring at a partially-formed, not particularly thought out yet idea, and NONE of the coding done; it can be daunting. If nothing else, this prologue has gotten me excited again to pursue HttK and has inspired me to plan even more crazy shit that I'm not 100% sure I can deliver on (actions--good or bad--will affect the endings dramatically, quests for people you don't actually get to sleep with (heresy!), a money system, and a foreign language quiz (parlez vous Miopan?).
That's all from me for now. Once again, this has ballooned past what I'd planned but hey, you're reading all of it so I guess we're alright.
Yours,
Minterlint
Second: I wanted to talk a little bit about what to expect from this *airquote*game*/airquote*. A better description--one that a couple of my beta-testers pointed out--is an interactive story that you follow along and make various choices at. That's not to say there aren't challenges and hidden things to find, they just aren't the main focus (or point) of this little prologue. Everything in this mini-game is designed to propel you into my next one, meaning there is no true resolution at the end; so I guess you could call this little experiment the AIF equivalent of blue balls (although I sincerely hope none of the gentlemen who play actually experience this--or the ladies and their version, either (blue cunt, vaginal wilting, pussy interruptus?). Some may be turned off by this style, while others will enjoy it, and either way, I'm good with that.
For me, it's been a success no matter what. I gained quite a bit more knowledge of different ADRIFT tools and techniques, this will serve as a good lead in for Hail to the King and, perhaps most importantly, it's helped me move through the sophomore doldrums. They can be a lot worse than people give them credit for. How often have we seen a first time author release a game and then...nothing? You have a lot of energy for that debut game, you think you've got a great idea that a lot of people will enjoy, it's exciting to finally release your creation to the rest of the free world and then comes the question, 'Now what?' The adrenaline and enthusiasm wears off and you're left staring at a partially-formed, not particularly thought out yet idea, and NONE of the coding done; it can be daunting. If nothing else, this prologue has gotten me excited again to pursue HttK and has inspired me to plan even more crazy shit that I'm not 100% sure I can deliver on (actions--good or bad--will affect the endings dramatically, quests for people you don't actually get to sleep with (heresy!), a money system, and a foreign language quiz (parlez vous Miopan?).
That's all from me for now. Once again, this has ballooned past what I'd planned but hey, you're reading all of it so I guess we're alright.
Yours,
Minterlint
Wednesday, February 25, 2015
Yes, I am still alive! Beta-Testing is go!
So...I definitely wouldn't call myself the most consistent blogger in the world. I always seem to find myself wrapped up in other things--work, family etc.--and using the excuse 'I can write something interesting tomorrow.' But honestly, I don't find posts from other game designers describing the new content they added, or the new system they put together, or a programming snafu they spent hours fixing terribly exciting. Hell, I enjoy writing my games, but I often find myself bored out of my skull even thinking about writing a post that only serves to let people know I've done a little bit more work since the last blog post. For those of you who revel in such minutiae, more power to you; it just ain't me.
Now for the important bit, and why most of you are here.
My new (mini) game is being beta-tested as we speak. It was intended for two purposes: 1) To experiment with my programming capabilities in ADRIFT and try new things and 2) Give the background story to my next full-length game, Hail to the King. Much of the programming items are not readily visible in the main game--nor should it be if done reasonably well--and if nothing else, I discovered new ideas I really enjoyed exploring (branching pathways/events), some that I absolutely hated and never see myself using again (conversation trees), and some I am indifferent to (character movements). As for the success of the second goal, I'll leave the final decision up to you, the players.
I still have a bonus section that I'm finishing up while the main part is being tested, so I'm going to give a very tentative release of...before the last of the snow melts for the winter. Which, considering the kind of weather we've had recently, does not set a very specific goal, I know but c'est la vie.
Yours,
Minterlint
Now for the important bit, and why most of you are here.
My new (mini) game is being beta-tested as we speak. It was intended for two purposes: 1) To experiment with my programming capabilities in ADRIFT and try new things and 2) Give the background story to my next full-length game, Hail to the King. Much of the programming items are not readily visible in the main game--nor should it be if done reasonably well--and if nothing else, I discovered new ideas I really enjoyed exploring (branching pathways/events), some that I absolutely hated and never see myself using again (conversation trees), and some I am indifferent to (character movements). As for the success of the second goal, I'll leave the final decision up to you, the players.
I still have a bonus section that I'm finishing up while the main part is being tested, so I'm going to give a very tentative release of...before the last of the snow melts for the winter. Which, considering the kind of weather we've had recently, does not set a very specific goal, I know but c'est la vie.
Yours,
Minterlint
Subscribe to:
Posts (Atom)