Spigot 1.13 | Veterancraft Dedicated Server | Forum

A A A

Please consider registering
guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 4 characters - maximum search word length is 84 characters

sp_Feed Topic RSS dirt
Spigot 1.13
Topic Rating: 0 (0 votes) 
July 10, 2018
10:16 pm
frelling
Senior Tech
Forum Posts: 3232
Member Since:
August 18, 2011
sp_UserOfflineSmall Offline

There is a lot to be said, but for now, I want to keep it short. Spigot 1.13 will contain significant changes. Not only for new features, but also how items, blocks, and entities are handled. While this was not new news, we underestimated the depth and impact of these changes. With 1.13 supposedly slated for release toward the end of July, we are shifting our focus away from a 1.12 upgrade and moving directly to 1.13.

I realize that this may cause more questions than those answered. Just keep in mind that we can do almost anything in regards as to what items, builds, etc. survive and/or make it into Arda. However, at the moment we are focused on more basic issues.

We need to get a 1.13 development server built on which we can test all our plugins. This is something that we are not very familiar with. Previously, we have always worked with pre-releases and releases, not previews. We are hoping that the mechanics are similar and that we will also be able to publish a preview version of Spigot for members to test, not unlike the current 1.12 test world.

However, it must be understood, that unlike releases, previews are subject to change without notice and not having the necessary preparations in place could cause additional work on our part – something we would like to avoid.

There are several external factors that are competing for my attention. Although I have recovered from a recent injury to my forearm that limited my ability to use a keyboard effectively – I have gotten good at one-handed typing to send emails, but I did not realize how much I used a mouse until I could not. Depending on certain actions over the next few weeks, I may also turn in my notice at work to pursue another endeavor. However, I will save those details for another time.

Human beings, who are almost unique in having the ability to learn from the experiences of others, are also remarkable for their disinclination to do so. - D. Adams
July 12, 2018
9:18 pm
frelling
Senior Tech
Forum Posts: 3232
Member Since:
August 18, 2011
sp_UserOfflineSmall Offline

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.

Human beings, who are almost unique in having the ability to learn from the experiences of others, are also remarkable for their disinclination to do so. - D. Adams
July 12, 2018
11:10 pm
frelling
Senior Tech
Forum Posts: 3232
Member Since:
August 18, 2011
sp_UserOfflineSmall Offline

I just read a text from LWK informing me that Mojang will be releasing 1.13 on July 18, which would be in a little less than a week. Given that, we will nix the notion of trying to get a preview up before that and just focus on getting our plugins ready by compiling against the preview version of Bukkit 1.13.

This time around, we will make an attempt to be as bleeding edge as possible. As soon as Spigot pre-/releases a 1.13 version, we will deploy another test server. The existing 1.12 test server will continue to remain for regular use. I would like to caution that the 1.13 test server may be unstable. While members are encouraged to test and play with new features do not go overboard on your builds unless you can tolerate rollbacks or even wipes. I am not saying that such will happen, but it could happen.

We will use the 1.13 test server to deploy 3rd-party and VC plugins as they become ready. Most VC plugins should be ready, but a week is a lot of time for things to go pear-shaped.

At this point, we are not concerned with Shillings, claim blocks, items, and inventory. Our foremost and most important priority is to get all our plugins working well, 3rd-party plugins installed or replaced as needed. Without those, all other things are not worth considering.

As I mentioned in a post a few days ago, as far as currency, items, etc. we can do most anything, and chances are that we will be as accommodating as possible. So, for now, please hold off on any 1.13 questions unless they are related to game mechanics, plugins, and features. Thank you in advanced for keeping to the immediate topic.

While speaking of plugins; the most significant change in 1.13 is how Minecraft identifies items and blocks. Up till now, this has been handled by a tuple consisting of a material number (Block Id) and a damage value (DV). The latter used to select between different types or variants of the same block type (e.g. Oak Sapling, Birch Sapling, etc.).

Mojang has deprecated the use of these tuples in favorite of string identifiers. For example, instead of using (6,0) to represent an Oak Sapling, the will just use

oak_sapling

; similarly, (6,2) representing a Birch Sapling is replaced with

birch_sapling

. Metadata associated with potions, effects, and enchantments will continue to work in the same fashion, though some of the identifiers used by them may also be changed to text strings instead of numerical data.

The point of mentioning these (excessive) details, is that plugins relying heavily on ids and DV will have to be updated. This change is not late breaking news, so most plugins devs are prepared and have done as much as possible; however, those that have not will find themselves scrambling (hopefully) to put out a 1.13 version.

The 3rd-party plugins we use that rely heavily on Id/DV are DynMap, GriefPrevention, LogBlocks, mcMMO, and WorldEdit. VC plugins that depend on Id/DV are Alchemist, Diver, OpenBlocks, and Shoppes. Obviously, we expect that these will be updated before the release. Shoppes may take a little longer since we have to rework its item information storage system that we had tried to make 1.12 and 1.13 compatible. It should not be rocket science, but it is pervasive, increasing the likelihood of unwanted bugs.

Human beings, who are almost unique in having the ability to learn from the experiences of others, are also remarkable for their disinclination to do so. - D. Adams
July 14, 2018
1:09 pm
frelling
Senior Tech
Forum Posts: 3232
Member Since:
August 18, 2011
sp_UserOfflineSmall Offline

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.

Human beings, who are almost unique in having the ability to learn from the experiences of others, are also remarkable for their disinclination to do so. - D. Adams
July 14, 2018
10:43 pm
vyscaryska
Member
Members
Forum Posts: 38
Member Since:
June 22, 2014
sp_UserOfflineSmall Offline

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?

 

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.

July 15, 2018
8:36 pm
frelling
Senior Tech
Forum Posts: 3232
Member Since:
August 18, 2011
sp_UserOfflineSmall Offline

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.

Human beings, who are almost unique in having the ability to learn from the experiences of others, are also remarkable for their disinclination to do so. - D. Adams
July 15, 2018
8:53 pm
frelling
Senior Tech
Forum Posts: 3232
Member Since:
August 18, 2011
sp_UserOfflineSmall Offline

I got so absorbed in my previous reply that I forgot to mention that SpigotMC has released official pre-releases of 1.13, meaning that we can do full testing. Unfortunately, I am going to be out of town tomorrow on business; I will see what I can do from the hotel room.

Human beings, who are almost unique in having the ability to learn from the experiences of others, are also remarkable for their disinclination to do so. - D. Adams
Forum Timezone: America/New_York

Most Users Ever Online: 117

Currently Online:
12 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

Emulated: 3206

ryanpitts: 1300

Dalferes: 746

Pherian: 660

Okarim: 590

Member Stats:

Guest Posters: 10

Members: 1947

Moderators: 3

Admins: 2

Forum Stats:

Groups: 8

Forums: 45

Topics: 6215

Posts: 27283

Newest Members: ladonnauf18, bradleyzr1, jordanzr69, geraldineue69, Greogysealk, EROdonopay, DrongDib, BeverlyRot, SuzanneSak, Aisfelub, AbakbakoGex, ElyaLelia, Rebecajew, Mshertyuptex, Annated, JamesFlack, Rosejy, panlillita, Michaelelone, TheRealRedCakes

Moderators: terrorisly: 424, mudwog: 127, LightWarriorK: 2117

Administrators: meatbawllz: 2475, frelling: 3232