(This post was originally written for the company's devblog sometime in April, 2016)
It was a cold New England day and my head was reeling from the long crunch ending just hours before I pulled myself out of bed that afternoon. As usual I kept to the groggy rhythm of checking emails, responding, updating etc. I went into the garage for a smoke or two after, quietly gazing at the relic of my old car while noticing a similarly pasty white typewriter peeking out from under the dusty yellow plastic bag just inches away. It was propped up by old furniture and other disparate objects of course. I wondered, how was it that I found myself here again? Contemplating the same old things that seemed like proper motivation just months prior.
I took to investigating the typewriter for anything that might tell me what it had been through. How had I just noticed it? Over time I grew into a deep respect for physical goods, computer hardware in particular. Unlike software, the hard tangible result was unmistakably yours. I was again reminded of it’s sturdy design upon touching the cold carefully spaced keys that gave only slightly with pressure. Eventually producing an audible *click*, to my satisfaction.
Instantly I thought back to when tossing indestructable Nokia’s around the middle school cafeteria was considered a good time. I retrieved a scarred iPhone from my pocket with the intention of Snapchatting my discovery when the buzzing began. It was Sunday and I had promised my team I’d be done rewriting what we lost by midnight. I finished half a day early.
I stepped back outside and my phone kept buzzing. The weather had turned gray. Pockets of snow lined the shaded walkway, desperately grasping for pockets of Winter in the Spring. We had lost three months of code to some freak accident involving backups and fatigue. I always said that there are reasons and excuses for why things happen. The latter usually being a cop-out when presented. The former typically accompanied by a solution. Whatever the reason, what was done was redone.
By the end of March we had commissioned more art using new money that had long since taken the place of what we raised via crowdfunding. We wrote better stories and code in a feverish attempt at getting Triple X Tycoon to a playable state we call the Dev-Alpha. Which is used primarily for internal testing and isolated builds. The game engine was made leaner and more features put on the block. There was just enough to give someone an idea of what the game could be, should it be completed before our last pissing-pot dissolved into dust. It was time to get the thing seen again. Shinier, grittier and sexier than ever.
You see, Triple X Tycoon is a business-management game that focuses on the adult industry. And that last part is pretty important to the idea no matter how you spin it. So our middle ground is that business and sex are consistently held together by the relationships people establish. Performers usually establish some sort of working relationship with one another with the ultimate outcome being profit. Big business is held together in similar fashion. Build a framework to represent complex relationships and you have the basis for growth and profit.
It’s been a long time since we started this project in September 2014. We’ve seen a small handful of other adult desktop games come to market in the past few months which serves to validate the idea that people are open to the idea of higher quality adult games outside of the browser. This leaves us with very little choice going forward, and so we’ve built our tech to scale.
The goal right now is to reach a place where we can all work full-time toward getting this thing out to our fans and backers sooner rather than later. Maybe coding all night actually works in favor of setting the atmosphere for the game. I wonder what the frontal laptop lighting and dark backdrop is channeling subconsciously. I mean, I’ve even got a mustache.