Just a quick update here: My existing Patrons won't be charged for the upcoming month. I don't really like charging others when there isn't much releases out yet, regardless of how much work I've been doing in said month. As an user, I'd definitely hate having to pay for more when I haven't received much yet currently, so I can see the sentiment in that. There'll also be a massive Dev Update coming tomorrow for Patrons as well.
For everyone else: I'll be releasing another demo on Discord today - hopefully this is the finalized version for one of the new things coming in the 1.21 Update Series. It'll be quite interesting to say the least. See you soon!
A demo for one of the things coming in the 1.21 Update Series have been announced at Discord! Do try it out and let me know what you think over there.
Also, a quick note: If you're trying to contact me via Discord and DMs aren't working, the most reliable way to get it working right now is to join any servers I'm a part of, which will then fix it for you. I don't think you can wire it so that you'd accept DMs from anyone anymore? That'll have to be the workaround for the time being. I'll get a custom email thing if you want to reach me directly in the future, but for now, if you need to contact me personally for anything, you can reach me either via Discord or the Mail system PMC has set up.
1.21 is out! It's currently close to midnight where I'm at so I'll show you what I've been working on tomorrow. Just to set some expectations beforehand: The Update Series isn't done yet - I still have lots of things I wanted to do for this update that I haven't yet finished. I'm trying my best with the limited amount of free time I have though. See you soon!
Even when I try not to overpromise things, I still ended up promising way more than I thought I did at the time. I'll still make it happen though, it'll just take a while.
In the meantime, here's a slight tangent: Boy, do I love services that give you a 50% off deal when they realize you're not using their services anymore. I haven't paid them anything yet, and now that this deal's out, I won't be using them at all, since they had the audacity to inflate their prices to seem premium, rather than being honest about the value they're offering.
(I was experimenting with some website builders until I figured that it would be much better if I did it myself rather than rely on these kinds of things)
It's my birthday today and I realized something: I got enough time to bring some packs to 1.20.5, but not all of them. So, I've decided that since I won't be able to bring all my releases to 1.20.5 in time anyway, I'll be working towards getting them all ready for 1.21 instead, which is coming in about 2 weeks from now.
What does this mean?
You'd get all the features I announced (even the ones previously delayed), plus all the secret features I have yet to show (designed specifically for 1.21) as soon as possible after 1.21's release.
I'd get more time making sure the Update Series is the best it can be before it's out there.
It does mean you'd have to wait for it a bit longer, but late is just a little while. I could try to force it out the door, but that's not who I wanted to be, and I wouldn't want to use anything coming from someone like that anyway.
Thank you for reading all this. I'll head back to work now. More news soon!
I predicted a June release for 1.21 and a possibility that it'll come as I'm working on the 1.20.5 Update Series. I mean, it has to be out by June so Minecon may come with news for 1.22. And the Prereleases are here to confirm my little theories.
Here's a little response to that: I'll get my projects to 1.20.5/6 first, then to 1.21. The jump from 1.20.5 to 1.21, relatively speaking, is smaller than the jump from 1.20.4 to 1.20.5, so that won't take as much time in the oven as it would be for the 1.20.5 Update Series.
However, with the new features 1.21 is bringing, all fully realized, some of my packs will be designed much differently to adapt to the changing scene.
Made a hard decision today to not do something I was going to add alongside the 1.20.5 Update Series, and saving it for a later version. I find the idea to be a pretty good one, and I'll get to it eventually, but the main problem with going for it now is that it's going to take way too long to complete for a side improvement, and I want to mess around with the new stuff in 1.20.5 as much as you are. I'll talk more about the removal on Patreon in the next few days.
As for the update plan: I'll be updating each pack individually and release them when they're ready, so you'll get them as soon as possible (plus about 2 weeks for Early Access - which would be free if I don't need money to live, but ... life). Some packs have new features to come with them, and all packs' descriptions are going to be overhauled, but I'll let you know more about the new stuff and changes in particular later on.
PS: whenever I mentioned 1.20.5 I also meant 1.20.6 too, it's just that 1.20.6 is just 1.20.5 with a bugfix that won't affect my projects like, at all.
Also, yes, I'm still working on the Update Series - that's the biggest priority on the list right now. But I still want to keep you guys posted just so you know I'm not like, gone or anything.
Kinda ironic that 1.21 is the release that's going to make what I'm adding with 521 a lot less interesting ... The feature that caused it is a good change, I just find it to be a bit ... ironic.
Just learned today that if you haven't migrated to Microsoft from a historical Mojang account, your account is permanently deleted and you have to buy the game again. Even if you have the receipt of the original purchase.
Heck, to this day you can still migrate your old YouTube account for free. 17 years after YouTube's acquisition to Google, that deal held on.
I'd still make the comparison if it is since the point is still there. It's probably even worse for Microsoft if that's actually the case, regardless of if the YouTube migration deal is still held.
Another random piece of trivia: The file containing the things I need to know in order to port any given project to 1.20.5 is around 200 lines long, and counting! As a reference point, the same file with the things I need to know in order to port from 1.20.2 to 1.20.3 is only around 30. (the count is 27 if you were wondering)
Bit of context here: For every new release, I used a self-made tool called the "Patch Notes Grabber" to get information off a given update log, or a series of snapshots leading to a big update and merges all that into one mega update log (if the update log itself isn't out yet), then carefully sort through the resulting data for the stuff I need to pay attention to in order to bring a project to a given release.
It's standard practice for me now, but I never really talked about it since it's more of the boring bits, but I still need to let you know I'm still bringing this to 1.20.5, this'll just take a while for me.
I'm starting to think that this bug is on its track to becoming the 2nd Damage Wobble bug. It was a thing once, got removed, then many years later was re-implemented again and felt like a new feature. (Technically this one was never a thing, but alternatives existed that did the same thing - all of which were removed instead)
If 1.21 is released without this bugfix I'll look for another path to bring back "/nameless" to Villager Names myself. (Hopefully there'll be another way around it by then)
3 days later, I got a brand new tool out of it. This'll help me shave off a ton of time posting stuff (and managing them) across multiple platforms. look, building a parser from scratch is tough beans, alright?
Decided to speedrun HTML and CSS in 4 hours - I'll need them for future update shenanigans. Just the basics of them anyway, I can always improve it later on.
One of the things I'm implementing in this update asides from a full system rewrite is a new way to customize my datapacks! This is an idea I had back when we got 1.20.2, but it took me up until now to finally be able to implement it system-wide. I have to rewrite the system anyway, so might as well. (Note: by "system" here I mean all the packs I've made since 1.20 and am currently updating)
Yes, Version 20d1 (coming soon) will be designed for both 1.20.5 and 1.20.6, given the features we've seen in that release so far. It's exactly the same deal as it was in 1.20.4.
TheShadyy
Space Wars trial version (not everything works)Minecraft 1.15 Aesthetic Mod2.3k 146 2x 3
KavDev Studio
•8/29/20 12:00
PMC
Tommy Crime Empire Boss Tommy