Spigot 1.13 | Veterancraft Dedicated Server | Forum

I had always suspected this, but never bothered to verify. Although SpigotMC publishes a 1.13 preview of Bukkit, it does not do the same for CraftBukkit. Since both of these are the basis of the Spigot-API and Spigot-Server, it appears impossible to compile a Spigot Server via public means.

This good/bad news affects VC as follows. We will be able to test compile all our plugins as far as Bukkit/Spigot-API compatibility is concerned, allowing us to identify, fix, and update to e compatible with the new API specifications. However, we will not be able to compile a full server, which we would have used to run functional tests and/or provide a preview-version that members can log onto and play.

I will try to communicate with md5 to see if we can either: 1) sign our lives away and under the penalty of death to get private access to 1.13 previews of CraftBukkit and the remainder of Spigot build files; or, 2) at least have him send us a compiled version of a 1.13 Spigot server that we can use for testing, and if allowed, for experimentation by members.

Good news. I was able to get our master plugin support library to compile with Bukkit 1.13. It only took a couple of tweaks and minor changes. Granted, just because it compiles, does not mean that it works. At this point we cannot run unit tests since our test framework is based on CraftBukkit, for which no preview edition exists. Still, it is a good feeling to have some validation of the pre-1.13 work we did over the past few months.

Still no pre-release or release of Spigot 1.13. I doubt it will be available before 7/18; though I expect that a pre-release will be available shortly thereafter.

vyscaryska said
Good to see you've really hit the ground running on this 1.13 thing. My only question involves the current test server. Will we still be able to move our collected materials to Arda?

 

Short answer, yes. Keep in mind that things are subject to change; my current thinking is that the 1.12 test server world will still become a secondary world for Arda; albeit, it will only have 1.12 blocks and items. The 1.13 test server world will become the new OR or SR, depending on which one we current have running (been a while). In essence, Arda will have two active secondary worlds. Actually, it will have three active secondary worlds, since we always keep the old one up for another 30 days. Given the interest by members playing elsewhere for now, we will probably keep it around longer, to ensure that they can get their stuff from that world too.

Concerning the metadata change for every single item, I recently started casually playing on a different server that has had the unusual property of being up for seven years but never having a map reset. Consequently, this map has existed through every single major patch and bug change and hotfix that minecraft has ever had. So, you have some things like "alpha leaves", which are functionally a block which no longer exists in current minecraft, but still exists in game for these players because their map has never reset. The texture is the purple and black block that exists now which is the textureless version of any block in minecraft. 1.13 will remove these blocks from the game because any leaves will simply become their 1.13 equivalent. Fun fact, that server's memory is measured in terabytes, and costs thousands of dollars a month to host.

Seven years would be enough time to collect a lot of odd blocks. I am surprised that they did not convert them. We had a similar issue when we switched from Vetronia to Arda. Various leaves and sandstone block ids did not convert, requiring us to parse each world and change them ourselves. Since this did not fix items in inventory, we also defined a few custom recipes letting members convert their stash of older blocks.

Given the pervasive change in block ids, it will be interesting to see what the 1.13 upgrade will do. Spigot's Bukkit 1.13 API still provisions ids for older blocks, appropriately named such as LEGACY_WATER, LEGACY_FENCE, etc. We do intend to test the extensiveness of world updates and make any id changes deemed necessary.

Wow, TB memory -- drool, drool. Just for S&G's I checked with our data center, we could update any one of our three servers from 6/12-core, 64 GB to 24/48 core and 512 GB for an additional $600, each. They must be running multiple instances or VMs. A single Minecraft or Spgiot instance handling that many players to justify TB memory would just crawl

What is the name of server, I would be interested to check them out more. Maybe we can learn something from them.

A quick update. We have been going balls to the wall getting everything ready for a pre-release of 1.13. Most of the VC plugins have been updates to support 1.13. Some require further tuning, but that can be done later on. Currently, we are review our 3rd-party plugins (e.g. LogBlock, mcMMO, GriefPrevention, etc.). This has been a bit of a challenge as most of them have not yet been updated.

We are going through each one of them to see how they react under 1.13. This is a very painstaking tasks. Of particular note is that PermissionsEx has no maintainer and will not be updated. The question we need to answer is whether we bring PermissionsEx in-house or switch to an active permissions plugin such as LuckyPerms. Either way, it is more work.

If things go well, we should be pushing out a 1.13-pre7 test server out sometime tomorrow. Please note, you will have to use the 1.13-pre7 client, not the 1.13 client, to connect to it.

Anyways, just throwing out a quick status update for those that were wondering what was going on -- back to the grind.

Another quick update. As mentioned previously, we are examining our third-party plugins as to their 1.13 "readiness." As suspected, some are moving forward and many have not yet. Likewise, some have tweaked versions that work "good enough" on Spigot's 1.13 community server.

Since our goal is to get a 1.13-pre7 server up and running in order to test our plugins, we cannot wait for the those to update. Those that are mostly unaffected or only require minor tweaks, we update ourselves and contribute the code back to their authors; hopefully helping them along a bit.

The show stopper at this point is GriefPrevention. While it works "good enough" with 1.13, it does not cover all item changes. We believe that GP is important enough to have at the onset and we have been working on its update so far. Once that is done, we will put together a test server configuration ready for members to explore.

As we have are deep diving into GP, we have realized that some of our own plugins may need some additional changes. If deemed important, they are updated immediately; otherwise, the issue(s) is added to our tracker and scheduled to be solved at a later point in time.

On a side note, normally LWK spends a considerable amount of time finding a good seed for our secondary worlds to ensure that the world includes all interesting features within reasonable proximity. Unfortunately, the Amidst application he uses currently crashes when trying to render 1.13 worlds. If anyone has found any good seeds playing with 1.13 or its previews, feel free to mention them. If not, we will just wing it. After all, this is a pre-release and nothing is cast in stone.

Trip6s6i6x said
Was reading the patch notes for 1.13 and noticed this:

"When editing an existing Minecraft world, there is now a new "Optimize World" button, allowing you to update old worlds to a newer format."

I know when we update, usually the new mobs and stuff seem to spawn in automatically (unless you're changing things in the background that we're not seeing in order to allow it lol), but thought this might be worth looking into in regard to future updates as well. From the sound of things, having to recreate worlds to add new blocks may no longer be necessary maybe? (unless I'm reading that Optimize World thing wrong?)

Oh, really! I did not see that. Is that a single player feature? You are right, we will definitely have to look into that. That is not to say we would abandon the secondary world concepts, since they would still be useful as resource worlds without staff having to deal with aggressive plumbing and mining of the main world.

LWK, can you put that on you Things To Do list and flag me when we get close to a full conversion?

We did intend to test various update techniques on Arda to see what type of effect they would have, but if Minecraft itself can do that, it would be a wonderful time saver.

Greeting all,

This is just a quick post to let everyone know that my heart is still beating. I had promised LWK to post a more detailed update last week, but in normal form, I was side-tracked by other issues.

In short, we (Mudwog and I) are working on two key tasks: 1) getting Shoppe ready for prime time; and, 2) getting an Arda ready for an update once (1) is ready.

Currently, I am heads deep in Spigot item metadata structures and fixing a few bugs therein. The work done therewith is crucial not only for Shoppe, but also other item/inventory related tasks. However, rather than writing our own fix, these issues are at the core of Spigot and require changes to it.

Unfortunately, the default Spigot build environment is not playing well with creating such fixes and changes that can be properly submitted to Spigot as pull requests. Thus, I am working on documenting the process and fixing/augmenting Spigot's BuildTools to make this problem go away and provide information for those occasions, since time will erode my memory of the details with other stuff. I hope that by the end of the week, I can get back on track to working on Shoppe.