There may be a way to, but I really don't have the motivation for that since it'll require creating entirely new maths to render the lines.
RoanneTheWolf
Creator of
Recent community posts
The main focus of the kink, I think, is juxtaposition. Big means nothing if there isn't small to go with it. Ludicrous only gets noticed when it's surrounded by otherwise normal. Gigantic tits are best suited for foxes of a tall, but otherwise average stature. Sometimes you need to, as a storywriter, shove some inconvenient details under the rug when nobody's looking, and other times, you need to point at the plothole directly, wave your magic wand, and make it disappear right before the reader's eyes.
There's a few representations and explanations for hyper as a concept, but the best ones tend to combine the right level of physics and rationality with complete and utter absurdity.
The research tab wouldn't have opened because only after Yuri's milked at a specific size do you get milk cells and unlock the tab. It may take another round of milking or three after buying the last cash upgrade to get there, but it won't take long.
I'm glad you understood my thought process in first making it cute, and only then making it horny. As for making games, I certainly don't have any formal education in programming. I got started hacking Twine games, then making twine games, and now I'm skipping Twine and moving straight to javascript and html.
If you did ever get the urge to start the way I did and just... make a lil minigame that makes a fox's boobs grow when you do something, Twine-Sugarcube is a good place to start. It's free, not too difficult to grasp the very basics, and it has a reasonable amount of potential (though this game did stretch the limits pretty well).
Big Yuri Best Yuri
There are two main issues with that. Number one, I'm not into it. I'm a degenerate of a very specific kind, and that kind wants a character to be hyper in only one aspect, to an extreme degree. Mixing multiple types of hyper on the same character dilutes the effect of each one, in my eyes.
Second, it's an exponential workload. Writing from 1 to 10 takes ten numbers, but writing every pair of two numbers from 1 to 10 takes a hundred. If I want to make the game have good quality, I'd need to write far more than would be necessary for the hyperspecialized games I make so far. If I don't write that much, and instead try to write two sets of ten, it loses detail and I'm forced to be more vague to account for a number of options in each line of text. My standards are higher than that.
I make things in various directions from time to time, including male hyper, but it takes a lot of dedication to turn some piddly little thought or single-page skinner box that I made on a whim into a proper game. Especially since I don't really want to be repetitive with the games I release.
I'm not much of an artist. I drew a fox once, drew boobs a few times, and that's all I've needed so far. The issue is that I can't use any external art because the only reason I can make the boobs wobble is because they're vector paths rather than just bitmap pixels.
If you check out my FurAffinity gallery (RoanneTheWolf, you have to have adult mode enabled) you can see the progression from badly-drawn-foxes to badly-drawn-but-bustier-foxes.
You have to click the booba themselves, which can have a slim profile when they're small. I've encountered some odd errors with some people on mobile, for that matter, even though onclick() should be relatively universal.
To test, if you click the +/- in the top right, the one that's highlighted should alternate. If they don't, it's not working.
The variables I'm using are double floating points, which have two parts: The significand, which is the number itself, and the exponent, which is the magnitude it's raised to, be it incredibly large or incredibly small. Precision is lost in incredibly large numbers, but that's not important in this kind of game.
However, a double floating point has a maximum value of around 1.78e308, or 178000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000. This is, for most purposes, large enough.
However, for incremental games and/or big titty fox games where an upper limit simply isn't a thing, it's a wall. Attempting to create a number above that limit will create "infinity" a value in javascript that can be used for some things, but there are places it breaks.
Specifically, the SVG code I plug the number into. That's not strictly javascript, and it has no handlers for infinity, so when I try to plug a string into a few 40 or 50 places where it expects a number, it throws an error, every frame. It also does not render the fox. So, I limit the volume at 1e300 or so (and in doing so, limit the length at 1e100).
There are a few solutions, but the best one by far is Break_Infinity.js, used by the Antimatter Dimensions incremental game to create some silly huge numbers by storing the exponent and significand in two separate floating points, allowing them to effectively raise the limit to 1e308e308. It's important to note that with those kinds of numbers, you can't just use javascript's inbuilt operators, they're not designed for that. You have to instead use custom operators, which can be troublesome, and even that doesn't solve the main problem:
You wouldn't be able to plug the numbers larger than 1e308 into the svg display. They'd have to be truncated or shrunk, but regardless, at that point nothing is being accomplished. The visual change is less than a millionth of a pixel.
What makes my games cute is the stories in them, because they paint to life the big titty foxes and make them more than just objects or placeholders. When you start to care, everything starts to matter just a little bit more- especially the booba.
1e308 inches is the diameter of the universe to the power of 11. That's plenty enough to tell a story, I think.
In order to edit or mod this game you'll want to download the thing and open it through the Twine app. Due to how Twine stores its saves, editing the save itself is ineffective (and saves barely work for this game anyways).
In order to properly save, you need to do so through the Settings menu, you can't just use the big "save" button on the left side.
Well dang, I'm really glad my game was worthy of that kind of analysis! There are admittedly a few different errors that can happen, and though it was resilient it was inevitable that something would break somewhere.
Incremental games are an excellent medium for breast expansion, but oddly nobody really... made any. So I decided to. It was a moment of inspiration lasting two weeks and a process of continuing to bother a discord server for playtests, and what came of it is really beautiful if I do say so myself.
Yuri best girl.
Yuri My Beloved's done, there may be a bugfix update in the future but I'm happy with where it is and don't think I can take it further. I'm on hiatus for this game, and college is kicking back up so I likely won't have time at all to do any of this in the near future.
I'm not done making big titty content by a long shot, but it may be a while before you see anything new.
It's probably possible, but you would need to have some very specific knowledge of how the SVG works- not to mention the original fox file. Giving some variation to the foxes is in the plan, actually, though it's been pushed down in favor of bugfixing the visuals.
While I'm passive towards hip/ass content, I much prefer hyperspecialization in what I make. A character with massive boobs and a massive ass is kind of just... middling, to me. Boobs no larger than the ass, ass no larger than the boobs. Those two are the only things I can focus on, so I lose the ability to consider the massive difference in scale between the fox herself and the tits.
You're free to take a crack at it, but it's going to be a long, painful journey. Especially if you don't know how bezier curves are made, both through javascript and through mathematics. I use actual calculus in a few places here.
I got my start in programming by hacking Twine games. This... is not really a Twine game anymore. You can give it a try, though I will warn you that if what you're trying to do is change how the visuals work, it will be a very tedious process in a tangle of an SVG. I could probably say more if I knew what you were going to suggest.
Not quite. Integer overflows are the error occurred from exceeding the maximum possible number, and if there was one it would break in more subtle and potentially much more disastrous ways. Besides, this isn't an integer, it's a floating point, which javascript clamps to a maximum value with the NaN check safely
I'm glad you liked it! I'd been disappointed by pretty much any other game out there for either setting their max size far too low or not actually describing anything at all and just spitting out a number.
And getting that image to work is tough. Both FurAffinity and Twitter image sources only work if you have an nsfw-enabled account. Here's my FA gallery where you can find the 3 fanarts (and several other, much lower quality self-made arts) and such.
https://www.furaffinity.net/gallery/roannethewolf/
Yeah, I'm not too into belly or butt. I respect them as fetish material, but they're just not my thing. I enjoy balls as well, but male hyper's not for everyone. My first two games were male hyper, though calling them games is a pretty huge stretch and they're not worthwhile if you're not into the subject matter.
I'm really glad you enjoyed them, though! I hope that whenever you're back in a boobin' mood you'll check out Grope That Fox or my FA gallery, both have some very nice visuals that the previous games lacked.
That's odd, nobody else has had a problem with that specifically. However, saving is buggy in that if you didn't go into the settings menu to save then the created save is pretty much empty. The password is Perchance, if you'd like to skip to it, and by uploading the .html file into Twine you can peek into the code and begin from any page (including the ending) if that's more your speed.
Yeah, you have to save from the Settings menu due to how I used Twine in an unorthodox manner. Basically, whenever you click "save", it only saves the state you were in at the last time you transitioned between passages- which only happens at the beginning, ending, and when you enter the settings menu. The password is Perchance.
Numbers can't really get bigger than that. Once you've exceeded javascript's bit limit, it'll return "infinite", which will turn into "Not a Number" as it's passed through the various processes and functions I'm using. Plugging a string into all of the calculations used to then generate the fox pretty much ruins everything, yes.
I'll add a failstate at some point for a proper ending, this was just a basic demo.