Minecraft: The Fat Suite V1.0.5

[The_Stranger]

Thank you for your input. I’m glad people are finally getting into the project and asking for more things to be added beyond Real Time Weight Gain, lol.

You also clearly appear to be passionate, which I love.

Let’s get into it:

---

@Ultranova

So in Starbound, there’s a compression ball (similar to the Morph Ball from Metroid) that allows you to shrink down into a 1x1 ball.

I actually did forget about this. To put this into perspective I really only played Starbound for the Big Fatties mod, so not a whole lot of it really stuck with me afterwards besides that, lol.

@Ultranova

My idea isn’t to add anything advanced like that, no, let’s say we could have a “compression item” that you could equip (maybe shield/offhand slot or even as armor) that compresses your size as long as you have it equipped.

Well, something like that is outside the purview of The Fat Suite, as I said before. I want it all to be completely client sided, and only using CPM for any functionality.

Though, that being said, in the post you’re responding to I pretty much suggested the same thing:

@The_Stranger

I just wish I could change the width with animations in real time with CPM so that by sneaking, or with a gesture someone could optionally lower the hitbox width so it could actually be playable while still allowing people if they wanted to to be restricted by the width and depth. I might actually put in an issue to the CPM GitHub so that maybe I could get this feature added for us.

…except obviously in the form of a gesture in CPM, or by sneaking instead of an item.

These solutions are client sided, completely optional, and Vanilla+ feeling things. (I mean, sneaking already decreases your height in vanilla). The only problem is I can’t do them with CPM yet. The reason why I elect to do it this way is because:

1. I am not a Java coder.
2. The reason why my models can change their width is because they only do so if you have Pekhui installed, which CPM has comparability for but if not then it’s only a soft requirement. So, for example, if you modeled something off of my Steve model in single player where you have Pekhui installed, then your width would be changed, but if you go onto a vanilla server with that model then it’s not like the model doesn’t work, it just don’t change the width like it did in Single Player.
3. Relying on other mods instead of coding it myself means updating is much, much, much faster. Day 1 these models were available for Fabric 1.19, and that is a point of pride for me.
4. Also, compatibility is a breeze.

@Ultranova

That’s a pretty advanced system, obviously, but it’s just an idea to show that there are workarounds to the obvious problem.

I know this, and like I said the only reason why I brought up my concerns is because currently the solution is impossible for the framework in which I’ve built the suite around. It could take months for this feature to get added into CPM, if at all. If it does not, I have some solutions in mind, but until it gets added it’s something I have to consider, which is why I brought it up as a concern I had in making bigger than Gigantic models.

@Ultranova

I really don’t think anyone whose goal it is to get that big is particularly worried about whether they’re going to be able to fit anywhere. Indeed, for some, that is the whole point.

Yes, but like I said a few posts ago: The purpose of this suite is to provide a more Vanilla+ approach to this, and by nature of that a solution for the width problem must not only exist, but be elegant and friendly with the vanilla game. Part of this is making sure that with any of my models you equip you are still able to beat the game, even when it’s combined with Pekhui.

@Ultranova

[T]he idea of having to carve out a house 200 blocks wide because you simply can’t fit anywhere else is extremely alluring.

I agree, but:

1. It was hyperbole. A model that big would actually be impossible not only in CPM but Minecraft itself without some intense labor, and Java skills. Singular models can only get so big before some problems start.
2. Even if it were possible, it would be extremely labor intensive just to model it, and texture it, and then at the end it would just look kind of silly when you moved. I have some cute ideas for sizes beyond gigantic and how they get around, but ultimately a size like 200 blocks is off the table for this project sadly.

@Ultranova

But in Minecraft, well, you have a theoretically infinite amount of space… why not use it?

Now we’re getting to the heart of the problem, and kind of the main idea here: Because at a certain point the game itself would be unplayable, and I personally would not want to put the insane amount of work involved to make a blob model, only for it just to be something that someone equips for a moment, and then goes out of because they literally can’t do anything in it.

Ultimately, even if that weren’t a problem, I enjoy the simplicity and the elegance of what I already have here, not only for me but for the player installing this as well, and if for whatever reason I’d have to sacrifice that to add something, I wouldn’t want to do it.

Does this mean I’d never do something that resembled a blob?.. No. It just means that whatever solution is put into place to make it possible has to be within the framework I’ve already built Gigantic from.

@Ultranova

[T]he “compression” idea gives you a catch-all solution that fixes most of the problems that would ever arise. Can’t fit? Go compressed mode and carve it out until you can.

I agree. That’s why later today I’m going to go ahead and put in an issue on CPM’s GitHub to allow me to change the Pekhui scaling variables with animations so that we all can be happy.

---

Hope this elucidated some stuff for you, @Ultranova!

---

Edit 1: Oh! I also forgot one reason the scaling is tricky: you can’t edit the hitbox’s shape, only it’s width, so as it gets wider and wider it gets less accurate for the upper-upper body like the head for example, making weird cases of it looking like you’re hitting invisible walls.
Edit 2: Ope, I’m really a scatterbrain, aren’t I? Another really important reason things are they way they are now is that The Fat Suite is ultimately a side project in comparison to my secret project.