2016-12-31

Fucked Up Burger Shack 6.14 + 4.12 Public Release

This will be the final release of Fucked Up Burger Shack ... for 2016. I'm squeezing this one out just in time me thinks. So now version 4.12 is the new release made public, but also the old release for Patrons whose new release is 6.14, which will be old later on. Got that?

To update you'll need to delete all of the files in the old source data path. There are some instructions in the included readme (read as ignore me) which may or may not make sense. Info about 4.12 is over here: Fucked Up Burger Shack 4.12

Download Version 4.12 from MEGA

So in version 6.14 I've added the ability to use text to speech on Windows and Mac. I had an uptick in Patreon folks in December so I was able to buy this asset called RT-Voice Pro for Unity. Having a more accessible version of FUBS is on my TODO list and this is a great start to that, so I definitely want to thank the Patron peeps for making this happen. I was saving up for TextMeshPro to add sharper/better text to FUBS, but RT-Voice was on sale so I went for it first. Linux TTS is supposedly on the way, so that's something to look forward later on.

Aside from that I've been screwing around with vector art for no obvious reason.



It actually has nothing to do with version 6.14, but, I mean, c'mon, look at that flyer! I did level up the game icon and added a little graphic to the screen resolution dialog that people will probably never see.

Luckily 6.14 also includes a feedback form where you can complain about my 'art'.

So content wise I've added some new paths to a few of the Rando events. There is an endless anal path during the late night serve scene, using strap-ons with women when robbed, and a bottom path with a little bit of a three-way during the sauce auction.

And last but not least I added a bunch of new dolls (19 of 'em).

Happy New Year internet!

FUBS Version 6.14 [Compatibility:6 Release:14]

• Added feedback submission form directly in game
• Added new dolls:
    - gold digger
    - repressed slut
    - sugar baby
    - chub
    - cow-mazon
    - daddy
    - genetic freak
    - twink
    - amazon trap
    - cow MILF trap
    - cow-mazon trap
    - MILF trap
    - piggy trap
    - trap
    - amazon
    - cow MILF
    - MILF
    - piggy
    - spinner
• Added Rando 01 group sex path
• Added Rando 02 strap-on harness fail path
• Added Rando 05 bottom path (requires cock partners)
• Added screen resolution dialog graphic
• Added TTS (text to speech) on mouse over for Windows/Mac ** this uses the RT-Voice plugin for Unity which I purchased thanks to all the Patreon folks **
• Added updated burger graphic to pre-load splash screen
• Changed app icon to updated burger graphic
• Fixed RANDO 04 missing event initialization

Download Version 6.14 on Patreon

2016-12-29

Version 6.14 teaser video ??

So someone told me that Fucked Up Burger Shack would be better if the text could be spoken out loud. I agree.

This needs a bunch more testing and features (that bitch needs to stop calling me 'page for p') but I thought it was worth a blog post. Yeah I'm going a little bit off the rails adding things, but what can I say, it's better than the opposite.

I'm pushing for a release version 6.14 before 2017.

2016-12-19

Feedback, Dolls, & Multiple Partners

Just a little blog post about some new stuff I've been adding to Fucked Up Burger Shack.

First I've added a feedback system directly into the game.
FUBS v6-14 Screen Shots

The goal is remove to barriers to providing feedback, because it does take some effort to navigate to the blog and go through blogger hoops to post a comment. And sending email is another kind of pain. Also the form can attach the current game output so issues will be easier for me to find.

No idea how this system will work out in the wild, but it wasn't too painful to setup. If this actually gets used by players, I think I can do a little more work to integrate it with Trello or github, that way there will be a public place to track bugs. I'm getting all serious and professional like ... well aside from the cursed cum and such.

In other news I've been adding new dolls:
  • twink
  • spinner
  • trap
  • genetic freak
  • amazon
  • amazon trap
  • chub
  • piggy
  • piggy trap
  • daddy
  • MILF
  • MILF trap
I had to create a new muscle category (freakish) just for genetic freaks, but generally RandoEngine is flexible enough to support all kinds of dolls. I'm in a perpetual ~research state~ coming up with ideas for more,  but I'm open to suggestions too.

And last but not least , remember that issue I had with adding multiple partners, where the game couldn't handle the amount of rules it required? And then the next update I did some kind of magic that boosted performance? So yeah, version 6.14 will have some good things if you are into multiple partners ^_^. Sometimes there is a method to my madness.

2016-12-13

AI

I'm on the march towards adding employees/spouses to Fucked Up Burger Shack. The road is long, hot, and sticky towards the tip, but it's the path that I chose. Seriously though I've gotten a little closer towards having the kind of AI that I want for NPCs in FUBS. The core of it is my interpretation of how Sims think, but I'm sure I'm missing quite a bit there.

I'm going for a system where NPCs act autonomously based on needs and wants, rules of behavior encouraged by the player, and the reality of what's going on in the moment. Once an NPC decides on an action to take they are put in place to do it. That's when time stops so that the player can act. They could throw a wrench into things by joining or interrupting in some way, or just ignore NPCs entirely since ideally the AI will continue ~doing what's best~ indefinitely. So managing the rules of behavior and interacting directly are going to be the primary things happening all the time.

There are a lot of details in a system like this and I think there are lots of opportunities for things to get good. The interesting bits for me are figuring out all the little questions like: How will NPC personality traits affect the actions they take? What happens when an NPC disobeys the rules the player has set? How will NPCs react to interruptions by the player? As you might imagine each of the NPC actions can turn into random events, as do player interactions like joining or interrupting.

I released version 5.13 on Patreon with the bare bones skeleton of the AI system in place. I'm just play testing like crazy to make sure that this system is as fun as I imagine before I get too invested in it. The plan is to make the next release along with a public release of version 4-12 around Christmas time.

2016-12-08

Been codin'

I've been tackling performance issues with my codin' cap on and came out only partially bruised. Check out this gif of the Debug screen for testing RandoEngine output.


What's happening there is I'm spamming the regenerate option using a keyboard shortcut. Each Rando is being generated using a 'crap ton' of rules that define all kind of stuff about them, from hair length to, foot size, to anal affinity. After that the Rando is copied over to a partner. A list of descriptions of the partner are shown when the page loads by checking another 'crap ton' of rules that blend words with properties in a (hopefully) sensible way.

Or in other words I've boosted performance for FUBS by a 'shit ton' and now what were the most taxing bits of the game are buttery smooth (literally in some cases).

I was really concerned that I'd reached the end of the line as far as optimization, but it turns out I just had to try some stuff out that I'd been thinking about for months. Unfortunately the changes that I've made have completely destroyed all of my unit tests for the compiler. Truth is I've had to rewrite those tests across so many iterations on the underlying system that I'm not even bothered about it at this point. Okay maybe a little bothered T_T

What's more important though is I'm planning on putting up another build with this new goodness this weekend. I'm working out some story events that are long overdue. I'm going to avoid biting off more than I can chew, and I'm hoping to have a first version of a new house mechanic inspired by the Sims. I'm just having issues stopping the AI from taking a shit constantly, but that's to be expected.

2016-12-01

Fucked Up Burger Shack 4.12

I haven't been blogging as much recently, so here's one. A few days ago I put out version 4.12 of FUBS on Patreon. Yeah it has more sex scenes and some new features, but what really matters is I was able to include references to Pokémon and Trump in a single scene. In a nutshell it includes: a new chikan encounter, can save Randos as contacts and have booty calls with a new experimental sex mechanic, game now has text color and a new font, Randos have more dick, breast, and other less important sizes, Lots of details for clothes, some other stuff.

Fucked Up Burger Shack 4.12 Changelog:

• Added ability to furnish apartment (currently just tv and couch)
• Added ability to purchase more stap-ons and stock replenishes weekly
• Added ability to save Randos met in positive encounters as contacts (currently 5 contacts can be added)
• Added basis of doll generation
• Added Booty Calls
• Added indefinite article generation
• Added many new clothing properties for Rando clothes
• Added more Rando depth: cock sizes, breast sizes, hair lengths, etc.
• Added RANDO 05
• Added text colors for Gae, business results, warnings, etc.
• Changed default Unity game quality setting
• Changed effectiveness of resting on couch/watching television
• Changed effectiveness of work actions with passive prep bonuses
• Changed in game font
• Changed Rando descriptions heavily
• Changed Rando gender weights
• Changed saves to no longer capture undo steps. This reduces file sizes and makes more sense since a save is essentially an undo step.
• Changed Unity version to 5.4.3f1
• Fixed a bunch of typos and oddities throughout the game.

The release got delayed due to a bunghole of issues that I ran into, so now the public/Patreon release schedule is all messed up and stuff. I think I'm going to go back to more frequent releases because they keep me focused on one thing at a time rather than going nuts on everything.

I've been working on optimization for the past few days because the more content I've been adding, the slower the game is getting. I actually wrote some multiple partner stuff that should have been in 4.12 but adding all the rules necessary for multiple partners basically fried performance. FUBS 4.13 will be built with Unity 5.5 which incidentally includes some performance improvements in the Unity player that ~should~ help out the little guys like me too.

2016-11-04

Fucked Up Burger Shack 3.11 (patch)

This is a bug fix version only. Version 3.11 fixes the dead ends in the bus tour scene and the pronoun issues with Bunkville Boys.

This is a source release only so you'll need a recent version of the game to use it.

Instructions:
  • If you have FUBS installed all you have to do is delete the old source folder in the directory that you set for game files, and replace it with the source folder found in the extracted version 3.11 update folder. 
  • If you don't have FUBS installed you can download it HERE, then if you want to apply the 3.11 update follow the instructions above.

FUBS v3-11.7z (152 KB)
https://mega.nz/#!YEMiRQiA!oUNy8e38cnw5IMBVk3Tl475HzKeuMqnFuRe7kwKc9bo

FUBS v3-11.sig (543 B)
https://mega.nz/#!NYd1Ub7J!hFqdE6efsh7t9Ex5K30_TvXz-cIOvFljz1smR-vPkho

2016-10-31

Fucked Up Burger Shack 3.10

3.10 is a rebuild of version 3.9 using a newer version of Unity 5.4.2f2, which seems to have fixed the strange blurry textness. I also added in text resizing to help with readability and such. I kind of did this fast without testing the build, so if anything is horribly broken feel free to leave a comment.

2016-10-30

Fucked Up Burger Shack 3.9 Public Release

Version 3.9 of Fucked Up Burger Shack is now available for download. This update mostly includes fixes for a bunch of issues people brought up, and some other things.

I should also have version 4.10 wrapped up within the next few days.

NOTE: When updating from previous versions, you'll have to move or delete the previous source folder so that the new source can be exported. That's the path for game files set when the game first begins.

2016-10-23

The MILF Problem

I've had my code hat on for the last few weeks. I've added text resizing, copying the current game output to the clipboard, and most importantly I've added nested embeds. Embeds are the only way to describe the Randos that get generated by the system without having to write countless variations by hand. The big problem with the implementation of embeds before was that they could only handle putting simple text in place of an embed call. Now embeds can call other embeds so that I can put descriptions inside of descriptions. This helps out in a lot of ways, but most notably it solves the MILF problem.

I really don't want to go into all the details of it, but basically the babe embed was always outputting MILF/DILF for Randos due to how text gets selected. I've been doing a massive overhaul of all descriptors to use the new embed nesting. I'm still tweaking things, adding word banks, fixing issues and trying to package everything together nicely for the next update.

Here are some exports of the Babe descriptor for a variety of Randos courtesy of the copy output shortcut:

    █ Babe: 'drop dead gorgeous daddy'
    █ Babe: 'bachelors graduated Venus'
    █ Babe: 'confident peach'
    █ Babe: 'big, ripped & shredded goddess'
    █ Babe: 'late twenties, early thirties Venus'
    █ Babe: 'average height, size-zero coquette'
    █ Babe: 'Middle Eastern DILF'
    █ Babe: 'small, small bull'
    █ Babe: 'barely legal fox'
    █ Babe: 'average, average weight siren'
    █ Babe: 'barely legal sex kitten'
    █ Babe: 'Latina seductress'
    █ Babe: 'Native American flirt'
    █ Babe: 'African seductress'
    █ Babe: 'barely legal fox'
    █ Babe: 'Asian Adonis'
    █ Babe: 'early twenties siren'
    █ Babe: 'forty plus cougar'
    █ Babe: 'late twenties, early thirties MILF'
    █ Babe: 'high school educated siren'
    █ Babe: 'middle class Aphrodite'
    █ Babe: 'plain looking siren'
    █ Babe: 'barely legal fox'
    █ Babe: 'stunning arm candy'
    █ Babe: 'stunning Aphrodite'
    █ Babe: 'high school educated baldy'
    █ Babe: 'White gigolo'
    █ Babe: 'mixed race cougar'
    █ Babe: 'tiny daddy'
    █ Babe: 'Native American bull'
    █ Babe: 'average weight, puny vixen'
    █ Babe: 'MILF'
    █ Babe: 'barely legal bull'
    █ Babe: 'barely legal flirt'
    █ Babe: 'normal looking MILF'
    █ Babe: 'average height, bulky bull'
    █ Babe: 'middle class DILF'
    █ Babe: 'Indian gigolo'
    █ Babe: 'college quitting bull'
    █ Babe: 'barely legal boy toy'
    █ Babe: 'barely legal gigolo'
    █ Babe: 'Indian gigolo'
    █ Babe: 'Black flirt'
    █ Babe: 'middle class bull'
    █ Babe: 'siren'
    █ Babe: 'mixed race minx'
    █ Babe: 'Black siren'
    █ Babe: 'average height, very big DILF'
    █ Babe: 'middle class cougar'
    █ Babe: 'femme fatale'

Here is a dump of some other important descriptors:

Rando Description:
    ░ Ass: 'dark chocolate petite heinie'
    ░ Breasts: 'hanging sweater stretchers'
    ░ Pussy: 'dry, youthful twat'
Rando Description:
    ░ Ass: 'Indian petite ass'
    ░ Breasts: 'stacked, soft implants'
    ░ Pussy: 'dark chocolate snatch'
Rando Description:
    ░ Ass: 'White petite booty'
    ░ Breasts: 'barely bouncy, micro itty bitty titties'
    ░ Cock: 'straight, heavy dainty dick'
    ░ Balls: 'perfect, fertile lady grapes'
Rando Description:
    ░ Ass: 'tiny bony derrière'
    ░ Breasts: 'itty bitty titties'
    ░ Cock: '!!Rule Not Found!!, jailbait lady phallus'
    ░ Balls: 'stuffed, sterile lady family jewels'
Rando Description:
    ░ Ass: 'average sized muscular gluteus maximus'
    ░ Breasts: 'bulky chest'
    ░ Cock: '8 inch, cut dick'
    ░ Balls: 'nuts'
Rando Description:
    ░ Ass: 'Black thick keister'
    ░ Breasts: 'naturals'
    ░ Pussy: 'virgin twat'
Rando Description:
    ░ Ass: 'plump, Middle Eastern bubble butt'
    ░ Breasts: 'sporty chest'
    ░ Cock: 'straight phallus'
    ░ Balls: 'rocks'
Rando Description:
    ░ Ass: 'dark brown muscular posterior'
    ░ Breasts: 'average, ripped & shredded chest'
    ░ Cock: 'extra thick big black cock'
    ░ Balls: 'donkey, fertile itchy and scratchy'
Rando Description:
    ░ Ass: 'big, vanilla bubble butt'
    ░ Breasts: 'soft, perfectly sized naturals'
    ░ Pussy: 'White, virgin beaver'
Rando Description:
    ░ Ass: 'dark chocolate thick booty'
    ░ Breasts: 'buxom udders'
    ░ Cock: 'dark chocolate, straight lady pecker'
    ░ Balls: 'fertile, perfect lady grapes'
Rando Description:
    ░ Ass: 'average sized round rear end'
    ░ Breasts: 'lean chest'
    ░ Cock: 'cut, mocha cock'
    ░ Balls: 'loaded, fertile walnuts'
Rando Description:
    ░ Ass: 'Black round derrière'
    ░ Breasts: 'soft, very wiggly naturals'
    ░ Pussy: 'youthful snatch'
Rando Description:
    ░ Ass: 'White badonk'
    ░ Breasts: 'bloated chest'
    ░ Cock: 'gigantic schlong'
    ░ Balls: 'stuffed orbs'
Rando Description:
    ░ Ass: 'Asian muscular ass'
    ░ Breasts: 'bulky chest'
    ░ Cock: 'middle class tadger'
    ░ Balls: 'fertile, picturesque balls'
Rando Description:
    ░ Ass: 'big round ass'
    ░ Breasts: 'soft, barely jiggly boobs'
    ░ Cock: 'solidly thick femme BBC'
    ░ Balls: 'fertile lady grapes'
Rando Description:
    ░ Ass: 'Asian petite ass'
    ░ Breasts: 'muscly chest'
    ░ Cock: 'middle class, !!Rule Not Found!! organ'
    ░ Balls: 'loaded rocks'
Rando Description:
    ░ Ass: 'badonk'
    ░ Breasts: 'overdeveloped naturals'
    ░ Pussy: 'top notch kitty'
Rando Description:
    ░ Ass: 'small muscular ass'
    ░ Breasts: 'bulky chest'
    ░ Cock: 'straight phallus'
    ░ Balls: 'sterile spunk bunkers'
Rando Description:
    ░ Ass: 'small flat bottom'
    ░ Breasts: 'soft, developed, jiggly udders'
    ░ Pussy: 'mixed race, !!Rule Not Found!! slit'
Rando Description:
    ░ Ass: 'vanilla donk'
    ░ Breasts: 'highly underdeveloped cup cakes'
    ░ Cock: 'cut cutie length'
    ░ Balls: 'sterile lady balls'
Rando Description:
    ░ Ass: 'big thick buns'
    ░ Breasts: 'slightly milky, very jiggly, soft udders'
    ░ Cock: 'heavy femme rod'
    ░ Balls: 'fertile lady stones'
Rando Description:
    ░ Ass: 'African donk'
    ░ Breasts: 'impossibly milky, very jiggly naturals'
    ░ Pussy: 'puss'
Rando Description:
    ░ Ass: 'very big wide rear end'
    ░ Breasts: 'soft naturals'
    ░ Cock: 'dark brown lady schlong'
    ░ Balls: 'fertile lady nuts'
Rando Description:
    ░ Ass: 'European muscular booty'
    ░ Breasts: 'barely jiggly, ripe, soft bee stings'
    ░ Cock: 'working class, 9 inch sex'
    ░ Balls: 'little, fertile lady nuts'
Rando Description:
    ░ Ass: 'light brown round ass'
    ░ Breasts: 'big, tight chest'
    ░ Cock: 'rod'
    ░ Balls: 'baby, sterile family jewels'
Rando Description:
    ░ Ass: 'dark brown round buns'
    ░ Breasts: 'soft naturals'
    ░ Cock: 'dark chocolate, perfectly thick femme big black cock'
    ░ Balls: 'lady itchy and scratchy'
Rando Description:
    ░ Ass: 'Latino petite ass'
    ░ Breasts: 'tight chest'
    ░ Cock: 'dick'
    ░ Balls: 'donkey, sterile acorns'
Rando Description:
    ░ Ass: 'Latino petite ass'
    ░ Breasts: 'tight chest'
    ░ Cock: 'dick'
    ░ Balls: 'donkey, sterile acorns'

These are all very much work in progress (notice the !!Rule Not Found!!s, 'average's,) yet I really like the kinds of things this new system can support. A few favs:
  • 'average height, size-zero coquette'
  • 'barely bouncy, micro itty bitty titties'
  • 'dark chocolate, straight lady pecker'
  • 'average sized muscular gluteus maximus'
  • 'big, vanilla bubble butt'
  • 'overdeveloped naturals'
  • 'dark chocolate, perfectly thick femme big black cock'
  • 'mixed race minx'
  • 'buxom udders'
  • 'big, ripped & shredded goddess'
  • 'White badonk'
  • 'impossibly milky, very jiggly naturals' ... I better stop ^_^

2016-10-17

Text resizing


 

I've finally gotten around to adding the ability to resize text in FUBS. It should make the game playable for folks with retina and high DPI displays, and just generally help readability. Text very much blows in Unity, but no turning back now, etc.

2016-10-16

FUBS Modding Part 1: NPC Gender modding

It's about time I write up something about modding Fucked Up Burger Shack. If you read through and follow this nonsense you will have a mod file that will alter the game to produce Randos of different genders at a fuzzy rate of your choosing.

First we need to find the source files that FUBS exports. By default these are at a path like ~/My Games\Fucked Up Burger Shack



Inside the 'Fucked Up Burger Shack' folder there should be a 'source' folder.



That is where we can mess with the game. In version 2.8 you will see two folders inside of 'source', 'FUBS' which has most of the source of the game, and 'RandoEngine' which has the source files for NPC generation and descriptions. In later versions the descriptions are in a third folder named 'Partners'.



Our task is to change the probabilities of genders appearing for the Randos that you run into in FUBS. There are different ways to approach this, so we will start with the easiest, deletion.

Deletion

Navigate to /Fucked Up Burger Shack/source/RandoEngine/Generation/Bio/
and open up the 'Tier 01 Bio Gender.fate' file.



This is a .fate file which is really just a text file. I'll be using SublimeText to edit the file, but any text editing app will work.



So the gibberish at the top of the file between /* and */ on lines 1 to 14 are comments that can be ignored. They are entirely optional.

Line 16 '@contributor p4p @end' is a command to the system that credits the person who worked on the file. This is related to the credits for the game, but for now it can be ignored. It is also optional.

Line 22 marks the start of the first rule in the file. You can think of a rule as a container that defines text to display to the player and commands to run in the system. Rules also have a set of criteria attached that help determine when they will be displayed or run.

Breaking down this line it starts with '::', marking it as the start of a new rule. This is followed by a space (' ') and 'Gender'. Gender is the title of the rule. In this case we won't ever see the title because this rule is only used to set variables rather than display text.

Next there is another space and then a bunch of gibberish between two square brackets, '[rule($R == ^REGenGender && $prefMen == ^yes)]'. The meaning of this stuff is to say that this rule applies when the variable '$R' is equal to the value '^REGenGender', and the variable '$prefMen' is equal to '^yes'. Notice that '==' means is equal to and each of these statements is separated by '&&'.

So elsewhere in the game when we are looking for rules that can set gender, we use a command that sets the variable '$R' to '^REGenGender' and the system will return one matching rule. When playing, the preference for if you will fuck/be fucked by men also sets the variable '$prefMen' to true or false (yes or no) behind the scenes. Boolean values have different representations for whatever reason, so true can be written as '^yes', '^true', '1', and false may be written as '^no', '^false', '0'.

Line 23 is where the body of this rule starts. The '>' character marks the start of a command. This gives an instruction to the system to do something. In this case we are using 'set' which assigns a value to a variable. This set command will give the variable '$REGenderBiological' the value '^biologicalMale'. Notice that a single '=' is used for assignment.

Line 24 is another set command that assigns the value ^male to a different variable '$REGender'. FUBS uses these two variables along with many others during generation to build random NPCs. Looking forward in the file we see two other rules for women that follow the same format, but assign different values for the '$REGenderBiological' and '$REGender' variables.

Back to the major point here, we want to modify the game by deletion. So if we were to delete this file, when the game does a search for a rule where '$R' is equal to the value '^REGenGender', it will never find anything. This would lead to an error and generally be bad. Instead we can just delete at most two of the three rules if we wanted. For example, we could eliminate men and trans women by deleting their rules (lines 22 to 32).



Keep in mind that in the case that we have deleted the men and trans women rules, and the player does not set the preference for fucking women or being fucked by women, the game will have an error because the criteria of the women rule are not met. In other words '$prefWomen == ^yes' must be true for the rule to be selected. To fix this we can just remove that criterion (by deleting '&& $prefWomen == ^yes' in line 23) and ignore the players preferences completely.



Rules at minimum require a single criterion for the '$R' variable, which determines when the rule will be used. Looking at the original version of this file, each of the three rules have an equal chance of being selected at random since they all have two criteria. During a game the system does a search of all defined rules and will select the best possible match, or if multiple rules match the system will randomly pick one. By default this means you have an equal likelihood of encounter men, women, and trans women.

The best possible match is determined in part by number of criteria, so more criteria will always beat less. The system uses priority, but more on that later. When multiple rules match, weighting comes into play.

Weighting


In previous versions of FUBS I used weighting to determine how frequently players could encounter men/women/trans women in the game. 'weight' is another command that we can include in the body of a rule to help the system pick from several possible rules. A greater weight means greater likelihood that a rule will be selected. By default rules are defined with a weight of 1.

So now lets add this command to weight the three gender rules.

> weight 1000




I don't think of weighting as an exact science, it's more about what seems right where many rules potentially exist. In other words, I couldn't give you an exact probability of a rule being selected using weights, but a rule with weight 1000 will be selected nearly always compared to rules with the default weight 1. Over time I've moved towards the AFCOR concept from biology for weighting (https://en.wikipedia.org/wiki/ACFOR).

A – The species observed is "Abundant" within the given area.

> weight 1000
C – The species observed is "Common" within the given area.
> weight 750
F – The species observed is "Frequent" within the given area.
> weight 300
O – The species observed is "Occasional" within the given area
> weight 100
R – The species observed is "Rare" within the given area.
> weight 1
It's tempting to give super big numbers for weights, or negative values, but they either won't work or will fuck things up.

I am guessing that most players have a particular ratio they'd like for how frequent different genders appear, even if it is just to emulate population statistics, so weighting effectively allows this. But having changed the file, it is a problem to have to redefine these rules across game updates, so this is where priority can help.

Prioritizing


When FUBS is updated you have to delete the previous source folder so that the new source can be saved in it's place. Yeah that's kind of tedious (it's on my list), but more importantly if you do make changes to the source you would probably not want to redo them each time. One solution to this is to make your own .fate files and use prioritized rules where needed.

Taking the weighted gender rules from before, lets copy the entire file into a new .fate file. I created a new folder under 'source' and named it 'My Stuff', then created a file .fate named 'Gender stuff.fate'



Now when I update the game I can just move 'My Stuff' to a safe location, delete the old source, and add 'My Stuff' back after the new source has been copied in.

At this point the game would have six gender rules to choose from. Depending on the weights used it is probably more likely that the weighted rules will be selected, but we can use the 'priority' command to enforce it.

Just as it sounds, the priority command will prioritize a rule above others during selection. It looks a lot like the weight command and by default all rules start with a priority of 1. Add the following command to your custom rules.

> priority 2



Again you shouldn't add negative priorities or add super big numbers for priority.

So here is a summary of what the system will now do:
  1. First it will search for rules where '$R' is equal to the value '^REGenGender'.
  2. It finds six rules (three from the original file and three from our mod file).
  3. It keeps the priority 2 rules, but discards the original rules with the implied priority of 1.
  4. Each of our rules has the same criteria count so they will all be evaluated.
  5. If the player has enabled all of the genders ($prefMen == ^yes, $prefTransWomen == ^yes, $prefWomen == ^yes) then all three rules are available for selection.
  6. The odds of each rule being selected are in the favor of trans women, women, and then men, since the weights are set as 1000, 750, and 300 respectively.

And there you have it. You now have a mod file that will alter the game to produce Randos of different genders at a rate of your choosing. This is the first post I've made like this so hopefully it isn't a complete mess.

Here is a copy of the final file https://mega.nz/#!lR8WAAaS!7XO6LEyWhBZLKNRDY663mO9MX7bAwZD_F5qZDNSbbSU

2016-10-09

Fucked Up

Something is broken in FUBS, I have no idea what it is, but I'm carrying on anyway.

This week I was working on a new chikan event. Thing is, the feeling of groping an absolute stranger's ass deserves an accurate and detailed description. Something like this:

'Admiring how the lean babe's skin tight yoga shorts accentuate her bubble butt, you brazenly squeeze her ass cheek with your hand, delighting at the soft feel of cotton and ass flesh.'

That kind of thing is important, so I went through all of the upper/lower clothes and underwear that Randos wear and added new stats to them for things like fit, exposure type, texture, fabric, fun bits coverage, etc. After painstakingly defining these things for like 100+ items, I opened up the game to test it and the screen froze on the debug page.

After a bunch of tinkering with the source I couldn't find the problem, so I just rolled back the changes but the error was still happening. Then I fiddled with the code for the game to try and see if I could spot something, but came up short.. Just as I was ready to write a post about burning everything to the ground, I tested the game one more time and the freeze was mysteriously gone -_-.

So something horrible is definitely lurking in the source of FUBS or the code that runs it, but I have no idea where or what is. I'm not going to worry too much about it because I don't want to sink time into it. I have lewd to write!

2016-10-03

Fucked Up Burger Shack 3.9

Finally an update ... and it's mostly bug fixes. I suppose fixing issues is important, but September was a real drag for me. I like pretending everything works 100% so that I can continue adding things, but then people find issues here and there and I'm all like making tasks lists and junk. I want to spend my time writing Chikan, not doing Kanban! I honestly can't even bring myself to write about all the bug fixes, so here is the halfhearted change list.

Version 3.9
Features
    • General
        - Added debug links to test story events
        - Added location Sex Shop
    • Events
        - Added SIM 01
        - Added RANDO 02 sauce failure path
        - Added RANDO 05 auction
    • Randos
        - Added Ass Shape generation based on weight, muscularity, race, etc. and updated ass descriptions.
        - Added Cock Curvature generation
        - Added preference for hormone levels in order to generate more pleasing Rando's
     
Changes
    • Events
        - RANDO 03 remove cum farting line
    • Randos
        - disable MILF/DILF babe descriptions for better balancing
        - increase hair length for feminine men

Improvements
    • General
        - Update to Unity 5.4.1
        - Increased scroll sensitivity
    • Events
        - DAY 1 Add fast option select instructions
        - REM 03 "You are such a dirty." statement was vague.
    • Randos
        - Flatten the odds of babe descriptions for more variation

Fixes
    • General
        - prevent depositing and withdrawing negative or zero values from the bank because apparently that's something cubano tried -_-
    • Events
        - RANDO 02 "on pants" typo
        - RANDO 02s fix trans woman content
        - RANDO 03 added missing stat bars on event exit
        - RANDO 03 fix trans woman content
        - REM 01 dead link
        - REM 03 rule name conflict causing loop
    • Randos
        - womb description fertile typo


This is also the first release that I'm putting on Patreon before making it public. I'm hoping folks won't mind this too much, since 3.9 doesn't have much new stuff... okay there is something kind of nice, but it's nothing major at all >_>. Next release things will be more balanced since I'll have something to make public along with the Patreon early access.

My goal for October is to focus solely on events. All of the events. I want to get to the point where every work action leads to something lewd. All of the lewd. I have a bunch of fleshed out plans for scenes, and I shouldn't have to mess around with Rando generation or descriptions to get them done. Of course, my plan for 2.9 was to just do bug fixes, then it all piled up and I ended up adding the curved cocks and stuff just to ease my mind.

Oh and as for the worst of the bugs, the mysterious memory leak, I can only hope that it was related to something in Unity itself. I've updated to a newer version of the Unity Editor that has supposedly patched some memory leaks. Hopefully this is the root of the issue, but I honestly don't even know.

2016-09-25

Ass shapes and curved cocks

I've been ticking off more bugs this week. I fixed a few problems with Rembert scenes like an occasional loop and a dead link. I'm doing a pass over all of the story scenes to make sure that little errors are fixed. Part of it is having a good strategy for how links between rules are named. I've been working something new out for that.

On to Randos. So now Randos have generated ass shapes. Previously ass descriptions were kind of decided based on BMI and hip size. Now various factors go into setting which of ten or so ass shapes get assigned to a Rando. Frail Randos get bony and flat asses, super muscular types get muscular glutes, those with slimmer waists and wider hips get hourglass shaped asses, black women are more likely to get donks and badonks, etc. I think these are good things!

And Randos with cocks can now have cock curvature. My ~research~ into this tells me that it's actually a disorder to have a bent schlong. I don't plan on introducing any negative impact for curved ones though. If anything it should be a bonus. For now though there are just special descriptions for cocks that are curved up, down, left, or right. That's right, it's important to describe which way they bend!

I'm not quite ready for fingernail colors yet (sorry cubano :P). Makeup, facial hair and style in general will take a lot more thought before I can get them working. I don't even have matching underwear being generated yet, but these things are on my radar.

Finally I've been working on some content based on a suggestion from one of the Patreon folks (the only one actually :S). I think it's kind of helpful to break away from my normal priorities to bump up stuff that I otherwise wouldn't have gotten into yet. I'll keep this addition under wraps until it gets into the next release.

And speaking of releases, now that summer is over my dev pace has slowed down some. I think I'll shift towards monthly releases because otherwise I'm not feeling as if the week-to-week content is significant enough to warrant a full release. I'm aiming to release 3.9 before the end of the month. Actually that reminds me, there's 1 more thing to mention.

I've upped the compatibility number to 3 because I've done a large refactor of Rando descriptions which breaks previous game saves. The change was to make all of the descriptions of a Rando describe a generic partner instead. What happens is the Rando gets generated, all the stats of the rando are copied to a partner, and the partner is the one described in encounters. One benefit of this is that the state of a Rando is easier to track and change. For example, rather than magically knowing that a Rando is a virgin, it can just be a 'flag' that could be discovered in order to change descriptions. This addresses oddities like the MILF/DILF debacle. Most importantly though this change paves the way towards another big step, generating multiple partners.

2016-09-18

Preferences?

I've been ignoring the memory leak and chipping away at other issues with version 2.8. One interesting thing to talk about are some new branches to the robbery encounter. There is now a way to opt out of sex after you take the robber's gun. And it's also now possible to fail completely.

I've also given some thought to the preferences at the start of the game. My idea with the 'fuck/fucked by' preferences was to avoid sexual encounters that you cannot control. As a random example, say you get captured by a sorority and are forcibly fucked ~against your will~ by all of the sisters. I wanted there to be a way to prevent something like that without actually having to set it as a preference up front. Disabling the preference 'fucked by women' can exclude the scenario without having to get into the details of each potential crazy idea I come up with. But even then, that kind of encounter is an exception to the rule, since there should always be a choice that gets you out of an encounter. I forgot about that with the robbery scene, but the mistake made me more conscious of the importance of adding a way out.

Anyway, having preferences to prevent manly men Randos for example is actually kind of hard to do. The good news is that I think it's possible to expose a preference for hormone production that will alter generation in many ways. The way RandoEngine works, hormones have a ripple effect on many other stats in a Rando like masculinity and femininity, depravity, breast size, muscularity, cock size, etc. Boosting estrogen will increase 'girly' traits and raising androgen will bump up 'manly' traits. The preference will probably be something like:
  • female estrogen level: random, low, medium, high
  • female androgen level: random, low, medium, high
  • male estrogen level: random, low, medium, high
  • male androgen level: random, low, medium, high
In the long run, I'd like to make it a little more friendly for players to dive into RandoEngine source files and tinker with generation so that it produces exactly the kinds of Randos desired. Until then I'm open to any suggestions for things that deserve to be a preference.

2016-09-11

Leaky

So I'm dealing with a memory leak with FUBS that's been reported by a few people. The issue happens after the game runs for a while, and it can cause the memory taken up by the executable to balloon into gigabytes. I believe the problem happens on Windows and Mac, but I'm uncertain about Linux.

Honestly I'm struggling to find the root cause of the leak. FUBS is built with Unity and is coded in C#. C# is a memory managed language, meaning that the work of allocating and deleting objects isn't done manually by the coder, but instead it is handled automatically by a garbage collector at run time. Even though there is a hands off approach to memory, I believe problems can still happen with data types, object ownership, and other stuffs.

Up until now I haven't done any specific work with the performance of the game. I felt pretty safe in the fact that it's just a text game, and haven't given much thought to things beyond limits with text UI elements in Unity's UI system. There are some crazy things happening when the source of the game is loaded in, but that should only hiccup when loading happens. I've become too comfortable in my programming, thinking that I'd never have to deal with memory leaks. And sorting this issue out is taking up far more time than I'd like, so I'm a bit frustrated by it.

At this point I'll probably have to set the leak aside to focus on fixing bugs within the game logic, typos, and other things that have been pointed out. Coding feels like an amazing time sink in comparison to the stuff I'd like to be doing, like writing more scenes, tweaking Randos, etc. I suppose it's the cost of writing my own system, so I'll have to pay it.

2016-09-03

Fucked Up Burger Shack 2.8

This release only has some fixes for several issues. The biggest fix is for pronoun/gender mix ups. I really don't want to make that kind of mistake anymore, so I've written a little utility that should help me prevent them.

The other major fix has to do with text replacement which is used all over the place. I made a blog post way back when about how I was able to add this useful library called Humanizer to do mutations on text. In short it allows me to write something like this:

You talk dirty in the [^randoBabe]'s ear, explaining in great detail the things you like to do with [^randoSlur, plural] like her.

Which should output something like this:

You talk dirty in the super attractive babe's ear, explaining in great detail the things you like to do with drop dead gorgeous airheads like her.

That plural keyword does exactly what it says even with irregulars and such (I think). I enabled it along with a few other keywords that should really help with grammar and stuff. The goal is to eliminate the dreaded '!!Rule Not Found!!' error, but that is an ongoing struggle. Thanks to cubano for pointing me towards these issues!

Version 2.8
-General
--Changed death to off until more content is added.
--Fixed capitalization of a few instances of time of day, heat.
--Fixed replaced text not being capitalized at the beginning of sentences.
-Events
--Fixed a series of bad pronouns. I've setup some automation to prevent these kinds of errors because they really, really, really suck.
--Fixed improper spelling of "bukkake" as "bukakke".
--Fixed issue preventing a Rando scene start when prefFucksTransWomen.
-Randos
--Changed cum descriptions to align with having a cock/vagina.
--Fixed issue when describing thighs
--Fixed unnecessary commas when describing dumb, attractive randos.
-Fate
--Added text mutations for case: lower, sentence, title, upper
--Added text mutations for code transforming: camel, dehumanize, humanize, pascal
--Added text mutations for dashing: hyphenate, underscore
--Added text mutations for numbers: ordinal
--Added text mutations for plural: plural, singular

2016-09-01

Fucked Up Burger Shack 2.7


This update adds a much needed feature to Fucked Up Burger Shack, trans women! They will appear in each of the current random encounters and future ones too. I've been slowly refining the RandoEngine to enable Transsexuals. The main requirement was a separation of biological gender and gender identity. Then with a few tweaks to hormones the rest mostly falls into place. For now, trans women will always be pre-op. I've taken out the gender weighting so that you have an equal chance of finding men, women and transwomen. You can still set the option at the start of the game to block any mixture of genders so long as you keep one. (Gae will be upset if you don't) Or go into the source to weight the odds as you like. I'm stopping myself from turning this into a geeky post about awesomeness of RandoEngine, because that energy is better spent developing stuff.

I've also loosened the race restrictions to inject more diversity with Randos. There are a lot of missing details in regards to hair, makeup, clothes, etc. that are yet to be addressed. I will get to styles, tattoos, body hair, facial hair, fingernails, toenails, and many more things that will be fucking amazing, it's just a question of when. I did do a lot of cleanup work on Randos and hopefully haven't missed too many glaring inconsistencies. The next batch of Randos so to speak, will have ass shapes, breast shapes, and cock curvature. And speaking of cocks, I really want to do away with the inch implementation. Ahh here I go, getting into the Rando stuff.

There is a new random encounter that adds a touch of complexity to coupling with Randos. Randos now have several general interests that they like to talk about. In the encounter, you have to use the information you gather about the Rando to guess which topics will lead to more intimate conversation. Femme Randos like style and shopping, older Randos like news, rich Randos philanthropy, smart Randos like tech and science, etc. Randos also have a preference in flirting too; crass moves appeal to degenerates, friendly actions appeal to virginal types, etc. I see this as a basis for how dating will work later on. I can picture the player talking about these topics and getting more versed in them via experience points to help when courting.

I've added a skip button to each of the story scenes to avoid repeating the content after multiple play throughs. It hurts my soul a little, but I can understand the usefulness of jumping ahead.

Finally, I've gone over how money flows to make things a little ~better~. Purchases are now done with the bank account by default. That makes overdrafts a thing which will eventually matter. I may add in paying by cash for purchases or having an available setting for it. Of course cash needs to exist as a tangible thing that can be taken and such. Also illegal purchases will require cash, but that's not even close to being implemented yet.

A note on the version numbers. I can't remember if I've mentioned this, but I'm using a different version number scheme where the number on the right is the release number, and the number on the left is the compatibility number. All of my old test saves have broken completely in this update, so I'm bumping compatibility for this release. Albeit there isn’t much to save yet.

It has been a month now since I started blogging about and releasing demos of Fucked Up Burger Shack from my little corner of the internet. In that time, I've added a good amount of content to FUBS and I feel a little better about presenting it places. Big thanks to cubano for being literally the only person who has left feedback about the game so far. I don't know what specific thing I'm going to work on next, but in September I'll be continuing on the path of crafting the tale of the young man with the cursed, orgasm inducing cum. Burgers shall be tainted.

I've made a Patreon page in the hopes of getting support so that I can spend more than just my free time building FUBS. As I start this Patreon thing I intend to continue making FUBS at the pace that I have been, only placing a gap between the time that I release builds to theoretical Patreon supporters and when I release builds here. There are a handful of developers making adult text games who have had success with bringing their projects to Patreon this way. Then there are projects on Patreon that are/were pure money grabs, and also team projects that fall apart for a variety of reasons. I have no idea what the silent majority of visitors to this blog will think about me starting a Patreon, but I can say that if I can ditch my current job to focus on building FUBS instead... I'll be able to make the game much better, much faster.

Well that's my 'Advertise' for the day. You can grab Fucked Up Burger Shack 2.6 2.7 from the FUBS page. Fixed an unpleasant issue with source export, so this is now 2.7 :S

Version 2.7
--Fixed issue preventing source from exporting.

Version 2.6

-General
--Added ability to skip story scenes. (cries a little)
--Added action hub for gas station and food shop.
--Changed all payments to be done with bank account rather than cash.
--Changed cursed/orgasmic cum replacers to only work when player knows about cursed cum.
--Changed default bank withdraw amount to be bank balance, and default deposit amount to be cash held.
--Changed default credit payment amount to credit balance.
--Changed stat bars to use diamond caps.
--Changed visuals in the player.
--Changed wording in Restaurant Food Dealer Place Shop Emporium.
--Fixed bus hourly stats not resetting on a new day.
--Fixed credit payment to actually pay the amount entered instead of taking the payment and further increasing the debt by the same amount >_>.
--Fixed GivenName as a potential player first name (face palm).
--Fixed some missing stats for the stat bar when working under certain conditions (that's specific huh).
-Events
--Added a new Rando encounter. ༼ つ ◕_◕ ༽つ Gae's Pro Tips: this event is kind of rare to occur while the literal kinks are worked out.
--Fixed many issues with Rando bus tour.
--Fixed LAY 02 Text issue.
-Randos
--Added basics of hair generation.
--Added descriptions for bimbos, breast flesh, class, clothes source, depravity, femme, laugh, masc, milky nipples, mimbos, nipple, race based babes, rando (basically a generic 'man', 'woman' type output), relationship status, scent, sexual experience, smart, social skills, straight, taste, udders, uncut cock heads, wealth.
--Added generation of dominance.
--Added generation of education.
--Added generation of flirt type (friend,mate,partner).
--Added generation of general interests (7 of 14 possible).
--Added generation of relationship status.
--Added generation of sm.
--Added pregnant belly descriptors based on month pregnant, trimester.
--Added race, class and wealth variations for cock and pussy descriptions.
--Added special asshole descriptions for virgins with pussies.
--Added age variations for education level.
--Added transsexual women (bites lip).
--Changed age to promote more 18/19 year olds.
--Changed children count, sexual experience to prevent so many MILFs and DILFs.
--Changed crotch to holes, which describe 'asshole' or 'pussy & asshole'.
--Changed education level to ignore class.
--Changed genitals to describe cock/balls/pussy.
--Changed how muscles are generated.
--Changed how pregnancy status is generated.
--Changed masculinity, femininity weights.
--Changed Race probabilities to get some more diverse Randos.
--Changed religious devotion generation to not create so many religious people.
--Changed shoe to shoes.
--Changed skin color weights.
--Changed wealth values to be more flexible for all classes.
--Changed weights for encountering men, women, and trans women to equal chance.
--Fixed a few hormone production issues.
--Fixed BMI vs muscles issues with several descriptions.
--Fixed hasBreast limitation on nipple descriptors.
--Fixed lactation quantity to be based on being pregnant, having had kids, etc.
--Fixed missing African skin color generation.
--Fixed missing hasPussy constraints for descriptions.
--Fixed muscular Randos being described as fat.
--Fixed oddness with MILF and DILF to read as 'daddy you'd like to fuck', rather than 'daddy I'd like to fuck'.
--Fixed womb descriptions to respect having a pussy, and greatly expanded descriptions because fuck yeah.

2016-08-25

FUBS Demo 5

I was all over the place with this update. The main goal was to start adding in some problems for the player. Since money is the key stat in the game it has to be possible to lose it. I've started calculating average daily performance in order to get decent values when things have a cost. There are some gaps in the logic since you could game the system by lowering the average (ending the day without making any money). Figuring out those kinds of problems are less interesting than the challenges with Randos.

I've given some thought to how clothes can work with Randos. The massive amounts of variation in dress are intimidating, but I'm tackling the problem one step at a time like everything else. For now, Randos will be wearing very basic clothes without fabric, pattern, cut or color details for the most part. Some things that bug me: Men are all wearing undershirts even though that shouldn't always be the case; All women are wearing bras which I would greatly prefer to not be the case; depraved Randos are wearing underwear and other clothes, a true travesty; dresses and full body outfits don't exist yet. Currently the system is pumping out Rando clothes using rudimentary random selection, but it is a start.

Finally, some new characters appear under certain circumstances (theoretically). There are a few more left to introduce for the Burger Bus phase, then it's on to weaving tales with them.

    √ Added 18+ to starting option links for hell of it.
    √ Added ability to make purchases using credit.
    √ Added ability to rest and watch television at home.
    √ Added basic clothing to RandoEngine for lower, upper, shoe, lower under, upper under, and shoe under (sock, stockings).
    √ Added basic vignettes for advertise, clean, deposit, serve, and prep actions.
    √ Added better descriptions for balls.
    √ Added LOU 01.
    √ Added Robbery scene variations to fuck male/female Randos. Enabled the scene to appear when sauce a jar is available.
    √ Added several CC gender fallback responses because fuck it.
    √ Added several possible suggested 'common' first names in character creator.
    √ Added several possible suggested 'rare' last names in character creator to help story consistency.
    √ Added SKY 01.
    √ Added towing scene result for excessive power naps.
    √ Added web link to Bunkville blog on title screens.
    √ Changed Food sourcing costs to factor in average customers per day.
    √ Changed the price of fuel deliveries (doubled).
    √ Changed the price of gas to fluctuate daily. It caps at 2.50/5.00.
    √ Changed weather to update every six hours to prevent chaos.
    √ Fixed BBB typo (face palm).
    √ Fixed cock, balls, breasts, pussy descriptors to respect having them or not. Not having them should result in 'symbolic' cock for example.
    √ Fixed issue preventing death -_-.
    √ Fixed issue that applied sauce and cum money stats to regular served customers. That was not valid cum money.
    √ Fixed REM 03 event not closing properly.
    √ Fixed REM 03 missing stat bars.
    √ Fixed typo with weather calculations that prevented wetness and wind (face palm).
    √ Fixed visual oddity with save bookmark icon.

2016-08-21

FUBS Demo 4

Here are the details for this update:
Version 1.4
  • √ Added a variety of Rando descriptions for several different dimensions.
  • √ Added missing Rando descriptions for 'abs', 'chest and abs', 'cock and balls', 'cock head', 'crotch', 'cum', 'genitals', 'hair color', and 'pussy lips'.
  • √ Changed currency calculations to round in order to prevent decimal issues. This is a bandage for a bigger issue when working with currency in Fate.
  • √ Changed power nap tour to a chance event.
  • √ Changed text for Rembert event 2 to be more clear about timing.
  • √ Fixed declined power nap tour to prevent event from repeating for the day.
  • √ Fixed oddness when describing 18/19 year old mothers/fathers that you would like to fuck.
Since 1.4 is a hot fix for things brought up by cubano, I thought I'd try something different. Instead of doing the normal build process (which kind of sucks), I'm releasing this update with just the source code.

If you have FUBS installed all you have to do is delete the old source folder in the directory that you set for game files, and replace it with the source folder found in the extracted version 1.4 update folder.

If you don't have FUBS installed you can download it HERE and download the version 1.4 update below. When the game starts set the directory for game files to the Fucked Up Burger Shack folder within the extracted version 1.4 update.

If any of that is too confusing (likely all of it), you can just wait until I release the next full build, which should be in a week or so. I know this process isn't buttery smooth, but hey, this is a demo.

2016-08-19

FUBS Demo 3

Just finished uploading Fucked Up Burger Shack v1.3. This release is a little chunkier since it has been a week since the last update. Some things added: the first few scenes with Rembert, better work descriptions, a simple weather system, a new action to make extra jars of sauce, the basis of a new Robbery scene. I also fixed a bunch of issues all over the place but there are too many to keep track of right now. Hopefully 1.3 will be more stable all around.

I wrote some plans for where I'm going with Fucked Up Burger Shack. You can check it on the FUBS roadmap page HERE. In short I have a bunch of ideas that I'm going to be adding over time. A quick list:
    - employees and employee uniforms
    - fetish themed encounters via catering and other excuses
    - dating, relationships, and pregnancy
    - upgrading the business from truck, to drive-thru, to fine dining, to an outright brothel
    - and big goals like finding a solution to the family curse, crafting an ideal personalized restaurant, franchising the business, and leaving a great legacy.

I believe all of these things and more are possible given enough time and effort.

2016-08-12

Quick update note

 
I forgot to mention this but when updating to a new version of FUBS you will need to delete the previous source folder in the game directory, otherwise the game will use the existing source and seem to have not changed at all! This is a side effect of the way the system is built for modding. When it has a saved game files path, and finds the existing files, it loads them.

Streamlining this process isn't a high priority right now, but is is something I'm aware of. I'd also like to avoid writing any code that deletes files from people's computers if I can avoid it.

In other news I am in the process of writing the first story events for Mr. Rembert. Having a lawyer on your side will be super beneficial as the game progresses. One sticky issue (pun intended) is how to deal with adding characters of a particular gender that the player would rather not have relations with. For players who aren't interested in m/m content there has to be a platonic option with Rembert. The reverse is true with no m/f content players and the Layla character.

I'd like to remain inclusive for players, but I think only people who leave all options enabled will be 100% happy. So then, my target audience would be bisexual men?

Another idea is to just make male/female versions of each story character. It kind of kills my ideas for who the characters are, but it could be worth a try for a few select cases.

Last thing to note is I added a simple weather system that will eventually play a role in burger sales, customer clothing levels, and other nifty things. I could already tie this weather system into the sales formula, but I want to make sure the weather is stable before having it wreak havoc on business.

2016-08-11

FUBS Demo 2

I just finished uploading the second demo of Fucked Up Burger Shack. This one is version 1.2.

I added saving and loading. Game saves are created in the saves folder under the selected source directory. Each save stores all choices that were made so you could theoretically undo back to the very beginning, then redo forward. Not sure how well this will work since there is a strange bug in undo/redo that I need to find and squash.

I also did a lot of work on the random encounter. I was going through a lot of pain trying to use gender pronoun replacements. For example, saying '[$randoHe]' everywhere in place of 'he'. It made my life miserable so I decided to scrap the whole thing and make different identical rules for each gender with baked in pronouns. The random encounter is still buggy as hell, but it is at least playable enough to demonstrate the potential of it. I want to go much further with what actions are possible during sex and what kinds of NPCs you run into, but it's a start.

The changes to the business system that I mentioned last post are in this build. Plus, I made a fix for the issue preventing you from getting passed the first Layla story event (Facepalm). Thanks to cubano for pointing that out.

I welcome any feedback about the demo so far. I'm feeling better about the stability of things, but don't personally think FUBS is share worthy just yet.

Version 1.2
    √ Added game saving and loading.
    √ Added ability to skip past character options and intro
    √ Fixed display of some game metadata.
    √ Fixed issue where bold, italic couldn't be used together.
    √ Fixed several issues with the random NPC encounter.
    √ Changed Game toolbar.
    √ Changed the way profits and prep action work.

Download FUBS 1.2 Here

2016-08-09

Sales cleanup

FUBS Sales cleanup

I did a major overhaul of the business system. It now has hooks into several important factors that will affect sales later on, like weather, local competition, random events happening around the truck, employee uniforms, and yes employees. Of course all of those things are yet to be implemented. For now it does create different amounts of customers depending on the time of day as well as weekdays vs weekends.

I'm a little fearful that these changes my make the work aspect of the game too work like. This is one of those points where feedback would be helpful but I've gotten none so far. I wanted to hold off on posting about the demo anywhere until I got some feedback from people who stumble onto this blog, but that plan isn't working out so well.

Anyway, next up I'm going to build out the story with Rembert. I also need to make a platonic version of the Layla story and finish up her third scene. I noticed an odd bug with undo/redo but I'm holding off with that until later. I also have a few ideas for simplifying/enhancing the results of random NPC generation, but I might wait on that too.

2016-08-07

Saving and loading

I hacked saving/loading into the system kind of fast, so I need to spend some time testing before I release the next build.
FUBS game toolbar - saving

FUBS load screen

Even though it's only a demo the process of building, zipping, etc. takes a while. Looking at the screenshot I notice that the saves could be presented in a better order too :/

2016-08-05

FUBS Demo

A wise person once said, "either shit or get off the pot."

Well I've been on the pot for so long that it's left imprints where the sun don't shine. Or in other words this post is where I talk about the demo I've just put out for Fucked Up Burger Shack.

TLDR: The FUBS demo is only a demo, but it's downloadable! Things will break and seem horrible! You can mod it if you like but don't redistribute the game and stuff! I'll be focused on bugs for a while so post feedback if you are into that.

Content of the game:

So FUBS is basically a demo right now. The game will eventually have much more content, but for now I'm guessing it will only take a few minutes to consume it. I haven't written any code that deletes files, but still, I better just mention that this is an as is, at your own risk kind of thing.

The design is one part cyoa, one part business simulation. The content is meant to jump from simulation to story events or random encounter events depending on chance and things that the player has done. The third idea is exploration of different locations. You can travel home and to work right now, but eventually I want to expand to other places too.

Modding Why and How?:

At some point during the development of my text game system I came to the conclusion that exposing the source of a game for modding would be great. I wasn't thinking about the difficulty of actually building it, but now I'm so far in that I can't turn back. Of course it is possible to look at the html file that Twine outputs or break into the source code of other compiled games, but what I'm looking to do is encourage messing with the source of FUBS as part of the fun of playing. Maybe it's just the developer in me but I find changing character names, screwing with variables and text, or just editing save files really entertaining.

I have no idea how modding will work out for FUBS, but I do know that I'd like to avoid issues of ownership and the like. The recent collapse of Breeding Season is a good example of how to screw up a game with potential for everyone involved. I think one of the best examples of a moddable mainstream game would have to be Minecraft, so in the spirit of plagiarism I'm applying their 'One Major Rule' and other eula stuff to Fucked Up Burger Shack. The gist of it is 'you must not distribute anything we've made unless we specifically agree to it.' You own the things you write but I can use them in the game, ideally to make it much much better than what I can accomplish alone. That's the hope anyway.

So how does modding work?

When you start up FUBS you get a screen asking you where to store game files. FUBS should suggest a default location auto generated from your file system. YES IT CAN READ YOUR FILE SYSTEM, but I'm not doing anything shady. Or at least I'll point to an invisible privacy policy that I haven't written yet HERE. End Rant. You can accept that path or enter a new one, then FUBS will output the main source of the game into that path under '/Fucked Up Burger Shack/source'

The source directory contains a bunch of folders and .fate files. Each fate file is just a text file with the .fate extension, so you can open them up in any text editor to modify them. You can add, delete, and change these files and directories, but be careful deleting since that could mess up the game.

The writing format is inspired by the twee format used in Twine 1 but is not compatible past basic passages, links, and text.
The 'Start.fate' file and Start passage are the entry point of the game.
There are a bunch of specifics about how to write with the correct syntax so I am also including a rough document 'Fate Syntax.md' that roughly explains how things are supposed to work.

I'll also be making a post with how to make a custom event during the main game loop, but I'm probably getting way ahead of myself here. Again this is only a demo of the game so expect many problems.

With all of that said you can grab downloads on the game page HERE. Please post feedback here or send an email to p4p@ the name of my fictional universe .com

2016-08-01

Fucked Up Burger Shack

It's been a long while since my last post to this blog. My previous project Crooked failed spectacularly. If you check my last blog post it is pretty clear that I was on a steep decent into madness working on that game. But after some time off and a lot of reflection I've found that I really love making these games. It's an itch I have to scratch, so here I am.

I've spent countless hours this year rebuilding my little 'text game system that could', fate. Even now there is so much to be done with it, but I'm sick of toiling away in silence so I thought I'd show where I'm at with things.

I'm working on a project that I call Fucked Up Burger Shack. The game is a mix of business sim and text based smut. You play as a young man who has inherited a food truck business from a deceased uncle. The business is self sustaining due to the deceased uncle's secret sauce recipe. I hate to give things away, but lets just say that the secret to the sauce is freshly squeezed semen.

Still with me? Great.

So I started working on the project at the beginning of this year, then ran into the same brick walls that I did with Crooked. The old version of fate was very deeply broken and the only thing I could think to do was throw it away or start over. I made the tough choice to start over mostly from scratch. I looked into using different environments and languages like java or c++, but settled on Unity again. The majority of the system functions the same, but coded in a much better way (I think). I don't have all of the previous features working, but the stuff that I wanted the most ~works~.

The features of the game so far:
    male player character
    a random encounter with a randomly generated man or woman with a few sex options. (you can filter men/women in game or through modding)
    basic story introduction with a few linear story events that follow
    primitive food truck business simulation (it's really quite shit)
    modifiable game source using plain text files and a special format
    windows, mac, and linux builds

So I have a lot more to do with Fucked Up Burger Shack but the game is playable. I have a mountain of ideas and a lot of enthusiasm for where the game is headed. Releasing just a basic demo is an important milestone for me. I hope to have it ready to play in the coming days.