Search results

  1. mikeprimm

    Start of port to v1.12.2

    Good to hear, @Dan_Prime - I've only just started looking at Forge 1.13.2, for the sake of Dynmap. Once I've got that done (needed for the broader Dynmap community, since I've already got it for Spigot 1.13.2 and the Forge guys get jealous ;) ), I'm going to start sizing the effort for 1.13.2 -...
  2. mikeprimm

    Server Updates

    Server and client update for Prod: 1) New WesterosBlocks with additional and fixed blocks (Ask @Emotione11 for details!) 2) Updated Dynmap
  3. mikeprimm

    Start of port to v1.12.2

    OK - so, 1.12.2 test client and server are all up to date and ready for final testing! Please give it a look, so that we can prep for deploying it to production 'soon' :)
  4. mikeprimm

    Start of port to v1.12.2

    Cool - pleasant surprise :) I definitely know you don't want to 'poke the bear' over on Forge: didn't know whether they're so tied up in trying to move 1.13.x forward that they were gonna be slow on looking at non-1.13 work!
  5. mikeprimm

    Start of port to v1.12.2

    Really don't want to get into building a custom Forge for any reason.... if they don't accept the fix quickly, we can work around it without corrupting our ongoing ability to have a Forge supported by other modders (none of who will give us the time of day if we aren't working with an official...
  6. mikeprimm

    Start of port to v1.12.2

    OK - nice! Just to be clear: with 1.4.1, we should be good for updating to the newer forge, yes? I'll give it a spin - thanks for the quick response! Edit: Confirmed working - I've updated distribution.json, so we're all in sync with the current recommended Forge (2768).
  7. mikeprimm

    Start of port to v1.12.2

    I'm getting the impression that the requirement to match the Maven-Artifact field, at least for 1.12.2, isn't a concern - almost everything I've looked at (Optifine, BetterFoliage, JourneyMap, worldeditcuife) don't have it in their manifest. I'm pretty sure that field is only added if you go...
  8. mikeprimm

    Start of port to v1.12.2

    @Dan_Prime Nice job on running down the issue - I saw the commit activity around that issue, which was why I tried the latest build (2796) AND the build before the change Lex made in September (2759), but without good results. I'll check the maven identifiers for the couple of new components...
  9. mikeprimm

    Start of port to v1.12.2

    OK - completed big round of mod refreshes for the 1.12.2 server and client: On client: Updated to Forge 2768 (on legacy launcher): still on Forge 2651 on new launcher due to problem (looks like Forge builds from the last few months aren't working with the --modListFile parameter the new...
  10. mikeprimm

    Start of port to v1.12.2

    OK - added SEUS-Reloaded to 1.12.2 client. As with the prior SEUS, SEUS-Reloaded works on Windows but has issues on Mac. I've found instructions for patching it for SEUS - the headache is that the license for SEUS specifically precludes redistribution of any modifications to SEUS, so I'm not...
  11. mikeprimm

    Start of port to v1.12.2

    OK - v1.3.0 launcher is confirmed good for the issue I was seeing on Macs with the 1.12.2 client. I'm going to review over the 1.12.2 content, as far as 3rd party mods, in the next day or so, and bring the client and test server up to a current proposed release candidate. I'll post here when...
  12. mikeprimm

    Start of port to v1.12.2

    Yep - done
  13. mikeprimm

    Start of port to v1.12.2

    Still no luck with 1.12.2 launching on new launcher (I pulled down your updates this morning). Not seeing much detail on the particulars in the console - it's tripping on the versionData being null after 'validateEverything' returns with a result of 'Error during validation: Cannot read...
  14. mikeprimm

    Start of port to v1.12.2

    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.
  15. mikeprimm

    Start of port to v1.12.2

    @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...
  16. mikeprimm

    Website Refresh Feedback Thread

    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...
  17. mikeprimm

    Website Refresh Feedback Thread

    Site looks great here :)
  18. mikeprimm

    Start of port to v1.12.2

    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.
  19. mikeprimm

    Start of port to v1.12.2

    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...
  20. mikeprimm

    Start of port to v1.12.2

    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...
Top