Search results

No plans to phase it out, any more than I'll be phasing out support for the Technic packages or describing the custom deploy using the vanilla launcher.... essentially zero cost to keep it going, and (as I hit in this case), sometimes one works for folks while another doesn't.

@Dan_Prime I'm hitting a problem with the new launcher on the current 1.12.2 test client, as far as updating. I'm not sure if I goofed up something in the json for it - could you give it a peek, if you have a chance? Is the Windows version updating successfully to the current 1.12.2 test...

I love the Chronicle Entry idea - and it made me think of another feature: would you guys be interested if I added an option on Dynmap to be able to easily define a link with parameters that specify a marker name (in this case, specific to the markers for the warps). Net net is that the same...

Site looks great here :)

Nothing I know of - @illblew and I have discussed some potential migration plans (since we're also really in need of updating the linux distro on the main VM). Nothing else specifically to be done besides decision and approval from @pizzainacup and the key mods on going forward with the migration.

Yep - spigot port from 1.12.2 to 1.13 is trivial, relatively speaking: no custom blocks, and spigot worked pretty hard to try to preserve compatibility, when possible (big part of Bukkit/Spigot is the fact that it is even possible to have a plugin run on multiple versions - Forge rarely allows...

On the block ID question from earlier: the new blocks literally don't use a consistent number for how they are stored - internally, the data scheme is now a 'flattened' index space, which is just a fancy way of saying 'we used to have a 2 part number - and ID and a metadata value - and now each...

Yep - every mod we use, last I checked, is Java 8 only - we've only supported Java 8 since the 1.11.2 move, independent of whether 1.11.2 allowed Java 7 or not. Forge, as of as recently as May, only supported Java 8 (and specifically did not support Java 9 - some issues with launchwrapper...

The biggest issue is going to be the migration of existing block data to new blocks: the mapping isn't one to one, or even 1 to N or N to 1. Lots of shuffling even among vanilla-like blocks, and every reason to expect it to be tricky (since, for example, may of the states in 1.12.2 are runtime...

Cool!! OK, I'm going to be traveling for two weeks, starting on Friday (9/14) - mostly on board a ship, so intermittent internet at best. I'll be in UK and Ireland, when on land (with a couple days in London next weekend before the ship heads out), so I'd like to shoot to deploy to 1.12.2...

OK - long day of working on WC 1.12.2 - lots of progress, and I think I've licked the lag gremlins that @Emotione11 was seeing. Client and server are up to date - please give things a look! @Dan_Prime You are on whitelist - if anyone else wants to be added, just ask. Sorry that I've been off...

Production Server and Client updated (28 July 2018): Updated WesterosBlocks (new blocks for Oldtown) Updated Resource Pack Updated Dynmap Existing launcher, new alpha launcher, and Technic based clients updated

Not sure - I'm running with 3G on both min and max heap, and just logged on and was pretty clean while flying around King's Landing....

You may have given me the excuse I need to plan to visit London again ;) This is TOO cool!

If we're looking good, I'd like to start working towards a migration plan. A lot of existing mod support for 1.11.2 is starting to sunset, and I'm hoping we can avoid getting as far behind the curve as we were back with 1.7.10.

The client itself requires Java 8 - any other Java version is probably gonna have problems.

Updated Optifine in Production to C7 (we've been running C7 on test for a couple of months, so feeling pretty good about it).

Dunno - I'll try to study the problem a bit: haven't tried running the MC client under a memory profiler in a while, but it could be illuminating :) . If I find anything particularly 'damning' about how we're doing any of these - or, more accurately, how OptiFine opts to implement any of the CTM...

Make sure the Java settings (under the Gear) are '3G' or higher (3K would be 'very bad')

The latest update - which, as always, added more images to both our resource pack and to the WesterosBlocks mod to support new blocks - seems to have finally pushed us to the 'tipping point' for our default launcher memory settings (that is 2GB min/max for Java on the launched VM). From my own...