In control mod как настроить

Содержание

In Control! mod — настройка мобов [1.16.5] [1.15.2] [1.12.2] [1.11.2] [1.10.2]
In Control! — настрой мобов, мод на изменение свойств и характеристик мобов в майнкрафт.
Как пользоваться модом In Control!:
In Control! mod — настройка мобов [1.16.5] [1.15.2] [1.12.2] [1.11.2] [1.10.2]
In Control! — настрой мобов, мод на изменение свойств и характеристик мобов в майнкрафт.
Как пользоваться модом In Control!:
InControl
Contents
Introduction
Spawn Control
Additional Spawns
Loot Control
Experience
Commands
Examples for spawn.json
Examples for potentialspawn.json
Examples for joot.json

In Control! mod — настройка мобов [1.16.5] [1.15.2] [1.12.2] [1.11.2] [1.10.2]

In Control! — настрой мобов, мод на изменение свойств и характеристик мобов в майнкрафт.

Очень крутой мод который позволяет произвольно менять различные параметры мобов в майнкрафт, настраивается огромное количество параметров, от количества здоровья, до времени и места появления, в каких биомах, при какой освещенности, с каким оружием. Можно настроить лут с мобов (что выпадает при смерти моба)

Если вы хотите изменить свойства монстров в игре, то данный мод просто идеален.
Мод полностью работает при помощи конфиг файлов, он не имеет удобного интерфейса, но настройка своих правил довольно проста, я покажу где посмотреть и как прописать, покажу примеры реализующие некоторые возможности и вы сможете сами настраивать мобов для своего клиента.

Как пользоваться модом In Control!:

Итак, после установки мода и запуска игры у вас в папке появится папка \config\incontrol
В ней находится следующие файлы loot.json, main.cfg, potentialspawn.json, spawn.json, summonaid.json, именно их мы и будем менять, все они редактируются при помощи блокнота (я советую программу Notepad++).

Сами по себе файлы пустые, мы должны прописать туда наши правила, все правила доступны на официальной вики по моду, их описание можно перевести в переводчике.
Начну сразу с примеров заполнения конфига, так понятней:
Редактируем файл spawn.json.

Еще более сложная и интересная настройка, она позволяет сделать всех мобов на поверхности в 2 раза более опасными (больше урона и жизни), так же с небольшой вероятностью появятся невидимые зомби в в пещерах, а так же зомби и скелеты на поверхности будут в шлемах и не будут гореть.
Поясню: «mob»: [«Skeleton»,»Zombie»], — отношение к скелетонам и зомби
«seasky»: true, — положительное значение, улица это или нет (видит ли блок небо)
«healthmultiply»: 2, — множитель здоровья
«damagemultiply»: 2, — множитель урона
«speedmultiply»: 2, — множитель скорости
«armorhelmet»: [«minecraft:iron_helmet», «minecraft:golden_helmet»] — спавн в броне в железном шлеме или в золотом.
«random»: 0.1, — вероятность
«potion»: «minecraft:invisibility,10000,1» — включение мобу эффекта невидимости.

Данный конфиг для joot.json, о меняет лут у моба WitherBoss, он убирает у него из лута nether_star, но разрешает выпадание nether_star только если игрок убил его палкой.

Найти все параметры и их пояснения можно на вики — все параметры
Все пояснения к параметру нормально переводятся в переводчике.
Самое главное, соблюдайте синтаксис, не пропускайте запятые, скобки, кавычки.

Источник

In Control! mod — настройка мобов [1.16.5] [1.15.2] [1.12.2] [1.11.2] [1.10.2]

In Control! — настрой мобов, мод на изменение свойств и характеристик мобов в майнкрафт.

Как пользоваться модом In Control!:

Источник

InControl

This is a simple mod that gives you full control on where mobs are allowed to spawn. It is based on a rule system. The rule files are located in config/incontrol.

Introduction

There are currently five rule files (as of 3.7.0):

spawn.json: with this file you can block spawning of certain creatures under certain conditions. In addition, when a spawn is allowed you can also alter some of the properties of the mob like maximum health and others
summonaid.json: this is a file that is structured the same as spawn.json but is only used when zombies are summoned for aid
potentialspawn.json: with this file you can remove and add spawn rules under certain conditions. The rules in this file are used before the rules in spawn.json are fired so make sure that when you add a rule for new mobs here, the new mobs are allowed in spawn.json
loot.json: with this file you can control the loot that mobs drop when they are killed based on various criteria
experience.json: this file controls how much experience you get from killing mobs. It has a similar structure to loot.json except that you cannot control experience based on the type of damage (like magic, fire, explosion, . )

Note, everywhere in the rules below that you can specify items you can use the following notations:

minecraft:sand (just normal minecraft sand)
minecraft:stained_hardened_clay@13 (adds metadata 13)
With NBT (same format as for /give command): minecraft:stained_hardened_clay@13/>

When checking for items you can also use a json like this:

Spawn Control

In this section the rules in spawn.json and summonaid.json are explained. Every rule is basically a set of ‘criteria’ and a set of ‘actions’. Note that in the case of summonaid.json the affected mob will most likely be a zombie. The following criteria are currently supported:

Then there are a number of actions. The most important action is ‘result’:

result: this is either ‘deny’, ‘allow’, or ‘default’. Use ‘deny’ to block the spawn. If ‘allow’ is used then the spawn will be allowed even if vanilla would normally disallow it (i.e. too much light). If ‘default’ is used then it is possible the spawn can still be denied if there is not enough light for example. If ‘allow’ or ‘default’ is used then you can use any of the following actions:
nbt: allows you to add NBT to a spawned mob
healthmultiply: this is a floating point number representing a multiplier for the maximum health of the mob that is spawned. Using 2 here for example would make the spawned mob twice as strong.
healthadd: this is a floating point number that is added to the maximum health
speedmultiply: this is a floating point number representing a multiplier for the speed of the mob
speedadd: this is a floating point number that is added to the speed
damagemultiply: this is a floating point number representing a multiplier for the damage that the mob does
damageadd: this is a floating point number that is added to the damage
angry: this is a boolean that indicates if the mob will be angry at and/or target the nearest player. For zombie pigman this will make them angry at the player immediatelly. Same for enderman and wolves
potion: this is either a single string or a list of strings. Every string represents a potion effect which is indicated like this:

Additional Spawns

In this section the rules in potentialspawn.json are explained. Every rule is basically a set of criteria and then a list of additional mobs to spawn under those criteria. The following criteria as explained from spawn.json can also be used here: mintime, maxtime, minlight, maxlight, minheight, maxheight, minspawndist, maxspawndist, random, structure, mindifficulty, maxdifficulty, seesky, weather, tempcategory, difficulty, block, biome, and dimension. mincount and maxcount are also supported but they only work in the format «, «. i.e. you have to specify a mob.

Then every mob entry has the following attributes:

mob: an entity name in the form Creeper, Skeleton, . for (1.10.2) and optionally the notation modid:name for 1.11.2
weight: an integer indicating the weight of this spawn. i.e. how important it is compared to other spawns
groupcountmin: the minimum amount of mobs to spawn at once
groupcountmax: the minimum amount of mobs to spawn at once

You can also remove mob spawn entries with the remove keyword. This is either a string or a list of strings representing mobs that have to be removed from the possible spawns.

Loot Control

Here we explain how you can control the loot given by mobs when they are killed. The following criteria from spawn.json can also be used here: mintime, maxtime, minlight, maxlight, minheight, maxheight, minspawndist, maxspawndist, random, mindifficulty, maxdifficulty, passive, hostile, seesky, weather, tempcategory, structure, difficulty, block, biome, and dimension. In addition the following criteria are specific for loot:

player: boolean value indicating if the mob was killed by a player
fakeplayer: boolean value indicating if the mob was killed by a fake player (automation behaving as if it is a player)
realplayer: boolean value indicating if the mob was killed by a real player (no automation)
projectile: boolean value indicating if the mob was killed by a projectile
explosion: boolean value indicating if the mob was killed by an explosion
magic: boolean value indicating if the mob was killed by magic
fire: boolean value indicating if the mob was killed by fire
source: a string or a list of strings representing the damage source. Some sources are ‘lightningBolt’, ‘lava’, ‘cactus’, ‘wither’, ‘anvil’, .
helditem: a string or a list of strings representing the item that the player is holding in his/her main hand. The rule will match if the player has any of these items
offhanditem: a string or a list of strings representing the item that the player is holding in his/her off hand. The rule will match if the player has any of these items
bothhandsitem: a string or a list of strings representing the item that the player is holding in his/her main or off hand. The rule will match if the player has any of these items
gamestage: a string indicating the current game stage. This only works if the ‘gamestages’ mod is present

In addition there are the following possible outputs:

item: this is a string or a list of strings representing new loot that will be dropped
itemcount: this is a string representing how many items should drop (optionally depending on looting level). For example: «5/7-10/20-30» will drop 5 items at looting 0, 7-10 items at looting 1 and 20-30 items at looting 2 or beyond
nbt: this is a JSON specifying the NBT that will be used for the loot items
remove: this is a string or a list of strings representing items to remove from the loot
removeall: if this is present then all items will be removed from the loot (before new items are added by this rule)

Experience

This is similar to loot control except that it controls how much experience you get from killing a mob. All keywords from loot control can be used here except the ones that are about damage type (magic, explosion, . ) as that information is not present in this event. There are four outputs that work for these rules:

result: set this to ‘deny’ to not give any experience at all
setxp: set a fixed XP instead of the default one
multxp: multiple the normal XP with this number
addxp: after multiplying the normal XP add this amount to the final XP

Commands

This mod has the following commands:

ctrlreload: after editing the rule files you can use this command to reload it and reapply the new rules
ctrldebug: dumps debug info about spawning in the log. Warning! This can produce a lot of output
ctrlshowmobs: show all entities and their names that can be used in spawn.json for mob names
ctrlkill: kill all entities of a given type. Possible types are: ‘all’, ‘hostile’, ‘passive’, or ‘entity’. It is also possible to give the name of an entity instead of a type. On 1.11 this would be ‘minecraft:enderman’ for example. On 1.10 ‘Enderman’. There is also an optional extra parameter for a dimension ID

Examples for spawn.json

Here are a few examples for spawn.json:

The first example allows only spawns in plains biomes. All other spawns are prevented:

This example prevents ALL passive mob spawns in a certain dimension:

Only allow creepers, skeletons and passive mobs:

Disallow hostile mob spawns above 50. Below 50 only allow spawns on stone and cobblestone:

Make all mobs on the surface very dangerous. Underground there is a small chance of spawning invisible but weak zombies. In addition zombies and skeleton on the surface spawn with helmets so they don’t burn:

Make all zombies slower but have more health:

Examples for potentialspawn.json

Here are some examples for potentialspawn.json:

This example makes blazes spawn in the overworld but only on netherack:

This examples removes all squid spawns everywhere and also adds extra iron golems in villages with a maximum of three:

Examples for joot.json

Here are some examples for loot.json:

Make blazes only spawn blaze rods if they are killed by a player in a nether fortress. The amount of blazerods will be higher if the looting level is higher:

Let the wither only drop a netherstar if it is killed with a stick:

In this example zombies will drop an enchanted diamond sword:

Источник

In control mod как настроить

In Control! mod — настройка мобов [1.16.5] [1.15.2] [1.12.2] [1.11.2] [1.10.2]

In Control! — настрой мобов, мод на изменение свойств и характеристик мобов в майнкрафт.

Как пользоваться модом In Control!:

In Control! mod — настройка мобов [1.16.5] [1.15.2] [1.12.2] [1.11.2] [1.10.2]

In Control! — настрой мобов, мод на изменение свойств и характеристик мобов в майнкрафт.

Как пользоваться модом In Control!:

InControl

Contents

Introduction

Spawn Control

Additional Spawns

Loot Control

Experience

Commands

Examples for spawn.json

Examples for potentialspawn.json

Examples for joot.json