Hide World Seed.

Discussion in 'Archived: Plugin Requests' started by Inferno, Jan 29, 2012.

  1. Offline

    Inferno

    Yes I know this wouldn't be a plugin more like a craftbukkit.jar mod, but my server and others will really need this. When someone presses F3 they can find the world seed and then use programs like AMIDST or go onto single-player and find out the location of strongholds, or use xrays to find where the valuables are at. I want this to not happen!

    Couldn't there be a few class files that could be added to craftbukkit.jar that when someone does F3 the seed is displayed as something like -0000000000 but the client STILL gets the data it needs?
     
  2. Offline

    Minerhax444

    Force them to use Spoutcraft. That way, they can't see the seed, and you can use Spout plugins to stop xraying on the actual server.
     
  3. Offline

    mushroomhostage

    I've been working on something to do this (without client mods), but it has some significant drawbacks. If you want to try it (experimental):

    http://dl.dropbox.com/u/57628348/NoSeed-0.1.jar

    Then launch CraftBukkit through NoSeed:

    java -Xincgc -mx4G -javaagent:NoSeed-0.1.jar=42 -jar craftbukkit-1.1-R2.jar

    where "42" is whatever seed you want to send to the clients.

    It only fakes seed sent in the Packet1Login packet, and does not affect the world on the server. Problem is, the client uses the seed to calculate biome colors and weather, so things won't look quite right. I'm not sure if this effect is purely visual or has other consequences (haven't tested it much).

    Maybe a modified client (Spout?) could correct the biome colors, based on input from the server? If Spoutcraft is merely hiding the seed from the GUI, that may prevent a subset of users from seeing it, but as long as it is sent over the network it isn't secured and can be captured.

    Another option is to use a different hidden seed for ore generation (and strongholds etc.), but leave the public seed used for terrain generation visible. This is the approach taken by ChunkScrambler.
     

Share This Page