![]() The resettable solution is primarily used when chunk permaloading cannot be achieved (for example in a Spigot server), or when the chaining process is so complex it cannot be done manually (such as in concentrical chained villages). The solution to this is either putting the whole chained village in spawn chunk or its equivalent, then use a little trick to continue loading the chunks even when no player is in the same dimension as it (the non-resettable solution), or use redstone to rechain the village whenever the player needs (the resettable solution). Require a whole lot more door placing and breaking if it is non-resettable, and a lot more doors if it's auto-resettable.īecause even the quickest reloading of chunks (usually done in autosaving, and affects most kind of chunk loaders) will basically wipe all villages data in those chunks and recalculate everything, chunks containing chained villages must never unload as long as the game is open, or else the whole thing will merge.They have all component villages' centers in the exact same spot.Ĭomparing the non-concentrical version to the concentrical version On the other hand, concentrical chained villages are discovered much later. Their component villages' centers is usually arranged on a line and are not put in the same position. Non-concentrical chained villages are the first to be discovered. 2.4.1 Layered chained village + Keeping doors detected + Undetecting a doorĬlassifications Non-Concentrical and Concentrical.2.4 House detection mechanics & Layered chained village + Keeping doors detected + Undetecting a door.2.2 Properties of the village center & Center anchor.2.1 Village merging priority & Border extender. ![]() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |