Closed beta


Alright, after the last poll, the majority would want me to finish Dimitri’s story first. Then there are also people who’d like for Dimitri’s story to be released all at once, which could be an option.

So I’ve been thinking and weighing my options: I enjoy releasing updates so that I can get feedback and polish the story in between chapters. However, I get that most people would like to play it all in one go.

In the past, Tailor Tales has been an open beta where anyone could play and leave behind feedback that would help me improve Tailor Tales. The game has progressed immensely since the first release and right now all of the core mechanics are in place, there’s really only more story updates + clothing updates which are easy to do.

Therefor, I think it’s best if I closed the beta at this point. A set amount of people will be getting the beta releases to test and leave feedback on, which I could use to polish the story and improve the game. When all of the chapters have been beta-tested for the current character (which would be Dimitri at the moment), I will release an update to the public so that people can play the story in one go.

This does mean I need a dedicated set of beta testers, and fans will have to wait a while before the next bachelor is released.

Are you okay with reading chapters every couple of months or so, getting a head start on everyone else, and do you want to help beta test the game?

Then click here apply to be a closed beta tester!


I will need around 10 or so beta testers, so if you want to get early access to the next Tailor Tales update, go ahead and sign up :)

Finishing the story first, or release as I go?

Neil’s story is finished, that means I can focus on Dimitri’s story.

With Neil, I had already written his story before creating the third version of Tailor Tales. Dimitri however, is at 50k words (out of 80k), his story is not yet finished. I don’t write chronologically , so certain chapters are completely missing, whereas other chapters are finished but they appear way later in the story.

The thing is, I could focus on finishing Dimitri’s story and then slowly add them to the game… or I could force myself to write chronologically and release Dimitri’s chapters as I go. This means frequent updates.

You could compare it to some fanfiction; sometimes you’ll get an update for the next chapter every once in a while.

Writing his entire story first means I get more time to polish it before it is published. When it is finished, updates will be faster than if I were to publish them as soon as I finish writing the chapters.

Basically; wait longer for faster updates, or instant gratification but longer downtime in between updates?

Or would you rather have an update that released his entire story in one go? :p


Neil’s ending statistics!

Since over a 100 people have completed Neil’s survey (at the end of his route), I can release some statistics!

Which ending did people get on their first run?
56% Passionate Ending
44% Innocent Ending

A slight majority of players favour being fierce more over kind when it comes to Neil’s route! Probably because it’s a lot better to bite back when Neil is acting immature. I’m glad that there’s not a huge divide, as that would indicate I wasn’t giving really good options for the player to make. Both choices should have their own merit, after all.

What did players like about Neil’s route?
By far, with 87%, people liked it when Neil would be caught off guard and show his awkward self. There are plenty moments in Neil’s story where he’s simply at the mercy of Joselina or is too embarrassed to act composed. It’s fun to knock Neil down a peg or two when he’s always so full of himself.

Runner up with 83% are the kissing scenes! People seemed to really enjoy those, which I’m happy for. I made sure to not write the story in such a way that the kissing would happen at the end, no – kissing and physical intimacy would happen throughout the story. Things need to be spicy!

Most memorable chapter?
42% voted chapter 16 as most memorable. This chapter is where Neil kisses Joselina on top of her counter in her boutique, which includes the first kissing CG. 37% voted chapter 12, the masquerade ball, which is where the first kiss happens! I’m surprised chapter 16 won over chapter 12 since the masquerade has a very fairy tale like feeling, but hot make out scenes win here!

Best CG?
No surprise here, CG 4, the kissing CG, is the most popular. Close behind is CG 6, Neil and Joselina’s selfie. In third place is Neil’s first CG, where he hides behind a laptop. What to take from this is that people love kissing CGs, as well as CGs where Neil looks ridiculous.

Do you like Neil’s purple hair?
80% liked his black hair more
9% no opinion
9% liked his purple hair more

As expected, people are in love with his new hairstyle! I always try to give characters different sprites in their routes.

Do players want to read 18+ sex scenes?
87% yes (adults)
7% yes (minor)
5% no opinion
2% no

This ties in what players wanted to see more of; steamy romantic scenes. Basically, 95% of players want steamy romantic sex scenes with their favourite guy. And why the hell shouldn’t there be sex? The characters are adults and there’s nothing wrong with getting frisky. Tailor Tales will eventually have premium content that unlocks the 18+ stuff.

And lastly, Caine is still the runner up for next bachelor to be released in Tailor Tales.

Thanks for playing Neil’s route everyone!

Tailor Tales beta 1.4

Tailor Tales v 1.4 - Screenshot 6

Tailor Tales v 1.4 - Screenshot 22

Download 1.4 on

– Music has been replaced (with a couple of exceptions)
– Fixed a bug where you couldn’t complete random clients sometimes
– Fixed a bug in Outfit with the trash icon appearing on the remove icon
– Added in more important clients
– Added in the Decorate option
– Overhauled the menu, you can now re-read chapters and switch characters much more smoothly
– The game autosaves after using Design & Outfit, and will ask you if you want to save after each chapter
– A few graphical updates to certain characters
– There are now bundles for colours and patterns, so you don’t have to buy them one by one anymore. Just look for Bundles in the shop
– Neil’s chapters 26 and 27 for both Passionate and Innocent were added
– Dimitri’s chapter 7 added
– 3 new CGs
– Several new backgrounds
– More patterns added
– Several new shoes
– Several new hairstyles
– Backgrounds now blur whenever a character is up close to you
– Added another special effect for backgrounds (fog)
– Added the option to select white hair for CGs
– Gold adjustments. It’s easier to earn money now and chapters won’t have a huge spike when changing characters anymore.

Alright, lots of things were added! Sorry for the delay, it was a big update.

In this update, the game will ask you to save after completing a chapter, and it will autosave after you come out of Design or Outfit. While people like manually saving, too many people were forgetting to save, so I needed a solution. I feel like this is the best of both worlds. The autosave on Design & Outfit is forced because otherwise the game might get errors due to people creating/deleting clothes and then exiting the game without saving.


The option to decorate your boutique has finally been added! You can buy furniture, wallpaper and flooring in the shop. Click the Decorate option to change your boutique. This background will show up in the story! Speaking of backgrounds, they will now blur whenever a character is up close to you. It’s a subtle effect, but I like it :)

Menu overhaul

The previous menu was very buggy (especially with CGs), but it should now work a lot better. You can now select which chapter you want to re-read (if you’ve unlocked them). 1.3.1 Beta players will have all of the previous beta chapters unlocked. You can also change the MC’s appearance and name as well at any point in your playthrough.

Neil’s ending
We’re here! Neil’s route was released in late February, and now, we’ve finally reached his ending. Chapter 26 and chapter 27 have two versions: Passionate and Innocent. Whatever your Fierce or Kind points were, that’s what ending you’ll read. The game will ask if you’d like to read the other ending, for those that are completionists and want to see all of the CGs. Remember you’ll still have to pay for it or complete important client’s requests. This update does not include the epilogue! That would be the final chapter for Neil.

Other notes

With all of these additions Tailor Tales is very close to demo status, or should I say, to completed status? As soon as Neil’s route is finished, and all the major features are included in the game – the only thing that’s left are adding in other routes, and updating the game with more clothing items. This also means your save files can be imported from the previous build – no more losing your progress!

Of course, the game won’t be officially complete until all 6 guys have been added, but I basically consider them add-ons. I will look into creating an updater for the game so you can import updates whenever one is available, so that you won’t lose your in-game progress.

Thank you to everyone who’s been following Tailor Tales and supporting it, it means a lot to me.

1.4 coming in November!

I really tried getting a release for October, but I misjudged my own timings a bit. Neil’s chapters were being beta read so I had some downtime and figured I could still make it in time, but alas, it doesn’t seem like I can make that deadline.

So 1.4’s release will be in November. It will include both of Neil’s endings, and chapter 7 of Dimitri. In total that’s about 20k words.

Bear with me!

Re-reading chapters

Tailor Tales v 1.4 - Screenshot 33

Tailor Tales v 1.4 - Screenshot 35

Re-reading chapters now work as intended! If you’ve unlocked a chapter, you can re-read it at any time, regardless of which route you’re on. Re-reading chapters does not affect your current progress such as the chapter or character you’re on, or your fierce/kind points.

You can also decide to re-start the route from that point on so that you switch routes (in case you were on a different character) and so that your kind/fierce points matter (they don’t matter when re-reading chapters). This means you don’t need to grind all the way from chapter 1 to chapter 25 to get the second ending, in case you want both endings.

Getting both endings should be easy enough; the game will automatically ask you if you want to start at chapter 25 again to read the second ending after completing the first ending. You can choose no and always go back to re-read the chapter again to get the second ending!

You may notice the button “Side stories” – these will be unavailable, as they’re meant for future updates in case I’ll ever add more stories!

Still working hard on overhauling the menu so that all the options work and there are no more bugs :)

1.4 coming out in October

Just a small update letting you know I’m planning on releasing the next update in October, which includes Neil’s ending!

Progress is a bit slowed down because I’m having the last chapters be beta-read so that I can release something a bit more fine tuned. Once those chapters are ready to go, I can add them to the game, which will take several days.

I’m also working on overhauling the menu so that it’s easier to read previous chapters and switch characters. There will be an auto-save system that saves the game after you exit out of the Design process, and the game will ask for a manual save after each chapter now as well. Lots of new stuff!

See you in October girls!

Blurry background

Just a neat and subtle feature I added; backgrounds now get blurred when the character is close to you.

Tailor Tales v 1.4 - Screenshot 22Tailor Tales v 1.4 - Screenshot 15

I quite like it! It make you focus more on the sprite.

I’m still hard at work for the next update. My to-do list is:

– Finish 4 more backgrounds
– Finish 2 more CGs
– Add Neil’s chapter 26 & 27
– Add Dimitri’s chapter 7
– Overhaul the main menu … maybe

Neil’s story complete

Neil’s story was complete a long, long time ago. But that was only one ending, I had to write the second one still.

It took a while to get me motivated enough to pull through it, but I managed to write the second ending and both of them are the same in length. Neil’s story clocks out at 86k words, though one play-through should result in about 80k words.

Tailor Tales does not have any bad or true endings – there is only the Passionate Ending and the Innocent Ending, which you’ll get depending whether or not you had more fierce or kind points.

Both endings should conclude the story in a different way, and for Neil’s story, each ending is about 7400 words. This is divided into chapter 26 and chapter 27. What is different between the endings, you ask?

Mostly, it’s how the guy will treat you based on your treatment of him. Have you been nothing but kind to him, he’ll mellow out some more and take charge. Have you been nothing but fierce to him, you’re the one taking charge and he sometimes gets a little heated with you.

Anyways, each ending should feel like a natural progression of your choices.

Since Neil’s story is complete now, I’ll have to finish up the new backgrounds, as well as two ending-exclusive CGs.

Beta 1.4 should include both endings, but I’m still undecided whether or not to add the short epilogue as well, considering that also has a planned CG, and that’s quite a lot of work.

Cover art


Tailor Tales finally gets its cover art! Took me a couple of weeks to finally finish since each of them is basically an entirely new sprite I had to make. It’s also high res, in case I ever want to start handing out posters and whatnot.

Accompanying the cover art is a fresh coat of paint for the blog as well as the page.

Anyways, back to bug testing and writing Neil’s Innocent ending!