Right now, thanks to 1.8 the client can use xray mods and there is nothing we as server owners can do. Before they relied on our server telling their machine where diamonds and minerals were. That gave us(the server owners) the power to block sending ore and other minerals data to their machine till it was exposed by a miner. But even then, they could run programs that could reverse engineer the map to get the seed.
With 1.8 generating the map on the client machine from a published seed, we have NO control. So I propose you(minecraft team) set the maps up for 2 seeds. One seed published for the lay of the land. The second seed is a mineral/ore placement seed that we can choose to not published.
This will give us(the server owners) the ability to hold off sending ore placement data till the ore is exposed. If minecraft is to succeed, you need to come up with a method to block hacking.
Many servers are RPG or MMO or running on a Mineral economy. If your not going to provide anti-hacking tools, then you must give us the ability to create anti-hacking methods.
Concerned Minecrafter,
~MachetePanda
There is no X-Ray mod for 1.8 yet except Zombe's which is apparently decidedly crappy.
Im actually using one right now that I will not mention the name of. The great thing about the popular old xray mod was that the creator wasnt malicious when he made it. He also made an antixray tool for server owners. But that tool would now not work. Because of what I said to the below person...
I think it'd be best just to have a block/allow seed show setting.
But it wouldn't matter. 1.8 map generation is now client end based on the seed. If you don't send the send, they can't generate the map. Your computer now generates the map(as oppse to pre-1.8 when it requested map data) then the server tells your computer only whats different about the map.
The closest thing we could do as server owners is have a plugin from our amazing plugin community that replaces all the ores in the map. so basically, Client receives seed, generates map, then as they are digging, every dig the server is showing a different placement. Not a solution that will bring minecraft success. It would be better if we only had to check for ore exposure then send exposed ore information(the other way I mentioned your basically resending the whole thing.
Compounded on top of that, my above mentioned solution would now mean tools like regen(used often to fix map greifs) would not work.
This is actually a good idea. Allowing a server to have a resource distribution seed and a terrain generation seed would keep those resources hidden while saving bandwidth with client side terrain generation. It would be best if the resource seed didn't kick in until under height ~40.
Given that F3 is a development feature, it won't make it in to the actual release, and in the meantime it makes it easier for casual players to test seeds, you can't complain about your private server while it's still in beta, it's there to test it, it won't make it into the released game, chill out, you'll probably wipe once or twice before november anyway.
Given that F3 is a development feature, it won't make it in to the actual release, and in the meantime it makes it easier for casual players to test seeds, you can't complain about your private server while it's still in beta, it's there to test it, it won't make it into the released game, chill out, you'll probably wipe once or twice before november anyway.
Unfortunately, even when the F3 menu goes away, it'll be really easy to hack the client to expose the seed again. The point is that mineral generation should probably be handled server-side and only exposed as minerals are exposed to prevent abuse. I agree.
Given that F3 is a development feature, it won't make it in to the actual release, and in the meantime it makes it easier for casual players to test seeds, you can't complain about your private server while it's still in beta, it's there to test it, it won't make it into the released game, chill out, you'll probably wipe once or twice before november anyway.
The seed is still published to the client.
... I dont even know why your replying to this thread. Understand the game engine before posting.
Unfortunately, even when the F3 menu goes away, it'll be really easy to hack the client to expose the seed again. The point is that mineral generation should probably be handled server-side and only exposed as minerals are exposed to prevent abuse. I agree.
With 1.8 generating the map on the client machine from a published seed, we have NO control. So I propose you(minecraft team) set the maps up for 2 seeds. One seed published for the lay of the land. The second seed is a mineral/ore placement seed that we can choose to not published.
This will give us(the server owners) the ability to hold off sending ore placement data till the ore is exposed. If minecraft is to succeed, you need to come up with a method to block hacking.
Many servers are RPG or MMO or running on a Mineral economy. If your not going to provide anti-hacking tools, then you must give us the ability to create anti-hacking methods.
Concerned Minecrafter,
~MachetePanda
Im actually using one right now that I will not mention the name of. The great thing about the popular old xray mod was that the creator wasnt malicious when he made it. He also made an antixray tool for server owners. But that tool would now not work. Because of what I said to the below person...
But it wouldn't matter. 1.8 map generation is now client end based on the seed. If you don't send the send, they can't generate the map. Your computer now generates the map(as oppse to pre-1.8 when it requested map data) then the server tells your computer only whats different about the map.
The closest thing we could do as server owners is have a plugin from our amazing plugin community that replaces all the ores in the map. so basically, Client receives seed, generates map, then as they are digging, every dig the server is showing a different placement. Not a solution that will bring minecraft success. It would be better if we only had to check for ore exposure then send exposed ore information(the other way I mentioned your basically resending the whole thing.
Compounded on top of that, my above mentioned solution would now mean tools like regen(used often to fix map greifs) would not work.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumUnfortunately, even when the F3 menu goes away, it'll be really easy to hack the client to expose the seed again. The point is that mineral generation should probably be handled server-side and only exposed as minerals are exposed to prevent abuse. I agree.
The seed is still published to the client.
... I dont even know why your replying to this thread. Understand the game engine before posting.
Exactlly.