I'll be seeing "Where's 1.20.5" comments soon. When that comes, I'll save a link to this post as a response so I don't have to copy and paste the same post over and over again. Here goes: I manage 20 projects currently. Short version: It takes time. (Progress updates on Discord) Long version: My updates take time to complete as I properly go through each of them to see which features I'd need to improve to match the current version's meta, if there is any. I'm also using latest techniques available on the version I'm designing it for to make sure my packs are the best they can be on release, and it takes time to discover what these new techniques are. My datapack creator tool Scripter helps, but like any tool, it needs a person to be used to make stuff with.
Bit of a long default response, but the recap is the same across all my releases.
Good news, the Creator Analytics update is ready but the bad news is the timing isn't right to launch. I have some IRL things happening that require my undivided attention. All good things though, so no worries there. It's just best to wait until things are settled so that I can return the same attention to the update and you.
Creator Analytics WILL release next month! It took longer than initially expected for a number of unexpected reasons but scope of work also grew in many directions for the best. There's always more to do after the launch but there's more than enough to be useful and fun now and into the foreseeable future and historical past interests. Always nice when things motivate you to go, go, go. Didn't help switching chart libraries last week but know it was the right decision for the short and long run.
You'll see soon and I'm looking forward to having the proper time to respond to bugs and feature requests.
A small comment on the massive changes 1.20.5 is bringing to the table and it's massive effects to datapacks and custom maps as a whole:
I think the hardest thing with making the ideas I wanted to make happen into a datapack is that a lot of the times it's really really hard to do so efficiently, and some other times, Mojang would step in and mess with your stuff, and without the reach needed to overrule the thing they've irreversibly changed, you kinda just have to live with the storm.
It's understandable if because of that or any other reason, creators would prefer mods over datapacks since they can do what they want on a version they choose to do it at (basically removing Mojang's effect on things, at least partially, if you've read some of my secret Patreon dev posts), and if they choose to do so, we should still support them for it, because at the end of all this, they've spent the hours that could've been spent in other ventures that'll most likely give them way more money, to make sure you get the best things possible, in the best way that they can. (Wait, I've been making datapacks for 5 years? Time flies, man.) As for me? I'll just live with the storm and do my best to make sure all my projects I've made in the 1.20x series get a proper update to 1.20.5. I personally find the storm to be a challenge, a problem that I'm slowly overcoming with Scripter - which, in a way, is like the hand-crafted ship I'd built to weather this storm. But also because I wanted to experience the latest stuff the game has to offer with the tweaks that I've personally made to enhance the game the way I find fun to play.
But anyways, enough of that, the updates are coming. I'll leave update details on Discord if you wanted to check those out.
You honestly thought I was also moving to mods, don't ya? Reply to this one if you think I was about to say something like that at any point in the post.
I know that technically a datapack can stay at a given release too, but unlike mods, datapacks are more reliant on the tools that Mojang provides in each new release. So something I wanted to make back in 1.13 for example, can't really be made efficiently until way later on. It's kinda why I have a long list of old ideas. I just kept them all, even when I know it's not doable, so when it is, I can start messing with it.
At some point I'll make it possible so everyone could quickly make packs with my custom datapack creator Scripter. I'm not confident with showing the tool as it is now, as it was only built to suit my weird style, so it likely won't help anyone as it is. But someday, when I have a lot more time to spend on datapack shenanigans, I'll work on a version that can be used by a more diverse set of people, and release it by then.
Anywho, 1.20.5 is coming. Working on upgrading all my projects, more news in the Discord Server. See you soon!
this is your one reminder to make sure that your monitor refresh rate is set to the correct value
mine was on the default for a very long time and i just realised ive been living with a default refresh rate even though this monitor supports more than that
Gee, I wonder what's the average time on how long it would take for an Important bug to be fixed. I got this bug marked as Important in 1.20.4 when I realized that it broke a Villager Names feature in a way that can't really be worked around efficiently, even with the new stuff available in 1.20.5, and somehow it survived the full 1.20.5 snapshot cycle without even being noticed.
Anywho, if you're wondering why the workaround still exists in Villager Names 1.20.5, this is why. I'll leave a note in the pack's Update Log by then as well.
My guess would be several years… [that's using my definition of important bug which ignores all the "Misspelled name in credits" & "Fixed bad pixel in X model" padding…]
Time for a discussion: I think the Datapacks section in PlanetMinecraft field should be split into 2 categories: Datapacks and Modded Datapacks.
Modded Datapacks are datapacks designed to work for a particular mod or a modpack. (requires the mod/modpack's link in the download as well, kinda like required resource packs)
Datapacks are for packs designed for Vanilla Minecraft.
I think that when datapacks are mentioned people mostly mean vanilla datapacks anyway, so that's why I think the term "Datapacks" should be for packs designed in Vanilla. Anyways, let me know what you think!
I don't really think another category would do in this case.
Categories are often used to split up the different branches of the same big tree. But modded datapacks and vanilla datapacks are their own separate trees altogether - even though they are both trees (tree in this case being a datapack), they work on different environments which most of the time isn't compatible with eachother (a modded datapack might modify something vanilla itself doesn't have, for example), and hence can't be considered branches of the same tree.
From an user experience point of view: If you're someone who has no idea about the technical things that can be done by vanilla datapacks, you'd assume modded datapacks and vanilla datapacks as one and the same (since they're both categorized as "datapacks" at first based on the site's current design), only to then install a modded datapack in vanilla and be confused about why it doesn't work, or vice versa.
Splitting it into two categories would be a bit much, instead we could theoretically add a checkbox for something like “Requires a mod” and they could filter out those that do.
I'm none too clear on the lines between texture packs / data packs / resource packs / mods so some clarification wight be a good place to start…
Assuming I correctly understand what you mean, having at least a filter setting for those that require additional software (Optifine seems to be a commonly sited example) would make sense. Whether an entirely seperate subfora is needed is more debatable as there may be those who prefer having only one place through which to search. [Which again brings up the issue of overlap between various sorts of game modifying 'things'.]
Bye the bye, this probably shoud be filled as a suggestion ticket if you find any reasonable level of support…
I hate planned obsolescence. Why intentionally make your products bad after a few years of use? Sure, you'd get more trades doing that, and more trades means more money, but it comes at a cost of screwing everyone over.
PS: I said this because my new mouse broke after a year of use, and I had an older mouse that lasted for 5 years before this. I can see why some people would hoard old stuff in boxes and just use that - I mean I would if it means I don't have to waste valuable time in buying a new mouse every year.
After a roller coaster ride of locating, merging, migrating and auditing massive amounts of data (nearly a billion records), I'm back on crossing off front-end features until remaining tasks are down to launch preparation. The bulk of the work is done, last 10% requires pushing through and eventually leaving some ideas for post launch.
Just going to drop several work in progress screenshots from various analytics sub-pages and let them do the talking:
![The Original Bracken Pack: Adds Eleven Dimensions! [1.20.4] Minecraft Data Pack](https://static.planetminecraft.com/files/image/minecraft/data-pack/2020/280/13791790-thumbnail_m.jpg)
Brackenstrike
4/13/24 2:45
• posted 7/9/20 2:51
![Shadowlands - new dimensions, bosses and more! [1.20.1] [1.20.4] Minecraft Mod](https://static.planetminecraft.com/files/image/minecraft/mod/2024/616/17596506-background_m.jpg)
![Infinite Abyss [New underground dimensions] [1.16.5] [1.18.2] [1.19.2] [1.20.1] Minecraft Mod](https://static.planetminecraft.com/files/image/minecraft/mod/2022/236/16097222-logotest_m.jpg)
smok564