Custom PvP worlds

From Simplicitypvp
Revision as of 02:30, 10 January 2024 by SengornLeopard (talk | contribs) (Typos, Grammar correction)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

The server has sometimes in the past used custom PvP worlds, sometimes created by individual players, sometimes created as a community effort, and sometimes using old bases built in the overworld of the server. This page serves as a basic introduction for what's required for a custom pvp world, should anybody wish to create one.

Custom PvP worlds have to be prepared by somebody, and this can take a lot of effort. Preparing it basically means that the world is ready to be directly inserted as the pvp world, with no further work.

A prepared world is some file (.tar.gz or .zip) containing all the world files. For example, if you create a world in singleplayer, it would be everything inside the world directory, containing files such as level.dat and most importantly, the region directory which contains all the .mca files for the world.

The prepared world should be centered on 0 0, and it should have all valuable blocks removed. It must not contain large amounts of diamond blocks, or similarly valuable items that can be easily looted. Ores in the ground are ok, as long as they aren't in a greater than usual density. Here's a good list of items to remove but note that this list may not be complete.

chest,ender_chest,diamond_block,iron_block,gold_block,dispenser,coal_block,sponge,wet_sponge,slime_block,dropper,hopper,tnt,rail,powered_rail,detector_rail,piston,sticky_piston,trapped_chest,emerald_block,lapis_block,enchanting_table,bookshelf,furnace,jukebox,beacon,command_block,chain_command_block,repeating_command_block,mob_spawner,netherite_block,ancient_debris,raw_gold_block,raw_iron_block,raw_copper_block,copper_block,shulker_box,white_shulker_box,orange_shulker_box,magenta_shulker_box,light_blue_shulker_box,yellow_shulker_box,lime_shulker_box,pink_shulker_box,gray_shulker_box,light_gray_shulker_box,cyan_shulker_box,purple_shulker_box,blue_shulker_box,brown_shulker_box,green_shulker_box,red_shulker_box,black_shulker_box,player_head,player_wall_head,end_portal,end_portal_frame,nether_portal,dragon_egg,lectern,smoker,blast_furnace,barrel,brewing_stand,deepslate_emerald_ore,deepslate_redstone_ore,deepslate_gold_ore,deepslate_copper_ore,deepslate_iron_ore,deepslate_coal_ore,deepslate_lapis_ore,deepslate_diamond_ore,coal_ore,iron_ore,copper_ore,gold_ore,redstone_ore,emerald_ore,lapis_ore,diamond_ore,nether_gold_ore,lodestone,petrified_oak_slab

Most entities will generally be removed: kill @e[distance=..10000,type=!minecraft:player]

If the world is based on some base from the overworld which coords are not public, anything that might reveal those coords should also be removed. This is things such as signs and maps.

What the size of the world border should be is not fixed, it can be whatever size might make the most sense. Usually something like 500x500 is a reasonable size.

The world should be prepared well ahead of the scheduled reset, if it is not ready on time, it will not be used. Preferably it should be ready at least one month ahead of the scheduled reset. If it is not ready in time, it can always be used for the next reset, 2 months later.