Is 1.13 going to be a reset?

Because this seems like a pretty big change to commands.

@minesy hmmmm... seems like it may... but it probably wont because it has been less then a year since the last..

No matter the time, some command blocks creations won't function anymore.
I think there will be a reset..

But let's look at the bright side of it for a second.
1.13 will ease some harsh server mechanics (that never work for my server, grr!) that are hard to implement in a multiplater world such as world structures, custom loot tables, custom achievement etch, they all will be stores in one unique folder called datapack.

Now let's look at the command blocks for a second.
The most of the commands will the slightly changed

• /clear
• /give
• /setblock
• /summon
• /toggle
• /scoreboard
• /testfor
• /tp

Etch.

So reset ftw

Also the structure of resourcepack folders will change, and 98% of the 1.13 textures are just horrible

We are monitoring the changes but these are just snapshots and as stated not final. Once something is ready to be launched we will look at everything.

Changes to the command blocks are currently being worked on and there will be a few changes to how these systems function, if some of these changes do go live. But we are not counting our chickens just yet.

Nysic

I heard that from your friend Mickey Joe Alpha talking with Danchuc on the PackPainters discord.
@3ddy
Or maybe it was someone else, I don't remember just right.

It was something about the models and blockdata I think

Since all of this seems to be focusing on performance and "backend" stuff relative to the players, a reset may not be necessary.

After the new release, we'll probably be in the 1.12 version for at least another month while the admins work to adapt and test the new commands, but after that it'd be an update to the new version then back to business as usual (def not trying to minimize the amount of effort needed to go into the recoding though).

Unless the admins want a reset specifically for a clean slate or something, I don't think a reset is absolutely critical.

@Valgys We'll probably be in the 1.12 version for at least a month while the admins work to adapt and test the new commands, but after that it'd be an update to the new version then back to business as usual (def not trying to minimize the amount of effort

Craftymynes's always been updated to the newest version, why not this time? And if so:
How can you work on something it's not even sure?
What if you change all command block inputs but then Mojang decides to change? Much rage
All we know's a leak of an update still in develoepment.

If not, Valgys's right

Wouldn't want a reset, spent too much time lmao

Personally I would prefer no reset, just rewriting the commands for the same map.

@OtherGreenGamer Personally I would prefer no reset, just rewriting the commands for the same map.

That would implement the server either down for mantainance or some clutch functions to not work (like tpa or rtp) during playtime for a while.

And starting from 0 is fun

@HaloNest That would implement the server either down for mantainance or some clutch functions to not work (like tpa or rtp) during playtime for a while.

And starting from 0 is fun

Incorrect. They could just keep in the same version and map for a while, and transfer all the commands over with structure blocks to the new version. Downtime would be small.

I'm not sure if structure blocks save command blocks though.

@OtherGreenGamer Incorrect. They could just keep in the same version and map for a while, and transfer all the commands over with structure blocks to the new version. Downtime would be small.

I'm not sure if structure blocks save command blocks though.

That's another option.

@Jams__ They Do.

They do now, what if they get corroupted or changed in any way?
Happened in the past to some custom maps, nothing sure, but take it in consideration