Wednesday, October 17, 2018

Eroico has been released on Steam

Eroico has been released on Steam:

If you download the demo, your unlock codes (Eroico or Noaika) can be placed in the game folder called "cloud", which will unlock the game as usual (uninstalling it may remove it from the libary though). If you've bought the game before and want a Steam code, email me and I'll see what I can do. However it might not happen right away, since I don't have the ability to create codes freely, they must be requested from Steam.

There have been a few minor updates:
-F1 now activates a cheat mode (the 1 key refills health and magic, 2 restarts the room for speed running practice.)
- New title screen
- The ending has different music, and is now animated.
- A few bug fixes.
- The Steam version should now automatically apply button mapping to Xinput controllers, which aren't supported normally in GM8.
- Cloud saves.

Edit: I'll be uploading the updated version to all the other platforms soon. (DLsite, Nutaku, Mangagamer, here.)

Wednesday, September 26, 2018

Eroico will be on Steam

With Steam opening it's doors to uncensored games, I ran out of reasons not to sell games there

I will probably release future games on Steam as well, assuming the doors don't get slammed shut after they realize crazy people keep coming in.

Would also be convenient if unlock codes purchased here unlock demos downloaded through Steam. Though I think that would probably be against some kind of rule, so I'll have to check.

Edit: Also, sorry for not responding to comments on previous posts as quickly. Blogspot hasn't been emailing me when people comment like it used to. Need update some settings.

Tuesday, August 28, 2018

Early GM2 template

I've said before that I want to do a GM template at some point, one that beginners with GM can use.

While this doesn't contain much yet, I figured I'd post it here anyway, since I happened to make a quick version for someone else. This doesn't contain what someone would need to make an entire game, obviously, but some people might find parts of it useful.

This contains
- Tile collisions
- A basic camera system with limiters
- Gamepad support
- Scripts for checking controls and collisions.
- Basic state system

It's rough around the edges since it's derived from the game I'm working on, so there's some stuff that isn't too clean, at the moment.

Anything in the project with blue icons represents files that I will update/add functions to later,
The goal being that the template could be updated without breaking a game project so long as game-specific code is not added to those files. The template could be updated by simply dragging the update into the GM project folder.

This isn't something I'm working on every day, but I want to add stuff to it every so often. Initially I will be refining how the system should work as a whole (since I want to be able to use it myself as a base for games later), but later I also plan on adding templates for things like the player and enemies. The end goal would be the ability to make a game without programming, for artists who just want to make graphics and design levels, while still having a system that programmers can modify to save some time.

I'm open to any suggestions, as far as adding stuff or how it should look from a usability standpoint goes. Will be a while before it can be used for anything by non programmers in a plug and play fashion, though.

Tuesday, July 17, 2018

Enemy states and formating

Sorry about the silence. Working on stuff, life stuff, etc.

I've talked before about making a template of some kind for people to use. While I'm not currently working on one directly, I am trying to streamline certain parts of my workflow, and that inherently means making something that's easy to use, but flexible.

Part of  the process of making a game is enemy behavior, or rather, the actions an enemy can perform. There are a few methods for making an entity "do" something in GM.

You can have every action as a different object,

Or all the code can be contained within one object, with each action/state being represented by a number.

Initially, I found it easier to use the first method, as when an object is created it has it's own set of events (create, step, animation end, etc). It also made it easier for me to debug games since an issue with an action could be easily isolated, and messing up an object wouldn't affect the rest.

However, it isn't really practical as games become more complex, and as I've become better at programming my original reasons for using it have become less relevant. GM also added #region which is very helpful for keeping code separated.

That said, for the second method everything an object can do is separated into a state. For example, a simple jump upwards might be state 5. So switching to a jump is essentially just;

state = 5

So, if you wanted a character to do this,

You can separate it into two states
- move until edge (1)
- wait and turn (2)

So, the object hits an edge, changes the state to 2, it plays out the state, and then it's built into state 2 that it returns to state 1 at the end.

This is basically the manual version of the method; every state does something very specific. However, despite the fact that "wait" and "turn" might be a part of other actions, they are combined, and only go back to state 1. This means that if I wanted to add a new move that involves waiting and turning before doing an attack, I need to make a separate set of states.


So instead, you can do things in a sequence. Let's say you have the following states;

- pace (1)
- wait (2)
 - jump back (3)
- jump forward (4)
- melee attack (5)
- neat pose (6)

If you wanted an enemy to jump back, do a pose, jump forward, attack, wait, and then go back to pacing. Instead of programming each state to lead into the next manually, we can program a system that plays them in order based on a simple sequence of numbers. This would be the above sequence.

sequence[0] = [3,6,4,5,2,1]

Thus, that "move" is sequence 0.

By doing this, you can set a sequence to play out, rather than a single state. This also comes in handy for cutscenes, where you need to be able to animate characters quickly and easily.


That said, the question becomes, how much control do I want/need, and how should it be formatted? If you have a state for "jump", what should determine how far, or the direction? For example, you could have each variation be a separate state;

-move around (1)
-shoot (2)
-low jump (10)
-high jump (11)
-low jump back(12)
-high jump back(13)

a low jump back and then shooting would be

sequence[0] = [ 12 , 2 , 1 ]

Or, you could be more complicated with the arrays, such as having modifiers included in the sequence. So instead it might be written like this;

sequence[0] = [[12,5,3],2,1]

With every state having a set of optional modifiers. In this case 12 would be the state, 5 could be jump height, and 3 could be horizontal speed.

In either case, the more more states you eventually have, the more difficult it would be to remember them all. It might make more sense to name states with strings;

sequence[0] = ["jump back", "shoot", "move around"]

Which I guess would looks like this with modifiers

sequence[0] = [["jump back",3,1],["shoot",bullet_1_ob,5],"move around"]

Yikes. Makes sense but probably looks intimidating.

Other formats
Instead of having everything in one array, you could also split controls into multiple optional arrays.

sequence[0] = ["wait","jump","shoot","wait","pace"]
sequence_xspeed[0] = [0,2,0,0,0]
sequence_sprite[0] = [0,0,0,pose_sprite,0]
sequence_time[0] = [10,0,0,50,0]

The first chooses the states to play in sequence,
The second chooses the xspeed modifier for each state,
The third overwrites the sprite that the state displays, with 0 using the default.
The fourth would change the wait time.

Using only sequence[0] with nothing else would use the states with defaults. Could also include states like "jump_back" so that there's a quick and dirty method if more control isn't required.

Of course, it's hard to say how useful so many options would be outside of making a template since; at the end of the day just programming what you want is generally going to be faster for things like enemy specific attacks. Where it would probably be the most useful for me personally is simply creating movement patterns, and for cut-scenes where you definitely need some kind of system.

Words words words...

Anyhow. Let me know if you know of any good standard practice for dealing with states. Maybe something that other engines like RPG maker do particularly well, or stuff you'd like to see when I do eventually make a template.

Back to work...

Saturday, May 12, 2018

What kind of protagonist do you prefer?

Figured I may as well just ask, kind of interested to see.

Content of each option

To give more information; this question assumes that a game would be spending the same amount of time on H content regardless of the type. A female protagonist would have 100% of the time spent on animations that include that female character. A game in which you can choose your gender would have that time split between the two.

In the case of my games, a male protagonist implies 100% of the enemies are female, with few body altering mechanics applying to the protagonist. Mechanics such as romance/affection or pregnancy are available for this type of game, involving enemies or other characters.

A female protagonist can involve mechanics like pregnancy, and while mind altering mechanics (lust, lewidity) are possible on a male protagonist, they are more common with a female one. Enemies can be male or female. Romance/affection mechanics are less appealing on male enemies, but would still be possible with either gender.

I'm also more willing to have a female character turn into a male as a mechanic, rather than vice-versa. That said, in a male/female choice game I would be able to add gender bending mechanics in either direction, as at that point it's basically just up to the player what they want, and the distinction isn't something I have to make.

Viability of each option

Gender bending and futa options assume that the majority of the animations would use the default female character, and roughly 25%, a little more, or a little less, would use the secondary form or attribute.

The easiest options are to have either 100% male, 100% female, or a 25% futa attribute, as none of these require extra sprites.

25% male gender bent requires only sligtly more work, as it would likely be a special "form" in which not all gameplay mechanics are applicable (moveset may be different, items may be different, etc).

Male/Female choice requires the most work, or limits the mechanics without further development time, as if there are sets of clothing, action animations, etc, each gender must have a sprite set for them. If these mechanics are not present, then the work would not be drastically different.

Wednesday, May 9, 2018

Oh hai money

Hwelp, looks like I may have missed a Nutaku payment so I got two at once. Turns out I have plenty of cash at the moment.

For now, I'll get the dental stuff done and go back to working on the game. Will work on the current Patreon animation here and there, but there's no huge rush since I'll be fine for now.

After the final two animations are done, if I still need the Patreon for income I'll switch to a weekly or bi-weekly game. However, I do want to clarify a few things regarding patreon and what I will and wont do;

1. I will not, and will never do any sort of pay-per-month patreon. I will only do pay-per-release models.

2. I will not do any patreon wherein I'm being supported to work on full commercial games (games I'll sell).

What I would do is a pay-per-update game designed solely to be a patreon project. That is, the game would be free to everyone, with patrons getting the updates early along with some kind of voting power. After the game is complete or I stop working on it, it would not be sold.

After Noaika is released, I will likely not do Patreon stuff anymore, as at that point I'll have 3-4 in-progress games to work on and sell. Though if I'm doing a game patreon at that point, I may tie it up into a finished state over the course of a few months and give it closure.

Anyway, all that out of the way, I do need to start thinking a bit more seriously about what I'll actually do for a weekly updated game.

I think that for it to work well, it should be something that is replayable. I've seen projects like Guilty Hell and Unholy Sanctuary that grow over time into a traditional game, but I find that at a certain point it isn't really the same as playing a normal game if you're either replaying the entire game every time an update is released, or experiencing the one new thing and waiting for the next one.

I think that something with some degree of procedural generation and simulation would probably be my best bet. Either a Rogue-Lite meant to be played in sessions, or something in which success comes and goes, even if you slowly progress. Either way it would be a platformer though.

An initial state for the game would probably be a home location, a procedural generated area outside of that home, with the initial goal just being survival

Each update would contain some kind of H content + game content. For example one update would be a new enemy + an animation, while another update might be new items/mechanics + an animation for an existing enemy, or simply an environmental animation.

The main thing I haven't figured out is whether to focus on long term progression or not. A world you "live in" and come back to each day, VS a game where you're meant to play and win or lose within 20 minutes to an hour. Simple pleasures of farming or befriending monsters doesn't really work if none of it is long-term.

A combination of the two might work, wherein there is long term progression, but also the risk of losing progress or assets, either losing aspects of your character, or encountering situations in which the status quo must be taken back over time. Perhaps with leveling your character to further levels requiring you to start from 0 in order to slowly build your persistent base stats, or losing your home location and needing to take it back. Will have to think about it.

Tell me what you guys would like to see from such a game. There's also the matter of the gender of the protagonist, since chances are it wouldn't be viable to do both genders and two sets of enemies, unless the graphics are low res.

Thursday, May 3, 2018

Goings ons

Still working on stuff. Frustrating delay-of-the-day is the need to get some expensive dental work done.

Unfortunately, Aster didn't really sell much on DLsite. They stuck it away in a nebulous shooter section, so it doesn't get the exposure of other action games. While I think that if it were a better game it wouldn't have mattered, it is somewhat frustrating to see it not get a normal chance. Might sell it on Nutaku, but man I really don't want to go through the process of preparing promotional stuff again.

So, I'm currently figuring out what to do. Probably Patreon animations. The dental stuff is time sensitive, so I can't simply wait until a game is finished; which is what I would do if that wasn't the case. Every situation like this kinda just widdles down my patience; I just want to work on games have nothing else to worry about.

After I finish what Patreon animations I need to do, if I need money again I'll probably switch from animations to a patreon game. Even an initial week or two of getting something to a "build on" state would be wasting less time than I do spinning my tires on some of these animations.

Sunday, March 11, 2018

Next project

I've decided to work on the mario/sonic style game. Once it's done, I'll go back to Noaika full-time. and stop the patreon animations.

To give some context, this game was more or less started because I made some sprites for fun, and added basic controls to test gamepad settings while I was working on Noaika. Stuff slowly got added after that whenever I was bored.

Once GMS2 came out, I used it as a guinea pig for testing the new Tile-based collisions, the benefit of which is that tiles dont slow down the game, which makes things like this possible with little performance impact.

It also speeds up collisions quite a lot, which is why I'll be converting Noaika to GMS2 as a first order of buisness, after this game is done.

As for the game itself, as you can probably tell by the fact that I keep calling it mario/sonic, it's an attempt at a movement based game, with some inspiration taken from each. It will include an  rpg style world map, with some metroidvania elements.

There have been a few snags here and there in finding the game's identity, which I guess is to be expected when you rip stuff from two entirely different games. Luckily I "think" I've mostly sorted those out for now. The two main problems were basically "what happens when you roll into an enemy" and "what the hell are coins going to be used for", both of which conveniently had the same solution which was "depends what item you have equipped".

At the moment, messing with moves is still an active process. Many enemies and level mechanics are done, however they will be changed as the player's moveset gets refined and added to. Being about movement, it's important that I have most of the elements complete before finalizing levels or even a demo.

Anyhow, that's all for now.

Wednesday, March 7, 2018


*dusts off blogger*

While I'm waiting on some stuff to get Aster on DLsite, I'm trying to figure out what I should work on and release next. Always the question..

Needless to say, my main goal at this point is to work on Noaika. My mistake over the past couple years has been saying "I'll release a quick side project so that I can work on Noaika without worrying about money!"

Enter feature creep, uncertainty, and the usual health problems, and I've done a ton of work on various projects without any of them being released. I'd start a project, get a ton done in a week or two, and then the project would blow up into something bigger. I'd work on it a bit before thinking "this is going to take too long", and off I'd go starting another side project, honestly believing that I'd be able to hold myself back and make something small in a month or two.

Hell, Noaika itself was initially a side project taking a break from this

In fact, let's take a look at the trainwreck so far.

Crimson Blue
    > Got too big
         Crimson Brave as side project
               >Got too big
                           >  Kurovadis as side project
                           > Finished Kurovadis.
X Crimson Blue
X Crimson Brave
Try some stuff
Unnamed Metroidvania
   > Was unsure of direction
         >Started Eroico to take a break with lower res sprites
         >Finished Eroico
X  unnamed Metroidvania
Martial arts game
   > Too high res
X  Martial arts game      
Low res metroidvania
                > Cant even remember why I abandoned it
X Low res metroidvania

Umbrella girl
         > Got too big, almost die from health problems.
                    > Noaika as small side project. Behind the scenes demo       
                    > Upsize Noaika due to feedback
                          > Collab side project while working on Noaika
                    > Public Noaika demo
                   > Health,  money problems.
                   > Noaika Pre-orders 
                  > Work on Noaika,
                  > Patreon animations start
                                               > let's make a side project to get out of this rut.
                                               > Nope
                              >Slow work on Noaika
                                               > let's make a side project to get out of this rut.
                                               > Nope
                               > Patreon animations get harder and slow down                           
                               >Slow work on Noaika
                                                > let's make a side project to get out of this rut.
                                                > Nope
                                 Eroico RE
                                         >  Finish Eroico RE
                               > Work on side project
                               >Pick up previous side project, Aster
                                         >Release Aster

That's a lot of red.
To count them up , I've worked on about 12 projects, 3 of which have been sold, and 5 of which are anywhere from 40 to 70% done in dev limbo, and the rest will never see the light of day. Noaika itself is basically a game and a half given that it has three versions at this point that are totally different.

Patreon worked well initially, but has slowed me down quite a bit. It's become harder and harder to come up with animation concepts that dont feel like I'm repeating myself, and a lack of focus and uncertainty in ideas turns into procrastination. I'm always left with the thought "I wish I could just do 5 game animations instead of this one big one"

So what now?

All that said, working on Noaika without doing something else is still not an option at this point, financially. Do I try and finish one the many side projects while doing patreon animations so I can pay off stuff and get back to Noaika with no disctractions? Do I work on Noaika and switch to working on a seperate weekly patreon game instead of animations so that I can have more frequent, consistent patreon releases?

Or do I abandon games altogether and work on like 8 patreon animations in a row and....actually nevermind that sounds horrible.

So, what do you think I should do? I could work on pretty much any of the side projects (which you can see a little more about in the projects tab up top) Could even get the umbrella game out of the way before it becomes any more outdated, graphically. If I start talking about making a new side game and tell you I can finish it in 3 monthes though, just give me a good slap.

Wednesday, February 28, 2018

If you didnt get your download

I've noticed that at one point there was a string of orders that either didn't get sent out, or they were not downloaded.

If you bought the game and didn't get your link, email me at and I can send it to you manually, if it was not emailed to you.

Monday, February 26, 2018

Mini game release: Aster

Well, this one's something a bit different, that's for sure.

This game is a collaboration I worked on with another artist, who I'll simply refer to as S. It's an Asteroids/arcade style game with in-game H-animations.

While it isn't the usual size or complexity of my other games, it ended up taking me a while to get around to finishing, mostly because the music and sound gave me a bit of artist's block. The bulk of the work was done (including the H animations, which were done by the artist), a couple years ago, so I felt like I should probably get it out of the way, being the smallest project.

In total, the game has 10 animations (no CGs). The demo covers about half of the game and it's content. Since it's not the usual sort of game, I've decided to do a bit of a pay-what-you-want thing, with a $1 minimum. You can play the demo and decide for yourself what you think it's worth. The profits will be split 50/50 between the artist and myself.

Also, if you pre-ordered Noaika, your unlock file will work with this, so you dont need to buy it.

As per usual, this is the initial release so there's sure to be some bugs. Let me know in the comments if you run into any problems.


Also, as I stated before I'd start posting on the blog again once I released something, and while this isnt a big game this is something. I'll also be making an dedicated page soon showing the ongoing status of all my projects, what I'm working on, etc.

Sunday, January 28, 2018

Eroico Revision V7


New version of the Eroico Revision. (Redone animations, revised CGs, gameplay changes)
Note: Old unlock files still work, and now Noaika pre-order files will unlock Eroico as well.