| Только для Java Edition Edition |
Chunks store the terrain and entities within a 16×256×16 area. They also store precomputed lighting, heightmap data for Minecraft's performance, and other meta information.
NBT structure
См. также: Anvil (формат карт)
Chunks are stored in NBT format, with this structure (see Block Format below for the ordering of the blocks within each array):
- The root tag.
- DataVersion: Version of the chunk NBT structure.
- Level: Chunk data.
- xPos: X position of the chunk.
- zPos: Z position of the chunk.
- LastUpdate: Tick when the chunk was last saved.
- InhabitedTime: The cumulative number of ticks players have been in this chunk. Note that this value increases faster when more players are in the chunk. Used for regional difficulty: increases the chances of mobs spawning with equipment, the chances of that equipment having enchantments, the chances of spiders having potion effects, the chances of mobs having the ability to pick up dropped items, and the chances of zombies having the ability to spawn other zombies when attacked. Note that at values 3600000 and above, regional difficulty is effectively maxed for this chunk. At values 0 and below, the difficulty is capped to a minimum (thus, if this is set to a negative number, it will behave identically to being set to 0, apart from taking time to build back up to the positives). See Regional Difficulty for more specifics.
- Biomes: May not exist. 256 bytes of biome data, one byte for each vertical column in the chunk. See Data Values for biome IDs. If this tag does not exist it will be created and filled by Minecraft when the chunk is loaded and saved. If any values in this array are -1, Minecraft will also set them to the correct biome.
- Heightmaps:
- LIGHT_BLOCKING:
- MOTION_BLOCKING:
- MOTION_BLOCKING_NO_LEAVES:
- OCEAN_FLOOR:
- OCEAN_FLOOR_WG:
- WORLD_SURFACE:
- WORLD_SURFACE_WG:
- CarvingMasks:
- AIR:
- LIQUID:
- Sections: List of Compound tags, each tag is a sub-chunk of sorts.
- An individual Section.
- Y: The Y index (not coordinate) of this section. Range 0 to 15 (bottom to top), with no duplicates but some sections may be missing if empty.
- Palette: Set of different block states used in the chunk.
- : Block state
- Name: Id of the block
- Properties: List of block state properties, with [name] being the name of the block state property
- [name]: value of the property
- : Block state
- BlockLight: 2048 bytes recording the amount of block-emitted light in each block. Makes load times faster compared to recomputing at load time. 4 bits per block.
- BlockStates:
- SkyLight: 2048 bytes recording the amount of sunlight or moonlight hitting each block. 4 bits per block.
- An individual Section.
- Entities: Each TAG_Compound in this list defines an entity in the chunk. See Entity Format below. If this list is empty it will be a list of End tags (before 1.10, list of Byte tags).
- TileEntities: Each TAG_Compound in this list defines a block entity in the chunk. See Block Entity Format below. If this list is empty it will be a list of End tags (before 1.10, list of Byte tags).
- TileTicks: Each TAG_Compound in this list is an "active" block in this chunk waiting to be updated. These are used to save the state of redstone machines or falling sand, and other activity. See Tile Tick Format below.
- LiquidTicks:
- Lights: A List of 16 lists.
- LiquidsToBeTicked: A List of 16 lists.
- ToBeTicked: A List of 16 lists.
- PostProcessing: A List of 16 lists.
- Status: One of the following: empty, base, carved, liquid_carved, decorated, lighted, mobs_spawned, finalized, fullchunk, or postprocessed.
- Structures:
- References:
- [Structure Name]:
- Starts:
- [Structure Name]: Only the structures that can spawn in this dimension are stored, for example, EndCity is only stored in the end chunks.
- ChunkX: Chunk X coordinate of the start of the structure. Absent if id is INVALID.
- ChunkZ: Chunk Z coordinate of the start of the structure. Absent if id is INVALID.
- id: If there's no structure of this kind in this chunk, this value is "INVALID", else it's the structure name.
- biome: The biome id this structure is in. Absent if id is INVALID.
- BB: Bounding box of the entire structure. Value is 6 ints: the minimum X, Y, and Z coordinates followed by the maximum X, Y, and Z coordinates. Absent if id is INVALID.
- Valid: 1 or 0 (true/false) - (Village only) Whether the village generated at least 3 non-roads. Absent if id is INVALID.
- Processed: (Monument only) List of chunks that have had their piece of the structure created. Absent if id is INVALID.
-
- X: Chunk X coordinate
- Z: Chunk Z coordinate
-
- Children: List of structure pieces making up this structure. Absent if id is INVALID.
- : Structure piece data.
- id: Identifier for the structure piece. Typically a heavily abbreviated code rather than something human-readable.
- Rot: Rotation of ocean ruins and shipwrecks. Valid values are COUNTERCLOCKWISE_90, NONE, CLOCKWISE_90, and CLOCKWISE_180.
- BiomeType: The ocean temperature this ocean ruins is in. Valid values are WARM and COLD.
- Template: The template of the ocean ruin or shipwreck that was used.
- integrity: The integrity of this structure (only used by ocean ruins).
- TPX: The X coordinate origin of this ocean ruin or shipwreck.
- TPY: The Y coordinate origin of this ocean ruin or shipwreck.
- TPZ: The Z coordinate origin of this ocean ruin or shipwreck.
- isLarge: 1 or 0 (true/false) - If this ocean ruin is big.
- GD: Appears to be some sort of measure of how far this piece is from the start.
- O: Likely orientation of the structure piece.
- BB: Bounding box of the structure piece. (Does not include the part of a village roof that can overhang the road.) Value is 6 ints: the minimum X, Y, and Z coordinates followed by the maximum X, Y, and Z coordinates.
- Width: (Temples and huts) Width of the structure (X/Z).
- Height: (Temples and huts) Height of the structure (Y).
- Depth: (Temples and huts) Depth of the structure (X/Z).
- HPos: (Temples and huts) Y level the structure was moved to in order to place it on the surface, or -1 if it hasn't been moved yet.
- placedTrap1: 1 or 0 (true/false) - (Jungle temple) Whether the hallway arrow trap dispenser was placed.
- placedTrap2: 1 or 0 (true/false) - (Jungle temple) Whether the chest arrow trap dispenser was placed.
- placedMainChest: (1 or 0 (true/false) - Jungle temple) Whether the main chest was placed.
- placedHiddenChest: 1 or 0 (true/false) - (Jungle temple) Whether the hidden chest was placed.
- hasPlacedChest0: 1 or 0 (true/false) - (Desert temple) Whether chest was placed.
- hasPlacedChest1: 1 or 0 (true/false) - (Desert temple) Whether chest was placed.
- hasPlacedChest2: 1 or 0 (true/false) - (Desert temple) Whether chest was placed.
- hasPlacedChest3: 1 or 0 (true/false) - (Desert temple) Whether chest was placed.
- Witch: 1 or 0 (true/false) - (Witch hut) Whether the initial witch has been spawned for the hut.
- hr: 1 or 0 (true/false) - (Mineshaft "MSCorridor") Whether the corridor has rails.
- sc: 1 or 0 (true/false) - (Mineshaft "MSCorridor") Whether the corridor has cobwebs.
- hps: 1 or 0 (true/false) - (Mineshaft "MSCorridor") Whether the corridor has a cave spider spawner.
- Num: (Mineshaft "MSCorridor") Corridor length.
- tf: 1 or 0 (true/false) - (Mineshaft "MSCrossing") Whether the crossing is two floors tall.
- D: (Mineshaft "MSCrossing") Indicates the "incoming" direction for the crossing.
- Entrances: (Mineshaft "MSRoom") List of exits from the room.
- : Bounding box of the exit.
- Chest: 1 or 0 (true/false) - (Fortress "NeSCLT" and "NeSCRT") Whether this fortress piece should contain a chest but hasn't had one generated yet. (Stronghold "SHCC") Whether this chest in this stronghold piece was placed. (Village "ViS") Whether the blacksmith chest has been generated.
- Mob: 1 or 0 (true/false) - (Fortress "NeMT") Whether this fortress piece should contain a Blaze spawner but hasn't had one generated yet. (Stronghold "SHPR") Whether the Silverfish spawner has been placed in this piece.
- Seed: (Fortress "NeBEF") Random seed for the broken-bridge fortress piece.
- EntryDoor: (Stronghold) The type of door at the entry to this piece.
- Steps: (Stronghold "SHFC") Length of the corridor
- leftLow: 1 or 0 (true/false) - (Stronghold "SH5C") Whether the 5-way crossing has an exit on the lower level on the side with the upward staircase.
- rightLow: 1 or 0 (true/false) - (Stronghold "SH5C") Whether the 5-way crossing has an exit on the lower level on the side with the downward staircase.
- leftHigh: 1 or 0 (true/false) - (Stronghold "SH5C") Whether the 5-way crossing has an exit on the upper level on the side with the upward staircase.
- rightHigh: 1 or 0 (true/false) - (Stronghold "SH5C") Whether the 5-way crossing has an exit on the upper level on the side with the downward staircase.
- Tall: 1 or 0 (true/false) - (Stronghold "SHLi") Whether the library has an upper level.
- Type: (Stronghold "SHRC") Indicates whether the room contains a pillar with torches, a fountain, an upper level with a chest, or is just empty room.
- Source: 1 or 0 (true/false) - (Stronghold "SHSD") Whether the spiral staircase is the source of the Stronghold or was randomly generated.
- Left: 1 or 0 (true/false) - (Stronghold "SHS") Whether the corridor has an opening on the left.
- Right: 1 or 0 (true/false) - (Stronghold "SHS") Whether the corridor has an opening on the right.
- Type: (Village) Village type: 0=plains, 1=desert, 2=savanna, 3=taiga.
- Zombie: 1 or 0 (true/false) - (Village) Whether this village generated as a zombie village.
- VCount: (Village) Count of villagers spawned along with this piece.
- HPos: (Village) Y level the piece was moved to in order to place it on the surface, or -1 if it hasn't been moved yet.
- CA: (Village "ViF" and "ViDF") Crop in the farm plot.
- Name: Id of the block
- Properties: List of block state properties, with [name] being the name of the block state property
- [name]: value of the property
- CB: (Village "ViF" and "ViDF") Crop in the farm plot.
- Name: Id of the block
- Properties: List of block state properties, with [name] being the name of the block state property
- [name]: value of the property
- CC: (Village "ViDF") Crop in the farm plot.
- Name: Id of the block
- Properties: List of block state properties, with [name] being the name of the block state property
- [name]: value of the property
- CD: (Village "ViDF") Crop in the farm plot.
- Name: Id of the block
- Properties: List of block state properties, with [name] being the name of the block state property
- [name]: value of the property
- Terrace: 1 or 0 (true/false) - (Village "ViSH") Whether the house has a ladder to the roof and fencing.
- T: (Village "ViSmH") Table: 0 is no table, 1 and 2 place it on either side of the hut.
- C: (Village "ViSmH") Hut roof type.
- Length: (Village "ViSR") Length of the road piece.
- : Structure piece data.
- [Structure Name]: Only the structures that can spawn in this dimension are stored, for example, EndCity is only stored in the end chunks.
- References:
Block format
In the Anvil format, block positions are ordered YZX for compression purposes.
The coordinate system is as follows:
- X increases East, decreases West
- Y increases upwards, decreases downwards
- Z increases South, decreases North
This also happens to yield the most natural scan direction, because all indices in the least significant dimension (i.e. X in this case) appear for each index in the next most significant dimension; so one reads an array ordered YZX as one would a book lying with its top northward, all letters (or X-indices) on a single line (or Z-index) at a time, and all lines on a single page (or Y-index) at a time. For the 2D arrays (i.e. "Biomes" and "HeightMap") the inapplicable Y dimension is simply omitted, as though the book is only one page thick.
Each section in a chunk is a 16x16x16-block area, with up to 16 sections in a chunk. Section 0 is the bottom section of the chunk, and section 15 is the top section of the chunk. To save space, completely empty sections are not saved. Within each section is a byte tag "Y" for the Y index of the section, 0 to 15, and then byte arrays for the blocks. The "Block" byte array has 4096 partial block IDs at 8 bits per block. Another byte array "Add" is used for block with IDs over 255, and is 2048 bytes of the other part of the 4096 block IDs at 4 bits per block. When both the "Block" and "Add" byte arrays exist, the partial ID from the "Add" array is shifted left 8 bits and added to the partial ID from the "Blocks" array to form the true Block ID. The "Data" byte array is also 2048 bytes for 4096 block data values at 4 bits per block. The "BlockLight" and "SkyLight" byte arrays are the same as the "Data" byte array but they are used for block light levels and sky light levels respectively. The "SkyLight" values represent how much sunlight or moonlight can potentially reach the block, independent of the current light level of the sky.
The endianness of the 2048-byte arrays (i.e. "Add," "Data," "BlockLight," & "SkyLight"), which give only 4 bits per block, seems to stand as the one anomalous exception to the otherwise consistent, format-wide standard of big-endian data storage. It also runs counter to the presumably natural human-readable printing direction. If the blocks begin at 0, they are grouped with even numbers preceding odd numbers (i.e. 0 & 1 share a byte, 2 & 3 share the next, etc.); under these designations Minecraft stores even-numbered blocks in the least significant half-byte, and odd-numbered blocks in the most significant half-byte. Thus block[0] is byte[0] at 0x0F, block[1] is byte[0] at 0xF0, block[2] is byte[1] at 0x0F, block[3] is byte[1] at 0xF0, etc. ...
The pseudo-code below shows how to access individual block information from a single section. Hover over text to see additional information or comments.
byte Nibble4(byte[] arr, int index){ return index%2 == 0 ? arr[index/2]&0x0F : (arr[index/2]>>4)&0x0F; } int BlockPos = y*16*16 + z*16 + x; byte BlockID_a = Blocks[BlockPos]; byte BlockID_b = Nibble4(Add, BlockPos); short BlockID = BlockID_a + (BlockID_b << 8); byte BlockData = Nibble4(Data, BlockPos); byte Blocklight = Nibble4(BlockLight, BlockPos); byte Skylight = Nibble4(SkyLight, BlockPos);
Entity format
Every entity is an unnamed TAG_Compound contained in the Entities list of a chunk file. The sole exception is the Player entity, stored in level.dat, or in <player>.dat files on servers. All entities share this base:
- Entity data
Chunk format/Entity
Mobs
| Mob Entities | |
|---|---|
| Entity ID | Name |
| bat | Bat |
| blaze | Blaze |
| cave_spider | Cave Spider |
| chicken | Chicken |
| cow | Cow |
| creeper | Creeper |
| dolphin | Dolphin |
| donkey | Donkey |
| drowned | Drowned |
| elder_guardian | Elder Guardian |
| ender_dragon | Ender Dragon |
| enderman | Enderman |
| endermite | Endermite |
| evoker | Evoker |
| ghast | Ghast |
| giant | Giant |
| guardian | Guardian |
| horse | Horse |
| husk | Husk |
| illusioner | Illusioner |
| iron_golem | Iron Golem |
| llama | Llama |
| magma_cube | Magma Cube |
| mooshroom | Mooshroom |
| mule | Mule |
| ocelot | Ocelot |
| parrot | Parrot |
| pig | Pig |
| phantom | Phantom |
| polar_bear | Polar Bear |
| rabbit | Rabbit |
| sheep | Sheep |
| shulker | Shulker |
| silverfish | Silverfish |
| skeleton | Skeleton |
| skeleton_horse | Skeleton Horse |
| slime | Slime |
| snow_golem | Snow Golem |
| spider | Spider |
| squid | Squid |
| stray | Stray |
| turtle | Turtle |
| vex | Vex |
| villager | Villager |
| vindicator | Vindicator |
| witch | Witch |
| wither | Wither |
| wither_skeleton | Wither Skeleton |
| wolf | Wolf |
| zombie | Zombie |
| zombie_horse | Zombie Horse |
| zombie_pigman | Zombie Pigman |
| zombie_villager | Zombie Villager |
Mobs are a subclass of Entity with additional tags to store their health, attacking/damaged state, potion effects, and more depending on the mob. Players are a subclass of Mob.
Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude
Projectiles
| Projectile Entities | |
|---|---|
| Entity ID | Name |
| arrow | Arrow |
| dragon_fireball | Ender Dragon Fireball |
| egg | Egg |
| ender_pearl | Ender Pearl |
| experience_bottle | Bottle o' Enchanting |
| fireball | Ghast Fireball |
| llama_spit | Llama spit |
| potion | Splash Potion |
| small_fireball | Blaze Fireball/Fire Charge |
| shulker_bullet | Shulker Bullet |
| snowball | Snowball |
| spectral_arrow | Spectral Arrow |
| trident | Trident |
| wither_skull | Wither Skull |
Projectiles are a subclass of Entity and have very obscure tags such as X,Y,Z coordinate tags despite Entity Pos tag, inTile despite inGround, and shake despite most projectiles not being arrows. While all projectiles share tags, they are all independently implemented through Throwable and ArrowBase.
Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude
Items and XPOrbs
| Item Entities | |
|---|---|
| Entity ID | Name |
| experience_orb | Experience Orb |
| item | Dropped Item |
Items and XPOrbs are a subclass of Entity. Шаблон:Data transclude Шаблон:Data transclude
Vehicles
| Vehicle Entities | |
|---|---|
| Entity ID | Name |
| boat | Boat |
| minecart | Minecart |
| chest_minecart | Minecart with Chest |
| command_block_minecart | Minecart with Command Block |
| furnace_minecart | Minecart with Furnace |
| hopper_minecart | Minecart with Hopper |
| spawner_minecart | Minecart with Spawner |
| tnt_minecart | Minecart with TNT |
Vehicles are subclasses of Entity.
Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude
Dynamic tiles
| Dynamic Block Entities | |
|---|---|
| Entity ID | Name |
| falling_block | Dynamic Tile |
| tnt | TNT |
Dynamic tiles are a subclass of Entity and are used to simulate realistically moving blocks.
Шаблон:Data transclude Шаблон:Data transclude
Other
| Other Entities | |
|---|---|
| Entity ID | Name |
| area_effect_cloud | Area Effect Cloud |
| armor_stand | Armor Stand |
| end_crystal | End Crystal |
| evoker_fangs | Evoker Fangs |
| eye_of_ender | Eye of Ender |
| firework_rocket | Firework Rocket |
| item_frame | Item Frame |
| leash_knot | Lead Knot |
| painting | Painting |
| fishing_bobber | Fishing Rod Bobber |
Other entity types that are a subclass of Entity but do not fit into any of the above categories.
Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude
Шаблон:Anchor Block entity format
| Block Entities | |
|---|---|
| Block Entity ID | Associated Block |
| banner | Banner |
| beacon | Beacon |
| bed | Bed |
| brewing_stand | Brewing Stand |
| cauldron (BE) | Cauldron |
| chest | Chest Trapped Chest |
| comparator | Redstone Comparator |
| command_block | Command Block |
| daylight_detector | Daylight Detector |
| dispenser | Dispenser |
| dropper | Dropper |
| enchanting_table | Enchanting Table |
| ender_chest | Ender Chest |
| end_gateway | End Gateway (block) |
| end_portal | End Portal (block) |
| furnace | Furnace |
| hopper | Hopper |
| jukebox | Jukebox |
| mob_spawner | Monster Spawner |
| piston | Piston Moving |
| shulker_box | Shulker Box |
| sign | Sign |
| skull | Mob head |
| structure_block | Structure Block |
A block entity (not related to entity) is used by Minecraft to store information about a block that can't be stored in the four bits of block data the block has. Block entities were called "tile entities" until the 1.8 snapshots and that term is still used in some command usage.
Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude Шаблон:Data transclude
Tile tick format
Tile Ticks represent block updates that need to happen because they could not happen before the chunk was saved. Examples reasons for tile ticks include redstone circuits needing to continue updating, water and lava that should continue flowing, recently placed sand or gravel that should fall, etc. Tile ticks are not used for purposes such as leaf decay, where the decay information is stored in the leaf block data values and handled by Minecraft when the chunk loads. For map makers, tile ticks can be used to update blocks after a period of time has passed with the chunk loaded into memory.
- A Tile Tick
Chunk format/Tile Tick
History
Chunks were first introduced in Minecraft Infdev. Before the addition of the MCRegion format in Beta 1.3, chunks were stored as individual chunk files ".dat" where the file names contained the chunk's position encoded in Base36 - this is known as the Alpha level format. MCRegion changed this by storing groups of 32×32 chunks in individual ".mcr" files with the coordinates in Base10, with the goal being to reduce disk usage by cutting down on the number of file handles Minecraft had open at once. MCRegion's successor is the current format, Anvil, which only made changes to the chunk format. The region file technique is still used, but the region file extensions are ".mca" instead.
The major change from MCRegion to Anvil was the division of Chunks into Sections; each chunk has up to 16 individual 16×16×16 block Sections so that completely empty sections will not be saved at all. Preparation has also been made to support blocks with IDs in the range 0 to 4095, as compared to the previous 0 to 255 limitation. However, Minecraft is not fully prepared for such blocks to exist as items; many item IDs are already taken in the range 256 to 4095.
The Blocks, Data, BlockLight, and SkyLight arrays are now housed in individual chunk Sections. The Data, SkyLight, and BlockLight are arrays of 4-bit values, and the BlockLight and SkyLight arrays no longer house part of the block ID. The Blocks array is 8 bits per block, and the 4096-blocks support exists in the form of an optional Add byte array of 4-bits per block for additional block ID information. With the Anvil format, the NBT Format was changed from Notch's original specification to include an integer array tag similar to the existing byte array tag. It is currently only used for HeightMap information in chunks.
Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History Шаблон:History