http://coros.us/wiki/api.php?action=feedcontributions&feedformat=atom&user=Corosus 2026-08-05T05:01:58Z User contributions MediaWiki 1.26.3 http://coros.us/wiki/index.php?title=Zombie_Players&diff=70 2019-02-25T03:01:01Z

<p>Corosus: </p> <hr /> <div>== Make Zombie Players spawn naturally ==<br /> <br /> Open config/Zombie_Players.cfg and edit Spawning_spawnZombiePlayersNaturally to true.<br /> * You can also add more players names to spawn as zombie players by adding to the list for Spawning_playerNamesToUse<br /> <br /> == Calming your Zombie Player ==<br /> <br /> Zombie Players are just hungry, and you look delicious, but there are other things they can feed on.<br /> <br /> With some '''raw meat''', right click them or toss it on the ground for them to pickup, this will satisfy their hunger. You'll find they no longer try to bite you, for now... Some have observed they will remain calm for a '''few days'''. Perhaps they will stay calm longer if you feed them some more.<br /> <br /> If your zombie starts getting hungry and cranky, he'll start growling more and giving off anger particles, better '''feed him before he turns on you'''.<br /> <br /> You'll find they can be useful, and will '''attack other monsters''' to help protect you.<br /> <br /> Toss them some '''items and armor''' to help them survive better, this will also '''prevent them from despawning'''.<br /> <br /> They will regain some health on hit of a monster, and more on kill of a monster. They also heal very very slowly over time.<br /> <br /> They will avoid picking fights with mobs if their health is low. You'll know if their health is low by the '''redstone particles''' above their head constantly. '''Tossing them more meat will heal them'''.<br /> <br /> If the Zombie Player spawned from your death, they will hang around your spawn, but other naturally spawned ones will just wander.<br /> <br /> If you want to keep them in a general area, try '''right clicking them with a bed''', you'll see hearts appear, that means they will remain in that area as their home within '''16ish blocks'''. Another right click will extend it to '''32 blocks''', again for '''64 blocks''', then another click will '''remove their home area''' which shows as colored smoke, from there the cycle repeats with hearts again.<br /> <br /> Zombie too noisy? Right click them with an '''apple''' (because reasons), that should keep them quiet, do it again to make them noisy again.<br /> <br /> If they picked up an item you want back, '''right click them with rotten flesh''' and they will drop everything for you, be quick to grab it.<br /> <br /> === Summary ===<br /> <br /> * Calm and heal with raw meat<br /> * Calm zombies will attack other monsters if healthy<br /> * Toss weapon and armor to equip them<br /> * Right click with bed to set home, cycle is: home 16 range, home 32 range, home 64 range, remove home<br /> * Right click with apple to silence growls.<br /> * Right click with rotten flesh to force them to drop all items.</div>

Corosus http://coros.us/wiki/index.php?title=Zombie_Players&diff=69 2019-02-25T02:23:00Z

<p>Corosus: </p> <hr /> <div>== Calming your Zombie Player ==<br /> <br /> Zombie Players are just hungry, and you look delicious, but there are other things they can feed on.<br /> <br /> With some '''raw meat''', right click them or toss it on the ground for them to pickup, this will satisfy their hunger. You'll find they no longer try to bite you, for now... Some have observed they will remain calm for a '''few days'''. Perhaps they will stay calm longer if you feed them some more.<br /> <br /> If your zombie starts getting hungry and cranky, he'll start growling more and giving off anger particles, better '''feed him before he turns on you'''.<br /> <br /> You'll find they can be useful, and will '''attack other monsters''' to help protect you.<br /> <br /> Toss them some '''items and armor''' to help them survive better, this will also '''prevent them from despawning'''.<br /> <br /> They will regain some health on hit of a monster, and more on kill of a monster. They also heal very very slowly over time.<br /> <br /> They will avoid picking fights with mobs if their health is low. You'll know if their health is low by the '''redstone particles''' above their head constantly. '''Tossing them more meat will heal them'''.<br /> <br /> If the Zombie Player spawned from your death, they will hang around your spawn, but other naturally spawned ones will just wander.<br /> <br /> If you want to keep them in a general area, try '''right clicking them with a bed''', you'll see hearts appear, that means they will remain in that area as their home within '''16ish blocks'''. Another right click will extend it to '''32 blocks''', again for '''64 blocks''', then another click will '''remove their home area''' which shows as colored smoke, from there the cycle repeats with hearts again.<br /> <br /> Zombie too noisy? Right click them with an '''apple''' (because reasons), that should keep them quiet, do it again to make them noisy again.<br /> <br /> If they picked up an item you want back, '''right click them with rotten flesh''' and they will drop everything for you, be quick to grab it.<br /> <br /> === Summary ===<br /> <br /> * Calm and heal with raw meat<br /> * Calm zombies will attack other monsters if healthy<br /> * Toss weapon and armor to equip them<br /> * Right click with bed to set home, cycle is: home 16 range, home 32 range, home 64 range, remove home<br /> * Right click with apple to silence growls.<br /> * Right click with rotten flesh to force them to drop all items.</div>

Corosus http://coros.us/wiki/index.php?title=Zombie_Players&diff=68 2019-02-25T02:21:00Z

<p>Corosus: </p> <hr /> <div>== Calming your Zombie Player ==<br /> <br /> Zombie Players are just hungry, and you look delicious, but there are other things they can feed on.<br /> <br /> With some '''raw meat''', right click them or toss it on the ground for them to pickup, this will satisfy their hunger. You'll find they no longer try to bite you, for now... Some have observed they will remain calm for a '''few days'''. Perhaps they will stay calm longer if you feed them some more.<br /> <br /> If your zombie starts getting hungry and cranky, he'll start growling more and giving off anger particles, better '''feed him before he turns on you'''.<br /> <br /> You'll find they can be useful, and will '''attack other monsters''' to help protect you.<br /> <br /> Toss them some '''items and armor''' to help them survive better, this will also '''prevent them from despawning'''.<br /> <br /> They will regain some health on hit of a monster, and more on kill of a monster. They also heal very very slowly over time.<br /> <br /> They will avoid picking fights with mobs if their health is low. You'll know if their health is low by the '''redstone particles''' above their head constantly. '''Tossing them more meat will heal them'''.<br /> <br /> If the Zombie Player spawned from your death, they will hang around your spawn, but other naturally spawned ones will just wander.<br /> <br /> If you want to keep them in a general area, try '''right clicking them with a bed''', you'll see hearts appear, that means they will remain in that area as their home within '''16ish blocks'''. Another right click will extend it to '''32 blocks''', again for '''64 blocks''', then another click will '''remove their home area''' which shows as colored smoke, from there the cycle repeats with hearts again.<br /> <br /> Zombie too noisy? Right click them with some '''rotten flesh''' (because reasons), that should keep them quiet, do it again to make them noisy again.<br /> <br /> === Summary ===<br /> <br /> * Calm and heal with raw meat<br /> * Calm zombies will attack other monsters if healthy<br /> * Toss weapon and armor to equip them<br /> * Right click with bed to set home, cycle is: home 16 range, home 32 range, home 64 range, remove home<br /> * Right click with rotten flesh to silence growls.</div>

Corosus http://coros.us/wiki/index.php?title=Zombie_Players&diff=67 2019-02-25T02:19:33Z

<p>Corosus: </p> <hr /> <div>== Calming your Zombie Player ==<br /> <br /> Zombie Players are just hungry, and you look delicious, but there are other things they can feed on.<br /> <br /> With some '''raw meat''', right click them or toss it on the ground for them to pickup, this will satisfy their hunger. You'll find they no longer try to bite you, for now... Some have observed they will remain calm for a '''few days'''. Perhaps they will stay calm longer if you feed them some more.<br /> <br /> If your zombie starts getting hungry and cranky, he'll start growling more and giving off anger particles, better '''feed him before he turns on you'''.<br /> <br /> You'll find they can be useful, and will '''attack other monsters''' to help protect you.<br /> <br /> Toss them some '''items and armor''' to help them survive better.<br /> <br /> They will regain some health on hit of a monster, and more on kill of a monster. They also heal very very slowly over time.<br /> <br /> They will avoid picking fights with mobs if their health is low. You'll know if their health is low by the '''redstone particles''' above their head constantly. '''Tossing them more meat will heal them'''.<br /> <br /> If the Zombie Player spawned from your death, they will hang around your spawn, but other naturally spawned ones will just wander.<br /> <br /> If you want to keep them in a general area, try '''right clicking them with a bed''', you'll see hearts appear, that means they will remain in that area as their home within '''16ish blocks'''. Another right click will extend it to '''32 blocks''', again for '''64 blocks''', then another click will '''remove their home area''' which shows as colored smoke, from there the cycle repeats with hearts again.<br /> <br /> Zombie too noisy? Right click them with some '''rotten flesh''' (because reasons), that should keep them quiet, do it again to make them noisy again.<br /> <br /> === Summary ===<br /> <br /> * Calm and heal with raw meat<br /> * Toss weapon and armor to equip them<br /> * Right click with bed to set home, cycle is: home 16 range, home 32 range, home 64 range, remove home<br /> * Right click with rotten flesh to silence growls.</div>

Corosus http://coros.us/wiki/index.php?title=Zombie_Players&diff=66 2019-02-25T02:16:00Z

<p>Corosus: </p> <hr /> <div>== Calming your Zombie Player ==<br /> <br /> Zombie Players are just hungry, and you look delicious, but there are other things they can feed on.<br /> <br /> With some '''raw meat''', right click them or toss it on the ground for them to pickup, this will satisfy their hunger. You'll find they no longer try to bite you, for now... Some have observed they will remain calm for a '''few days'''. Perhaps they will stay calm longer if you feed them some more.<br /> <br /> If your zombie starts getting hungry and cranky, he'll start growling more and giving off anger particles, better feed him before he turns on you.<br /> <br /> You'll find they can be useful, and will attack other monsters to help protect you.<br /> <br /> Toss them some items and armor to help them survive better.<br /> <br /> They will regain some health on hit of a monster, and more on kill of a monster. They also heal very very slowly over time.<br /> <br /> They will avoid picking fights with mobs if their health is low. You'll know if their health is low by the redstone particles above their head constantly. Tossing them more meat will heal them.<br /> <br /> If the Zombie Player spawned from your death, they will hang around your spawn, but other naturally spawned ones will just wander.<br /> <br /> If you want to keep them in a general area, try right clicking them with a bed, you'll see hearts appear, that means they will remain in that area as their home within 16ish blocks. Another right click will extend it to 32 blocks, again for 64 blocks, then another click will remove their home area which shows as colored smoke, from there the cycle repeats with hearts again.<br /> <br /> Zombie too noisy? Right click them with some rotten flesh (because reasons), that should keep them quiet, do it again to make them noisy again.</div>

Corosus http://coros.us/wiki/index.php?title=Zombie_Players&diff=65 2019-02-25T02:08:35Z

<p>Corosus: Created page with &quot;== Calming your Zombie Player == Zombie Players are just hungry, and you look delicious, but there are other things they can feed on. With some '''raw meat''', right click t...&quot;</p> <hr /> <div>== Calming your Zombie Player ==<br /> <br /> Zombie Players are just hungry, and you look delicious, but there are other things they can feed on.<br /> <br /> With some '''raw meat''', right click them or toss it on the ground for them to pickup, this will satisfy their hunger. You'll find they no longer try to bite you, for now... Some have observed they will remain calm for a '''few days'''. Perhaps they will stay calm longer if you feed them some more.<br /> <br /> You'll find they can be useful, and will attack other monsters to help protect you.<br /> <br /> If the Zombie Player spawned from your death, they will hang around your spawn, but other naturally spawned ones will just wander.<br /> <br /> If you want to keep them in a general area, try right clicking them with a bed,</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=64 2019-02-03T02:14:42Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave templates or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> * TIP: use https://jsonlint.com/ to make sure your json syntax is correct.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> * The folder is empty, or<br /> * It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> I would recommend copying bits from these files to create and customize your invasions.<br /> <br /> === mob_spawns.json ===<br /> * Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> * Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> * Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> * The spawn profile defines a lot of things<br /> ** What to spawn<br /> ** How it spawns<br /> ** How many spawn<br /> ** What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json<br /> <br /> == Dynamic Local Difficulty ==<br /> <br /> CoroUtil has a local dynamic difficulty systems that tries its best to figure out what stage of the game the player is at, so it can ramp up difficulty along with them.<br /> <br /> Use of this system isn't actually required for invasions, but the default invasion setup uses it for scaling up inventory equipment, health, attack damage, speed, xp of mobs and also how many spawn in an invasion.<br /> <br /> If you want to tweak the default way the difficulty is setup, pop open config/CoroUtil/DynamicDifficulty.cfg<br /> <br /> Play with the configs prefixed with &quot;difficulty_&quot; or &quot;weight&quot; to change how much influence each type has on the average difficulty.<br /> <br /> To test this live in game, you can instead use the /config command to change the values, then run /coroutil difficulty to see the reflected result for your player.<br /> <br /> == Workflow of making and testing invasions ==<br /> <br /> First, do the &quot;Enable helpfull debug&quot; step in Testing Tips section below<br /> <br /> If you want to find a new mob to use from a mod:<br /> * /coroutil printEntities<br /> <br /> Lets use minecraft:husk for a simple example.<br /> <br /> Test a mob you found from the entities list:<br /> * /summon minecraft:husk<br /> * OR /coroutil spawn minecraft:husk<br /> <br /> Didn't crash? great! If it did crash, its probably a modded mob and you can't use that mob :(<br /> * TIP: open config/forge.cfg and set removeErroringEntities to true to save yourself from having to restart every entity crash while testing for ones that will work, be sure to read forges warning about using that setting in their config<br /> * If you use this setting, the entity should just dissapear if it has an issue, which also means you can't use it in an invasion.<br /> <br /> You can keep the game open and paused, we should never need to close it.<br /> <br /> Open up mob_spawns.json in text editor. I will edit the first mob spawn template to use this mob<br /> The first spawn profile is the zombie miner, I will leave that one alone and go down to the second mob spawn profile, that one is the zombie soldier.<br /> In the &quot;entities&quot; list there should be 1 entry, &quot;minecraft:zombie&quot;, lets change that to &quot;minecraft:husk&quot;<br /> <br /> Save the file, then in minecraft, run:<br /> * /coroutil reloadData<br /> * Make sure everything went ok in the console, check for json parse errors and fix anything needed.<br /> <br /> If you want, you can run:<br /> * /coroutil testProfile invasion_stage_1<br /> to see it print out the data for that template, you should see minecraft:husk used in there somewhere if it loaded in correctly.<br /> <br /> To see if your mob spawns with the setup ok, you can run: <br /> * /coroutil testSpawn invasion_stage_1<br /> you might have to run it a few times, as it will randomly choose a mob, so it will either spawn a zombie miner or a husk soldier.<br /> <br /> It should eventually spawn the husk soldier for you.<br /> <br /> Everything should work at this point for a real invasion if all the above worked correctly.<br /> <br /> To test an invasion, we can just set the time to when one should start.<br /> * Make sure you are in the overworld, on the surface for best results (caves will work but will be harder to find them)<br /> * /hw_invasions setPlayerTime 62000<br /> ** Need to fake a players playtime so an invasion will actually trigger now<br /> * /time set 62000<br /> ** default config has first invasion on the 3rd night, that time sets it to the 3rd night, adjust the time value as needed for your own config<br /> ** Since we modified the first invasion that is designed to be the only one run as the first invasion, your mob should be in this one.<br /> ** If you want to test a specific invasion mob spawn template see section &quot;Force specific mob spawn template&quot; in Testing Tips then do the time command above.<br /> <br /> You should get the invasion start message, look around for your husks, they should be there somewhere.<br /> <br /> Switch to survival mode to make sure they are targetting you and pathfinding to you, they wont in creative.<br /> <br /> If everything went well and you are satisfied, you can stop the invasion with:<br /> * /time set 0<br /> <br /> And kill off everything spawned with<br /> * /kill @e[type=!Player]<br /> <br /> And you're set! Start playing around and copying and pasting bits around and changing them up and retesting.<br /> <br /> I tend to use this workflow for fastest testing:<br /> * /hw_invasions setPlayerTime 62000<br /> ** Only need to run once per world<br /> * Edit json and save<br /> * /coroutil reloadData<br /> * /time set 0<br /> * /time set 62000<br /> * Find mobs, make sure setup how you want<br /> * Repeat all steps<br /> <br /> == Testing Tips ==<br /> <br /> === Enable helpfull debug output to diagnose potential problems in json === <br /> * in CoroUtil/General.cfg, set useLoggingDebug to true<br /> <br /> You will be able to see if there were any syntax errors with your json file, and where the error was, if everything went ok it should look like this:<br /> <br /> &lt;code&gt;processing, detected as DifficultyData: ./config/CoroUtil/data/templates/actions/mob_spawns.json<br /> <br /> [19:53:05] [main/INFO]: detected mob spawns to deserialize by detecting: mob_spawns&lt;/code&gt;<br /> <br /> === Live edit normal config options === <br /> * /config<br /> <br /> === Live reload data from the json files ingame === <br /> * /coroutil reloadData<br /> <br /> === See difficulty of area === <br /> * /coroutil difficulty<br /> <br /> === Print out a list of usable entities for invasions ===<br /> * /coroutil printEntities<br /> <br /> The printed entities SHOULD work, especially vanilla ones, but any modded entities you should always test, they could either not work, or worse, crash the game. A surprising amount of modded mobs like to crash the game if they aren't spawned in their own special way, that I cannot support without specifically accounting for them.<br /> <br /> Entities that work best are ones that walk on the ground, flying entities still need better support, and may never work because vanilla minecraft doesn't have a good standard for flying entities that modded entities could use, so every mod out there probably implemented their own way.<br /> <br /> === Test spawn a random mob from a specific mob spawn template ===<br /> * /coroutil testSpawn &lt;TEMPLATENAME&gt;<br /> * eg: /coroutil testSpawn invasion_stage_1<br /> <br /> === Test how your mob spawn template looks parsed ingame ===<br /> * /coroutil testProfile &lt;TEMPLATENAME&gt; &lt;DIFFICULTY&gt;<br /> * eg: /coroutil testProfile invasion_stage_1<br /> ** test with difficulty in current position for player<br /> * eg: /coroutil testProfile invasion_stage_1 0.5<br /> ** test with specific difficulty<br /> <br /> Will print out everything the game knows about your json setup, good for making sure everything loaded in as you expect.<br /> <br /> === Simulate the choosing of a mob spawn template and print out the results ===<br /> * /hw_invasions testInvasion &lt;DIFFICULTY&gt; &lt;WAVE NUMBER&gt;<br /> * both &lt;&gt; are optional, but if you want to specify &lt;WAVE NUMBER&gt; you must specify &lt;DIFFICULTY&gt; so it knows which is which<br /> * eg: /hw_invasions testInvasion 0.5 11<br /> ** Choose an invasion for difficulty 0.5 and wave count of 11<br /> <br /> Will print out the invasion mob spawn profile it chose.<br /> <br /> === Force specific mob spawn template for invasion to be used ===<br /> * in config/CoroUtil/General.cfg, set mobSpawnsWaveToForceUse to the name of your mob spawn template<br /> * eg: invasion_stage_1 or invasion_stage_3_opt_10_illagers<br /> <br /> === Reset dps calculations for 50 chunk area around you === <br /> * /coroutil resetDPS<br /> <br /> Probably not needed, but I've had issues with some situations causing super high DPS resulting in the difficulty being too high, mainly from mods. If you run into issues, use this, or disable DPS in the difficulty calculation, see Dynamic Local Difficulty wiki section for that.<br /> <br /> == Mob Grinders ==<br /> <br /> Mob grinder blocks or features from other mods have the potential to cause very high dps values which will throw the difficulty of an area off.<br /> A way to blacklist specific damage sources is in the works, but for now, if you think you might have this issue, you can limit the dps rating to a reasonable max:<br /> <br /> * In config/CoroUtil/General.cfg, Set enableAdvancedDeveloperConfigFiles to true<br /> * Restart game<br /> * In config/CoroUtil/Advanced.cfg, set difficulty_MaxDPSRatingAllowed to something lower than its default of 5, 1 is the theoretical vanilla max, so something like 2 might do.</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=63 2019-01-28T03:10:54Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave templates or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> * TIP: use https://jsonlint.com/ to make sure your json syntax is correct.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> * The folder is empty, or<br /> * It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> I would recommend copying bits from these files to create and customize your invasions.<br /> <br /> === mob_spawns.json ===<br /> * Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> * Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> * Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> * The spawn profile defines a lot of things<br /> ** What to spawn<br /> ** How it spawns<br /> ** How many spawn<br /> ** What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json<br /> <br /> == Dynamic Local Difficulty ==<br /> <br /> CoroUtil has a local dynamic difficulty systems that tries its best to figure out what stage of the game the player is at, so it can ramp up difficulty along with them.<br /> <br /> Use of this system isn't actually required for invasions, but the default invasion setup uses it for scaling up inventory equipment, health, attack damage, speed, xp of mobs and also how many spawn in an invasion.<br /> <br /> If you want to tweak the default way the difficulty is setup, pop open config/CoroUtil/DynamicDifficulty.cfg<br /> <br /> Play with the configs prefixed with &quot;difficulty_&quot; or &quot;weight&quot; to change how much influence each type has on the average difficulty.<br /> <br /> To test this live in game, you can instead use the /config command to change the values, then run /coroutil difficulty to see the reflected result for your player.<br /> <br /> == Workflow of making and testing invasions ==<br /> <br /> First, do the &quot;Enable helpfull debug&quot; step in Testing Tips section below<br /> <br /> If you want to find a new mob to use from a mod:<br /> * /coroutil printEntities<br /> <br /> Lets use minecraft:husk for a simple example.<br /> <br /> Test a mob you found from the entities list:<br /> * /summon minecraft:husk<br /> * OR /coroutil spawn minecraft:husk<br /> <br /> Didn't crash? great! If it did crash, its probably a modded mob and you can't use that mob :(<br /> * TIP: open config/forge.cfg and set removeErroringEntities to true to save yourself from having to restart every entity crash while testing for ones that will work, be sure to read forges warning about using that setting in their config<br /> * If you use this setting, the entity should just dissapear if it has an issue, which also means you can't use it in an invasion.<br /> <br /> You can keep the game open and paused, we should never need to close it.<br /> <br /> Open up mob_spawns.json in text editor. I will edit the first mob spawn template to use this mob<br /> The first spawn profile is the zombie miner, I will leave that one alone and go down to the second mob spawn profile, that one is the zombie soldier.<br /> In the &quot;entities&quot; list there should be 1 entry, &quot;minecraft:zombie&quot;, lets change that to &quot;minecraft:husk&quot;<br /> <br /> Save the file, then in minecraft, run:<br /> * /coroutil reloadData<br /> * Make sure everything went ok in the console, check for json parse errors and fix anything needed.<br /> <br /> If you want, you can run:<br /> * /coroutil testProfile invasion_stage_1<br /> to see it print out the data for that template, you should see minecraft:husk used in there somewhere if it loaded in correctly.<br /> <br /> To see if your mob spawns with the setup ok, you can run: <br /> * /coroutil testSpawn invasion_stage_1<br /> you might have to run it a few times, as it will randomly choose a mob, so it will either spawn a zombie miner or a husk soldier.<br /> <br /> It should eventually spawn the husk soldier for you.<br /> <br /> Everything should work at this point for a real invasion if all the above worked correctly.<br /> <br /> To test an invasion, we can just set the time to when one should start.<br /> * Make sure you are in the overworld, on the surface for best results (caves will work but will be harder to find them)<br /> * /hw_invasions setPlayerTime 62000<br /> ** Need to fake a players playtime so an invasion will actually trigger now<br /> * /time set 62000<br /> ** default config has first invasion on the 3rd night, that time sets it to the 3rd night, adjust the time value as needed for your own config<br /> ** Since we modified the first invasion that is designed to be the only one run as the first invasion, your mob should be in this one.<br /> ** If you want to test a specific invasion mob spawn template see section &quot;Force specific mob spawn template&quot; in Testing Tips then do the time command above.<br /> <br /> You should get the invasion start message, look around for your husks, they should be there somewhere.<br /> <br /> Switch to survival mode to make sure they are targetting you and pathfinding to you, they wont in creative.<br /> <br /> If everything went well and you are satisfied, you can stop the invasion with:<br /> * /time set 0<br /> <br /> And kill off everything spawned with<br /> * /kill @e[type=!Player]<br /> <br /> And you're set! Start playing around and copying and pasting bits around and changing them up and retesting.<br /> <br /> I tend to use this workflow for fastest testing:<br /> * /hw_invasions setPlayerTime 62000<br /> ** Only need to run once per world<br /> * Edit json and save<br /> * /coroutil reloadData<br /> * /time set 0<br /> * /time set 62000<br /> * Find mobs, make sure setup how you want<br /> * Repeat all steps<br /> <br /> == Testing Tips ==<br /> <br /> === Enable helpfull debug output to diagnose potential problems in json === <br /> * in CoroUtil/General.cfg, set useLoggingDebug to true<br /> <br /> You will be able to see if there were any syntax errors with your json file, and where the error was, if everything went ok it should look like this:<br /> <br /> &lt;code&gt;processing, detected as DifficultyData: ./config/CoroUtil/data/templates/actions/mob_spawns.json<br /> <br /> [19:53:05] [main/INFO]: detected mob spawns to deserialize by detecting: mob_spawns&lt;/code&gt;<br /> <br /> === Live edit normal config options === <br /> * /config<br /> <br /> === Live reload data from the json files ingame === <br /> * /coroutil reloadData<br /> <br /> === See difficulty of area === <br /> * /coroutil difficulty<br /> <br /> === Print out a list of usable entities for invasions ===<br /> * /coroutil printEntities<br /> <br /> The printed entities SHOULD work, especially vanilla ones, but any modded entities you should always test, they could either not work, or worse, crash the game. A surprising amount of modded mobs like to crash the game if they aren't spawned in their own special way, that I cannot support without specifically accounting for them.<br /> <br /> Entities that work best are ones that walk on the ground, flying entities still need better support, and may never work because vanilla minecraft doesn't have a good standard for flying entities that modded entities could use, so every mod out there probably implemented their own way.<br /> <br /> === Test spawn a random mob from a specific mob spawn template ===<br /> * /coroutil testSpawn &lt;TEMPLATENAME&gt;<br /> * eg: /coroutil testSpawn invasion_stage_1<br /> <br /> === Test how your mob spawn template looks parsed ingame ===<br /> * /coroutil testProfile &lt;TEMPLATENAME&gt; &lt;DIFFICULTY&gt;<br /> * eg: /coroutil testProfile invasion_stage_1<br /> ** test with difficulty in current position for player<br /> * eg: /coroutil testProfile invasion_stage_1 0.5<br /> ** test with specific difficulty<br /> <br /> Will print out everything the game knows about your json setup, good for making sure everything loaded in as you expect.<br /> <br /> === Simulate the choosing of a mob spawn template and print out the results ===<br /> * /hw_invasions testInvasion &lt;DIFFICULTY&gt; &lt;WAVE NUMBER&gt;<br /> * both &lt;&gt; are optional, but if you want to specify &lt;WAVE NUMBER&gt; you must specify &lt;DIFFICULTY&gt; so it knows which is which<br /> * eg: /hw_invasions testInvasion 0.5 11<br /> ** Choose an invasion for difficulty 0.5 and wave count of 11<br /> <br /> Will print out the invasion mob spawn profile it chose.<br /> <br /> === Force specific mob spawn template for invasion to be used ===<br /> * in config/CoroUtil/General.cfg, set mobSpawnsWaveToForceUse to the name of your mob spawn template<br /> * eg: invasion_stage_1 or invasion_stage_3_opt_10_illagers<br /> <br /> === Reset dps calculations for 50 chunk area around you === <br /> * /coroutil resetDPS<br /> <br /> Probably not needed, but I've had issues with some situations causing super high DPS resulting in the difficulty being too high, mainly from mods. If you run into issues, use this, or disable DPS in the difficulty calculation, see Dynamic Local Difficulty wiki section for that.</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=62 2019-01-27T04:49:13Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave templates or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> * The folder is empty, or<br /> * It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> I would recommend copying bits from these files to create and customize your invasions.<br /> <br /> === mob_spawns.json ===<br /> * Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> * Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> * Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> * The spawn profile defines a lot of things<br /> ** What to spawn<br /> ** How it spawns<br /> ** How many spawn<br /> ** What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json<br /> <br /> == Dynamic Local Difficulty ==<br /> <br /> CoroUtil has a local dynamic difficulty systems that tries its best to figure out what stage of the game the player is at, so it can ramp up difficulty along with them.<br /> <br /> Use of this system isn't actually required for invasions, but the default invasion setup uses it for scaling up inventory equipment, health, attack damage, speed, xp of mobs and also how many spawn in an invasion.<br /> <br /> If you want to tweak the default way the difficulty is setup, pop open config/CoroUtil/DynamicDifficulty.cfg<br /> <br /> Play with the configs prefixed with &quot;difficulty_&quot; or &quot;weight&quot; to change how much influence each type has on the average difficulty.<br /> <br /> To test this live in game, you can instead use the /config command to change the values, then run /coroutil difficulty to see the reflected result for your player.<br /> <br /> == Workflow of making and testing invasions ==<br /> <br /> First, do the &quot;Enable helpfull debug&quot; step in Testing Tips section below<br /> <br /> If you want to find a new mob to use from a mod:<br /> * /coroutil printEntities<br /> <br /> Lets use minecraft:husk for a simple example.<br /> <br /> Test a mob you found from the entities list:<br /> * /summon minecraft:husk<br /> * OR /coroutil spawn minecraft:husk<br /> <br /> Didn't crash? great! If it did crash, its probably a modded mob and you can't use that mob :(<br /> * TIP: open config/forge.cfg and set removeErroringEntities to true to save yourself from having to restart every entity crash while testing for ones that will work, be sure to read forges warning about using that setting in their config<br /> * If you use this setting, the entity should just dissapear if it has an issue, which also means you can't use it in an invasion.<br /> <br /> You can keep the game open and paused, we should never need to close it.<br /> <br /> Open up mob_spawns.json in text editor. I will edit the first mob spawn template to use this mob<br /> The first spawn profile is the zombie miner, I will leave that one alone and go down to the second mob spawn profile, that one is the zombie soldier.<br /> In the &quot;entities&quot; list there should be 1 entry, &quot;minecraft:zombie&quot;, lets change that to &quot;minecraft:husk&quot;<br /> <br /> Save the file, then in minecraft, run:<br /> * /coroutil reloadData<br /> * Make sure everything went ok in the console, check for json parse errors and fix anything needed.<br /> <br /> If you want, you can run:<br /> * /coroutil testProfile invasion_stage_1<br /> to see it print out the data for that template, you should see minecraft:husk used in there somewhere if it loaded in correctly.<br /> <br /> To see if your mob spawns with the setup ok, you can run: <br /> * /coroutil testSpawn invasion_stage_1<br /> you might have to run it a few times, as it will randomly choose a mob, so it will either spawn a zombie miner or a husk soldier.<br /> <br /> It should eventually spawn the husk soldier for you.<br /> <br /> Everything should work at this point for a real invasion if all the above worked correctly.<br /> <br /> To test an invasion, we can just set the time to when one should start.<br /> * Make sure you are in the overworld, on the surface for best results (caves will work but will be harder to find them)<br /> * /hw_invasions setPlayerTime 62000<br /> ** Need to fake a players playtime so an invasion will actually trigger now<br /> * /time set 62000<br /> ** default config has first invasion on the 3rd night, that time sets it to the 3rd night, adjust the time value as needed for your own config<br /> ** Since we modified the first invasion that is designed to be the only one run as the first invasion, your mob should be in this one.<br /> ** If you want to test a specific invasion mob spawn template see section &quot;Force specific mob spawn template&quot; in Testing Tips then do the time command above.<br /> <br /> You should get the invasion start message, look around for your husks, they should be there somewhere.<br /> <br /> Switch to survival mode to make sure they are targetting you and pathfinding to you, they wont in creative.<br /> <br /> If everything went well and you are satisfied, you can stop the invasion with:<br /> * /time set 0<br /> <br /> And kill off everything spawned with<br /> * /kill @e[type=!Player]<br /> <br /> And you're set! Start playing around and copying and pasting bits around and changing them up and retesting.<br /> <br /> I tend to use this workflow for fastest testing:<br /> * /hw_invasions setPlayerTime 62000<br /> ** Only need to run once per world<br /> * Edit json and save<br /> * /coroutil reloadData<br /> * /time set 0<br /> * /time set 62000<br /> * Find mobs, make sure setup how you want<br /> * Repeat all steps<br /> <br /> == Testing Tips ==<br /> <br /> === Enable helpfull debug output to diagnose potential problems in json === <br /> * in CoroUtil/General.cfg, set useLoggingDebug to true<br /> <br /> You will be able to see if there were any syntax errors with your json file, and where the error was, if everything went ok it should look like this:<br /> <br /> &lt;code&gt;processing, detected as DifficultyData: ./config/CoroUtil/data/templates/actions/mob_spawns.json<br /> <br /> [19:53:05] [main/INFO]: detected mob spawns to deserialize by detecting: mob_spawns&lt;/code&gt;<br /> <br /> === Live edit normal config options === <br /> * /config<br /> <br /> === Live reload data from the json files ingame === <br /> * /coroutil reloadData<br /> <br /> === See difficulty of area === <br /> * /coroutil difficulty<br /> <br /> === Print out a list of usable entities for invasions ===<br /> * /coroutil printEntities<br /> <br /> The printed entities SHOULD work, especially vanilla ones, but any modded entities you should always test, they could either not work, or worse, crash the game. A surprising amount of modded mobs like to crash the game if they aren't spawned in their own special way, that I cannot support without specifically accounting for them.<br /> <br /> Entities that work best are ones that walk on the ground, flying entities still need better support, and may never work because vanilla minecraft doesn't have a good standard for flying entities that modded entities could use, so every mod out there probably implemented their own way.<br /> <br /> === Test spawn a random mob from a specific mob spawn template ===<br /> * /coroutil testSpawn &lt;TEMPLATENAME&gt;<br /> * eg: /coroutil testSpawn invasion_stage_1<br /> <br /> === Test how your mob spawn template looks parsed ingame ===<br /> * /coroutil testProfile &lt;TEMPLATENAME&gt; &lt;DIFFICULTY&gt;<br /> * eg: /coroutil testProfile invasion_stage_1<br /> ** test with difficulty in current position for player<br /> * eg: /coroutil testProfile invasion_stage_1 0.5<br /> ** test with specific difficulty<br /> <br /> Will print out everything the game knows about your json setup, good for making sure everything loaded in as you expect.<br /> <br /> === Simulate the choosing of a mob spawn template and print out the results ===<br /> * /hw_invasions testInvasion &lt;DIFFICULTY&gt; &lt;WAVE NUMBER&gt;<br /> * both &lt;&gt; are optional, but if you want to specify &lt;WAVE NUMBER&gt; you must specify &lt;DIFFICULTY&gt; so it knows which is which<br /> * eg: /hw_invasions testInvasion 0.5 11<br /> ** Choose an invasion for difficulty 0.5 and wave count of 11<br /> <br /> Will print out the invasion mob spawn profile it chose.<br /> <br /> === Force specific mob spawn template for invasion to be used ===<br /> * in config/CoroUtil/General.cfg, set mobSpawnsWaveToForceUse to the name of your mob spawn template<br /> * eg: invasion_stage_1 or invasion_stage_3_opt_10_illagers<br /> <br /> === Reset dps calculations for 50 chunk area around you === <br /> * /coroutil resetDPS<br /> <br /> Probably not needed, but I've had issues with some situations causing super high DPS resulting in the difficulty being too high, mainly from mods. If you run into issues, use this, or disable DPS in the difficulty calculation, see Dynamic Local Difficulty wiki section for that.</div>

Corosus http://coros.us/wiki/index.php?title=Main_Page&diff=61 2019-01-27T04:33:56Z

<p>Corosus: </p> <hr /> <div>== Useful Links ==<br /> <br /> [//coros.us/wiki/index.php?title=Weather2_Main_Page Weather2]<br /> <br /> [//coros.us/wiki/index.php?title=Weather2_FAQ Weather2 FAQ]<br /> <br /> [https://coros.us/wiki/index.php?title=ZombieAwareness_Main_Page Zombie Awareness]<br /> <br /> [//coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions Hostile Worlds Invasion Main Info]<br /> <br /> [//coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing Customizing Hostile Worlds Invasions]</div>

Corosus http://coros.us/wiki/index.php?title=ZombieAwareness_Main_Page&diff=60 2019-01-27T04:33:27Z

<p>Corosus: </p> <hr /> <div>== Useful Links ==<br /> <br /> [//coros.us/mods/zombieawareness Mod Showcase and Download]<br /> <br /> [//coros.us/wiki/index.php?title=ZombieAwareness_FAQ Zombie Awareness FAQ]<br /> <br /> == How it works ==<br /> <br /> The mod makes it seem like mobs are aware of you more from the sounds you make or the smells you emit.<br /> <br /> When you perform certain actions like mining blocks or taking damage, the mod will spawn or buff an invisible &quot;sense&quot; entity that other mobs use to pathfind to. These decay over time to simulate the mobs eventually &quot;forgetting&quot; about it and caring more about the most recent senses.<br /> <br /> The current actions that trigger senses are:<br /> * Block breaking<br /> * Taking damage (configurable)<br /> ** Shows blood splatter on the ground<br /> * Having low health (as if you are bleeding over time)<br /> * Arrows hitting/shooting<br /> * Explosions<br /> * Chests and doors opening and closing<br /> * Buttons, Levers, Pressure plates being used<br /> * Pistons activating (can be heard from far, configurable)<br /> * Zombies growling (configurable)<br /> * Being near light sources they can see (configurable)<br /> <br /> You can enable or disable sound based triggers as a whole in Features.cfg<br /> <br /> If you want to see what is making sound senses ingame, turn on client_debugSensesVisual in ClientConfig.cfg<br /> <br /> You can decide what mobs are enhanced with all this extra awareness by editing MobLlists.cfg<br /> * As noted in the cfg file, won't work for all mobs if they arent using ground pathfinding or if a modded mob does its own special ways of ground pathfinding.<br /> <br /> === Other small features ===<br /> <br /> * Mobs make investigation and agression noises when they are pathing to you or see you<br /> * Random speed boost to mobs on spawn (configurable via General.cfg)<br /> * Spawns extra clusters of mobs at night from an existing zombie if its far enough away from you, (configurable via maxZombiesNight in Spawning.cfg)<br /> * Turns off baby zombies and random chance of re-enforcement feature (configurable via Features.cfg)<br /> <br /> == Extra features default off in config ==<br /> <br /> * Extra mob spawning on surface<br /> ** Turn on with extraSpawningSurface in Features.cfg, more detailed choices in Spawning.cfg<br /> <br /> * Extra mob spawning in caves<br /> ** Turn on with extraSpawningCave in Features.cfg, more detailed choices in Spawning.cfg<br /> <br /> * Mob Omniscience<br /> ** Turn on in General.cfg<br /> <br /> * Mobs See through walls<br /> ** Turn on in General.cfg</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions&diff=59 2019-01-27T04:30:34Z

<p>Corosus: </p> <hr /> <div>If you want to customize the mod, go here: [http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing Customizing Hostile Worlds Invasions]<br /> <br /> Otherwise not much info here yet, go here for the mods showcase [https://coros.us/mods/hostileworldsinvasions https://coros.us/mods/hostileworldsinvasions]</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions&diff=58 2019-01-27T04:30:15Z

<p>Corosus: Created page with &quot;If you want to customize the mod, go here: [http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing Customizing Hostile Worlds Invasions] Otherwise no m...&quot;</p> <hr /> <div>If you want to customize the mod, go here: [http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing Customizing Hostile Worlds Invasions]<br /> <br /> Otherwise no much info here yet, go here for the mods showcase [https://coros.us/mods/hostileworldsinvasions https://coros.us/mods/hostileworldsinvasions]</div>

Corosus http://coros.us/wiki/index.php?title=Main_Page&diff=57 2019-01-27T04:26:30Z

<p>Corosus: </p> <hr /> <div>== Useful Links ==<br /> <br /> [//coros.us/wiki/index.php?title=Weather2_Main_Page Weather2]<br /> <br /> [//coros.us/wiki/index.php?title=Weather2_FAQ Weather2 FAQ]<br /> <br /> [//coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions Hostile Worlds Invasion Main Info]<br /> <br /> [//coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing Customizing Hostile Worlds Invasions]</div>

Corosus http://coros.us/wiki/index.php?title=Main_Page&diff=56 2019-01-27T04:24:34Z

<p>Corosus: </p> <hr /> <div>:o<br /> <br /> == Useful Links ==<br /> <br /> [//coros.us/wiki/index.php?title=Weather2_Main_Page]<br /> <br /> [//coros.us/wiki/index.php?title=Weather2_FAQ Weather2 FAQ]<br /> <br /> [//coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions]<br /> <br /> [//coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing]</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=55 2019-01-27T01:49:25Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave profiles or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> * The folder is empty, or<br /> * It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> I would recommend copying bits from these files to create and customize your invasions.<br /> <br /> === mob_spawns.json ===<br /> * Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> * Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> * Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> * The spawn profile defines a lot of things<br /> ** What to spawn<br /> ** How it spawns<br /> ** How many spawn<br /> ** What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json<br /> <br /> == Dynamic Local Difficulty ==<br /> <br /> CoroUtil has a local dynamic difficulty systems that tries its best to figure out what stage of the game the player is at, so it can ramp up difficulty along with them.<br /> <br /> Use of this system isn't actually required for invasions, but the default invasion setup uses it for scaling up inventory equipment, health, attack damage, speed, xp of mobs and also how many spawn in an invasion.<br /> <br /> If you want to tweak the default way the difficulty is setup, pop open config/CoroUtil/DynamicDifficulty.cfg<br /> <br /> Play with the configs prefixed with &quot;difficulty_&quot; or &quot;weight&quot; to change how much influence each type has on the average difficulty.<br /> <br /> To test this live in game, you can instead use the /config command to change the values, then run /coroutil difficulty to see the reflected result for your player.<br /> <br /> == Workflow of making and testing invasions ==<br /> <br /> First, do the &quot;Enable helpfull debug&quot; step in Testing Tips section below<br /> <br /> If you want to find a new mob to use from a mod:<br /> * /coroutil printEntities<br /> <br /> Lets use minecraft:husk for a simple example.<br /> <br /> Test a mob you found from the entities list:<br /> * /summon minecraft:husk<br /> * OR /coroutil spawn minecraft:husk<br /> <br /> Didn't crash? great! If it did crash, its probably a modded mob and you can't use that mob :(<br /> * TIP: open config/forge.cfg and set removeErroringEntities to true to save yourself from having to restart every entity crash while testing for ones that will work, be sure to read forges warning about using that setting in their config<br /> * If you use this setting, the entity should just dissapear if it has an issue, which also means you can't use it in an invasion.<br /> <br /> You can keep the game open and paused, we should never need to close it.<br /> <br /> Open up mob_spawns.json in text editor. I will edit the first mob spawn template to use this mob<br /> The first spawn profile is the zombie miner, I will leave that one alone and go down to the second mob spawn profile, that one is the zombie soldier.<br /> In the &quot;entities&quot; list there should be 1 entry, &quot;minecraft:zombie&quot;, lets change that to &quot;minecraft:husk&quot;<br /> <br /> Save the file, then in minecraft, run:<br /> * /coroutil reloadData<br /> * Make sure everything went ok in the console, check for json parse errors and fix anything needed.<br /> <br /> If you want, you can run:<br /> * /coroutil testProfile invasion_stage_1<br /> to see it print out the data for that template, you should see minecraft:husk used in there somewhere if it loaded in correctly.<br /> <br /> To see if your mob spawns with the setup ok, you can run: <br /> * /coroutil testSpawn invasion_stage_1<br /> you might have to run it a few times, as it will randomly choose a mob, so it will either spawn a zombie miner or a husk soldier.<br /> <br /> It should eventually spawn the husk soldier for you.<br /> <br /> Everything should work at this point for a real invasion if all the above worked correctly.<br /> <br /> To test an invasion, we can just set the time to when one should start.<br /> * Make sure you are in the overworld, on the surface for best results (caves will work but will be harder to find them)<br /> * /hw_invasions setPlayerTime 62000<br /> ** Need to fake a players playtime so an invasion will actually trigger now<br /> * /time set 62000<br /> ** default config has first invasion on the 3rd night, that time sets it to the 3rd night, adjust the time value as needed for your own config<br /> ** Since we modified the first invasion that is designed to be the only one run as the first invasion, your mob should be in this one.<br /> ** If you want to test a specific invasion mob spawn template see section &quot;Force specific mob spawn template&quot; in Testing Tips then do the time command above.<br /> <br /> You should get the invasion start message, look around for your husks, they should be there somewhere.<br /> <br /> Switch to survival mode to make sure they are targetting you and pathfinding to you, they wont in creative.<br /> <br /> If everything went well and you are satisfied, you can stop the invasion with:<br /> * /time set 0<br /> <br /> And kill off everything spawned with<br /> * /kill @e[type=!Player]<br /> <br /> And you're set! Start playing around and copying and pasting bits around and changing them up and retesting.<br /> <br /> I tend to use this workflow for fastest testing:<br /> * /hw_invasions setPlayerTime 62000<br /> ** Only need to run once per world<br /> * Edit json and save<br /> * /coroutil reloadData<br /> * /time set 0<br /> * /time set 62000<br /> * Find mobs, make sure setup how you want<br /> * Repeat all steps<br /> <br /> == Testing Tips ==<br /> <br /> === Enable helpfull debug output to diagnose potential problems in json === <br /> * in CoroUtil/General.cfg, set useLoggingDebug to true<br /> <br /> You will be able to see if there were any syntax errors with your json file, and where the error was, if everything went ok it should look like this:<br /> <br /> &lt;code&gt;processing, detected as DifficultyData: ./config/CoroUtil/data/templates/actions/mob_spawns.json<br /> <br /> [19:53:05] [main/INFO]: detected mob spawns to deserialize by detecting: mob_spawns&lt;/code&gt;<br /> <br /> === Live edit normal config options === <br /> * /config<br /> <br /> === Live reload data from the json files ingame === <br /> * /coroutil reloadData<br /> <br /> === See difficulty of area === <br /> * /coroutil difficulty<br /> <br /> === Print out a list of usable entities for invasions ===<br /> * /coroutil printEntities<br /> <br /> The printed entities SHOULD work, especially vanilla ones, but any modded entities you should always test, they could either not work, or worse, crash the game. A surprising amount of modded mobs like to crash the game if they aren't spawned in their own special way, that I cannot support without specifically accounting for them.<br /> <br /> Entities that work best are ones that walk on the ground, flying entities still need better support, and may never work because vanilla minecraft doesn't have a good standard for flying entities that modded entities could use, so every mod out there probably implemented their own way.<br /> <br /> === Test spawn a random mob from a specific mob spawn template ===<br /> * /coroutil testSpawn &lt;TEMPLATENAME&gt;<br /> * eg: /coroutil testSpawn invasion_stage_1<br /> <br /> === Test how your mob spawn template looks parsed ingame ===<br /> * /coroutil testProfile &lt;TEMPLATENAME&gt; &lt;DIFFICULTY&gt;<br /> * eg: /coroutil testProfile invasion_stage_1<br /> ** test with difficulty in current position for player<br /> * eg: /coroutil testProfile invasion_stage_1 0.5<br /> ** test with specific difficulty<br /> <br /> Will print out everything the game knows about your json setup, good for making sure everything loaded in as you expect.<br /> <br /> === Simulate the choosing of a mob spawn template and print out the results ===<br /> * /hw_invasions testInvasion &lt;DIFFICULTY&gt; &lt;WAVE NUMBER&gt;<br /> * both &lt;&gt; are optional, but if you want to specify &lt;WAVE NUMBER&gt; you must specify &lt;DIFFICULTY&gt; so it knows which is which<br /> * eg: /hw_invasions testInvasion 0.5 11<br /> ** Choose an invasion for difficulty 0.5 and wave count of 11<br /> <br /> Will print out the invasion mob spawn profile it chose.<br /> <br /> === Force specific mob spawn template for invasion to be used ===<br /> * in config/CoroUtil/General.cfg, set mobSpawnsWaveToForceUse to the name of your mob spawn template<br /> * eg: invasion_stage_1 or invasion_stage_3_opt_10_illagers<br /> <br /> === Reset dps calculations for 50 chunk area around you === <br /> * /coroutil resetDPS<br /> <br /> Probably not needed, but I've had issues with some situations causing super high DPS resulting in the difficulty being too high, mainly from mods. If you run into issues, use this, or disable DPS in the difficulty calculation, see Dynamic Local Difficulty wiki section for that.</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=54 2019-01-27T00:37:41Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave profiles or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> * The folder is empty, or<br /> * It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> I would recommend copying bits from these files to create and customize your invasions.<br /> <br /> === mob_spawns.json ===<br /> * Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> * Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> * Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> * The spawn profile defines a lot of things<br /> ** What to spawn<br /> ** How it spawns<br /> ** How many spawn<br /> ** What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json<br /> <br /> == Dynamic Local Difficulty ==<br /> <br /> CoroUtil has a local dynamic difficulty systems that tries its best to figure out what stage of the game the player is at, so it can ramp up difficulty along with them.<br /> <br /> Use of this system isn't actually required for invasions, but the default invasion setup uses it for scaling up inventory equipment, health, attack damage, speed, xp of mobs and also how many spawn in an invasion.<br /> <br /> If you want to tweak the default way the difficulty is setup, pop open config/CoroUtil/DynamicDifficulty.cfg<br /> <br /> Play with the configs prefixed with &quot;difficulty_&quot; or &quot;weight&quot; to change how much influence each type has on the average difficulty.<br /> <br /> To test this live in game, you can instead use the /config command to change the values, then run /coroutil difficulty to see the reflected result for your player.<br /> <br /> == Workflow of making and testing invasions ==<br /> <br /> First, do the &quot;Enable helpfull debug&quot; step in Testing Tips section below<br /> <br /> If you want to find a new mob to use from a mod:<br /> * /coroutil printEntities<br /> <br /> Lets use minecraft:husk for a simple example.<br /> <br /> Test a mob you found from the entities list:<br /> * /summon minecraft:husk<br /> * OR /coroutil spawn minecraft:husk<br /> <br /> Didn't crash? great! If it did crash, its probably a modded mob and you can't use that mob :(<br /> ** TIP: open config/forge.cfg and set removeErroringEntities to true to save yourself from having to restart every entity crash while testing for ones that will work, be sure to read forges warning about using that setting in their config<br /> ** If you use this setting, the entity should just dissapear if it has an issue, which also means you can't use it in an invasion.<br /> <br /> You can keep the game open and paused, we should never need to close it.<br /> <br /> Open up mob_spawns.json in text editor. I will edit the first mob spawn template to use this mob<br /> The first spawn profile is the zombie miner, I will leave that one alone and go down to the second mob spawn profile, that one is the zombie soldier.<br /> In the &quot;entities&quot; list there should be 1 entry, &quot;minecraft:zombie&quot;, lets change that to &quot;minecraft:husk&quot;<br /> <br /> Save the file, then in minecraft, run:<br /> * /coroutil reloadData<br /> * Make sure everything went ok in the console, check for json parse errors and fix anything needed.<br /> <br /> If you want, you can run:<br /> * /coroutil testProfile invasion_stage_1<br /> to see it print out the data for that template, you should see minecraft:husk used in there somewhere if it loaded in correctly.<br /> <br /> To see if your mob spawns with the setup ok, you can run: <br /> * /coroutil testSpawn invasion_stage_1<br /> you might have to run it a few times, as it will randomly choose a mob, so it will either spawn a zombie miner or a husk soldier.<br /> <br /> It should eventually spawn the husk soldier for you.<br /> <br /> Everything should work at this point for a real invasion if all the above worked correctly.<br /> <br /> To test an invasion, we can just set the time to when one should start.<br /> * Make sure you are in the overworld, on the surface for best results (caves will work but will be harder to find them)<br /> * /hw_invasions setPlayerTime 62000<br /> ** Need to fake a players playtime so an invasion will actually trigger now<br /> * /time set 62000<br /> ** default config has first invasion on the 3rd night, that time sets it to the 3rd night, adjust the time value as needed for your own config<br /> ** Since we modified the first invasion that is designed to be the only one run as the first invasion, your mob should be in this one.<br /> ** If you want to test a specific invasion mob spawn template see section &quot;Force specific mob spawn template&quot; in Testing Tips then do the time command above.<br /> <br /> You should get the invasion start message, look around for your husks, they should be there somewhere.<br /> <br /> Switch to survival mode to make sure they are targetting you and pathfinding to you, they wont in creative.<br /> <br /> If everything went well and you are satisfied, you can stop the invasion with:<br /> * /time set 0<br /> <br /> And kill off everything spawned with<br /> * /kill @e[type=!Player]<br /> <br /> And you're set! Start playing around and copying and pasting bits around and changing them up and retesting.<br /> <br /> I tend to use this workflow for fastest testing:<br /> * /hw_invasions setPlayerTime 62000<br /> ** Only need to run once per world<br /> * Edit json and save<br /> * /coroutil reloadData<br /> * /time set 0<br /> * /time set 62000<br /> * Find mobs, make sure setup how you want<br /> * Repeat all steps<br /> <br /> == Testing Tips ==<br /> <br /> === Enable helpfull debug output to diagnose potential problems in json === <br /> * in CoroUtil/General.cfg, set useLoggingDebug to true<br /> <br /> You will be able to see if there were any syntax errors with your json file, and where the error was, if everything went ok it should look like this:<br /> <br /> &lt;code&gt;processing, detected as DifficultyData: ./config/CoroUtil/data/templates/actions/mob_spawns.json<br /> <br /> [19:53:05] [main/INFO]: detected mob spawns to deserialize by detecting: mob_spawns&lt;/code&gt;<br /> <br /> === Live edit normal config options === <br /> * /config<br /> <br /> === Live reload data from the json files ingame === <br /> * /coroutil reloadData<br /> <br /> === See difficulty of area === <br /> * /coroutil difficulty<br /> <br /> === Print out a list of usable entities for invasions ===<br /> * /coroutil printEntities<br /> <br /> The printed entities SHOULD work, especially vanilla ones, but any modded entities you should always test, they could either not work, or worse, crash the game. A surprising amount of modded mobs like to crash the game if they aren't spawned in their own special way, that I cannot support without specifically accounting for them.<br /> <br /> Entities that work best are ones that walk on the ground, flying entities still need better support, and may never work because vanilla minecraft doesn't have a good standard for flying entities that modded entities could use, so every mod out there probably implemented their own way.<br /> <br /> === Test spawn a random mob from a specific mob spawn template ===<br /> * /coroutil testSpawn &lt;TEMPLATENAME&gt;<br /> * eg: /coroutil testSpawn invasion_stage_1<br /> <br /> === Test how your mob spawn template looks parsed ingame ===<br /> * /coroutil testProfile &lt;TEMPLATENAME&gt; &lt;DIFFICULTY&gt;<br /> * eg: /coroutil testProfile invasion_stage_1<br /> ** test with difficulty in current position for player<br /> * eg: /coroutil testProfile invasion_stage_1 0.5<br /> ** test with specific difficulty<br /> <br /> Will print out everything the game knows about your json setup, good for making sure everything loaded in as you expect.<br /> <br /> === Simulate the choosing of a mob spawn template and print out the results ===<br /> * /hw_invasions testInvasion &lt;DIFFICULTY&gt; &lt;WAVE NUMBER&gt;<br /> * both &lt;&gt; are optional, but if you want to specify &lt;WAVE NUMBER&gt; you must specify &lt;DIFFICULTY&gt; so it knows which is which<br /> * eg: /hw_invasions testInvasion 0.5 11<br /> ** Choose an invasion for difficulty 0.5 and wave count of 11<br /> <br /> Will print out the invasion mob spawn profile it chose.<br /> <br /> === Force specific mob spawn template for invasion to be used ===<br /> * in config/CoroUtil/General.cfg, set mobSpawnsWaveToForceUse to the name of your mob spawn template<br /> * eg: invasion_stage_1 or invasion_stage_3_opt_10_illagers<br /> <br /> === Reset dps calculations for 50 chunk area around you === <br /> * /coroutil resetDPS<br /> <br /> Probably not needed, but I've had issues with some situations causing super high DPS resulting in the difficulty being too high, mainly from mods. If you run into issues, use this, or disable DPS in the difficulty calculation, see Dynamic Local Difficulty wiki section for that.</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=53 2019-01-25T18:46:11Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave profiles or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> * The folder is empty, or<br /> * It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> I would recommend copying bits from these files to create and customize your invasions.<br /> <br /> === mob_spawns.json ===<br /> * Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> * Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> * Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> * The spawn profile defines a lot of things<br /> ** What to spawn<br /> ** How it spawns<br /> ** How many spawn<br /> ** What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json<br /> <br /> == Dynamic Local Difficulty ==<br /> <br /> CoroUtil has a local dynamic difficulty systems that tries its best to figure out what stage of the game the player is at, so it can ramp up difficulty along with them.<br /> <br /> Use of this system isn't actually required for invasions, but the default invasion setup uses it for scaling up inventory equipment, health, attack damage, speed, xp of mobs and also how many spawn in an invasion.<br /> <br /> If you want to tweak the default way the difficulty is setup, pop open config/CoroUtil/DynamicDifficulty.cfg<br /> <br /> Play with the configs prefixed with &quot;difficulty_&quot; or &quot;weight&quot; to change how much influence each type has on the average difficulty.<br /> <br /> To test this live in game, you can instead use the /config command to change the values, then run /coroutil difficulty to see the reflected result for your player.<br /> <br /> == Workflow of making and testing invasions ==<br /> <br /> First, do the &quot;Enable helpfull debug&quot; step in Testing Tips section below<br /> <br /> If you want to find a new mob to use from a mod:<br /> * /coroutil printEntities<br /> <br /> Lets use minecraft:husk for a simple example.<br /> <br /> Test a mob you found from the entities list:<br /> * /summon minecraft:husk<br /> * OR /coroutil spawn minecraft:husk<br /> <br /> Didn't crash? great! If it did crash, its probably a modded mob and you can't use that mob :(<br /> <br /> You can keep the game open and paused, we should never need to close it.<br /> <br /> Open up mob_spawns.json in text editor. I will edit the first mob spawn template to use this mob<br /> The first spawn profile is the zombie miner, I will leave that one alone and go down to the second mob spawn profile, that one is the zombie soldier.<br /> In the &quot;entities&quot; list there should be 1 entry, &quot;minecraft:zombie&quot;, lets change that to &quot;minecraft:husk&quot;<br /> <br /> Save the file, then in minecraft, run:<br /> * /coroutil reloadData<br /> * Make sure everything went ok in the console, check for json parse errors and fix anything needed.<br /> <br /> If you want, you can run:<br /> * /coroutil testProfile invasion_stage_1<br /> to see it print out the data for that template, you should see minecraft:husk used in there somewhere if it loaded in correctly.<br /> <br /> To see if your mob spawns with the setup ok, you can run: <br /> * /coroutil testSpawn invasion_stage_1<br /> you might have to run it a few times, as it will randomly choose a mob, so it will either spawn a zombie miner or a husk soldier.<br /> <br /> It should eventually spawn the husk soldier for you.<br /> <br /> Everything should work at this point for a real invasion if all the above worked correctly.<br /> <br /> To test an invasion, we can just set the time to when one should start.<br /> * Make sure you are in the overworld, on the surface for best results (caves will work but will be harder to find them)<br /> * /hw_invasions setPlayerTime 62000<br /> ** Need to fake a players playtime so an invasion will actually trigger now<br /> * /time set 62000<br /> ** default config has first invasion on the 3rd night, that time sets it to the 3rd night, adjust the time value as needed for your own config<br /> ** Since we modified the first invasion that is designed to be the only one run as the first invasion, your mob should be in this one.<br /> ** If you want to test a specific invasion mob spawn template see section &quot;Force specific mob spawn template&quot; in Testing Tips then do the time command above.<br /> <br /> You should get the invasion start message, look around for your husks, they should be there somewhere.<br /> <br /> Switch to survival mode to make sure they are targetting you and pathfinding to you, they wont in creative.<br /> <br /> If everything went well and you are satisfied, you can stop the invasion with:<br /> * /time set 0<br /> <br /> And kill off everything spawned with<br /> * /kill @e[type=!Player]<br /> <br /> And you're set! Start playing around and copying and pasting bits around and changing them up and retesting.<br /> <br /> I tend to use this workflow for fastest testing:<br /> * /hw_invasions setPlayerTime 62000<br /> ** Only need to run once per world<br /> * Edit json and save<br /> * /coroutil reloadData<br /> * /time set 0<br /> * /time set 62000<br /> * Find mobs, make sure setup how you want<br /> * Repeat all steps<br /> <br /> == Testing Tips ==<br /> <br /> === Enable helpfull debug output to diagnose potential problems in json === <br /> * in CoroUtil/General.cfg, set useLoggingDebug to true<br /> <br /> You will be able to see if there were any syntax errors with your json file, and where the error was, if everything went ok it should look like this:<br /> <br /> &lt;code&gt;processing, detected as DifficultyData: ./config/CoroUtil/data/templates/actions/mob_spawns.json<br /> <br /> [19:53:05] [main/INFO]: detected mob spawns to deserialize by detecting: mob_spawns&lt;/code&gt;<br /> <br /> === Live edit normal config options === <br /> * /config<br /> <br /> === Live reload data from the json files ingame === <br /> * /coroutil reloadData<br /> <br /> === See difficulty of area === <br /> * /coroutil difficulty<br /> <br /> === Print out a list of usable entities for invasions ===<br /> * /coroutil printEntities<br /> <br /> The printed entities SHOULD work, especially vanilla ones, but any modded entities you should always test, they could either not work, or worse, crash the game. A surprising amount of modded mobs like to crash the game if they aren't spawned in their own special way, that I cannot support without specifically accounting for them.<br /> <br /> Entities that work best are ones that walk on the ground, flying entities still need better support, and may never work because vanilla minecraft doesn't have a good standard for flying entities that modded entities could use, so every mod out there probably implemented their own way.<br /> <br /> === Test spawn a random mob from a specific mob spawn template ===<br /> * /coroutil testSpawn &lt;TEMPLATENAME&gt;<br /> * eg: /coroutil testSpawn invasion_stage_1<br /> <br /> === Test how your mob spawn template looks parsed ingame ===<br /> * /coroutil testProfile &lt;TEMPLATENAME&gt; &lt;DIFFICULTY&gt;<br /> * eg: /coroutil testProfile invasion_stage_1<br /> ** test with difficulty in current position for player<br /> * eg: /coroutil testProfile invasion_stage_1 0.5<br /> ** test with specific difficulty<br /> <br /> Will print out everything the game knows about your json setup, good for making sure everything loaded in as you expect.<br /> <br /> === Simulate the choosing of a mob spawn template and print out the results ===<br /> * /hw_invasions testInvasion &lt;DIFFICULTY&gt; &lt;WAVE NUMBER&gt;<br /> * both &lt;&gt; are optional, but if you want to specify &lt;WAVE NUMBER&gt; you must specify &lt;DIFFICULTY&gt; so it knows which is which<br /> * eg: /hw_invasions testInvasion 0.5 11<br /> ** Choose an invasion for difficulty 0.5 and wave count of 11<br /> <br /> Will print out the invasion mob spawn profile it chose.<br /> <br /> === Force specific mob spawn template for invasion to be used ===<br /> * in config/CoroUtil/General.cfg, set mobSpawnsWaveToForceUse to the name of your mob spawn template<br /> * eg: invasion_stage_1 or invasion_stage_3_opt_10_illagers<br /> <br /> === Reset dps calculations for 50 chunk area around you === <br /> * /coroutil resetDPS<br /> <br /> Probably not needed, but I've had issues with some situations causing super high DPS resulting in the difficulty being too high, mainly from mods. If you run into issues, use this, or disable DPS in the difficulty calculation, see Dynamic Local Difficulty wiki section for that.</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=52 2019-01-24T03:01:04Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave profiles or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> * The folder is empty, or<br /> * It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> I would recommend copying bits from these files to create and customize your invasions.<br /> <br /> === mob_spawns.json ===<br /> * Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> * Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> * Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> * The spawn profile defines a lot of things<br /> ** What to spawn<br /> ** How it spawns<br /> ** How many spawn<br /> ** What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json<br /> <br /> == Dynamic Local Difficulty ==<br /> <br /> CoroUtil has a local dynamic difficulty systems that tries its best to figure out what stage of the game the player is at, so it can ramp up difficulty along with them.<br /> <br /> Use of this system isn't actually required for invasions, but the default invasion setup uses it for scaling up inventory equipment, health, attack damage, speed, xp of mobs and also how many spawn in an invasion.<br /> <br /> If you want to tweak the default way the difficulty is setup, pop open config/CoroUtil/DynamicDifficulty.cfg<br /> <br /> Play with the configs prefixed with &quot;difficulty_&quot; or &quot;weight&quot; to change how much influence each type has on the average difficulty.<br /> <br /> To test this live in game, you can instead use the /config command to change the values, then run /coroutil difficulty to see the reflected result for your player.<br /> <br /> == Workflow of making and testing invasions ==<br /> <br /> First, do the &quot;Enable helpfull debug&quot; step in Testing Tips section below<br /> <br /> If you want to find a new mob to use from a mod:<br /> * /coroutil printEntities<br /> <br /> Lets use minecraft:husk for a simple example.<br /> <br /> Test a mob you found from the entities list:<br /> * /summon minecraft:husk<br /> * OR /coroutil spawn minecraft:husk<br /> <br /> Didn't crash? great! If it did crash, its probably a modded mob and you can't use that mob :(<br /> <br /> You can keep the game open and paused, we should never need to close it.<br /> <br /> Open up mob_spawns.json in text editor. I will edit the first mob spawn template to use this mob<br /> The first spawn profile is the zombie miner, I will leave that one alone and go down to the second mob spawn profile, that one is the zombie soldier.<br /> In the &quot;entities&quot; list there should be 1 entry, &quot;minecraft:zombie&quot;, lets change that to &quot;minecraft:husk&quot;<br /> <br /> Save the file, then in minecraft, run:<br /> * /coroutil reloadData<br /> * Make sure everything went ok in the console, check for json parse errors and fix anything needed.<br /> <br /> If you want, you can run:<br /> * /coroutil testProfile invasion_stage_1<br /> to see it print out the data for that template, you should see minecraft:husk used in there somewhere if it loaded in correctly.<br /> <br /> To see if your mob spawns with the setup ok, you can run: <br /> * /coroutil testSpawn invasion_stage_1<br /> you might have to run it a few times, as it will randomly choose a mob, so it will either spawn a zombie miner or a husk soldier.<br /> <br /> It should eventually spawn the husk soldier for you.<br /> <br /> Everything should work at this point for a real invasion if all the above worked correctly.<br /> <br /> To test an invasion, we can just set the time to when one should start.<br /> * Make sure you are in the overworld, on the surface for best results (caves will work but will be harder to find them)<br /> * /time set 62000<br /> ** default config has first invasion on the 3rd night, that time sets it to the 3rd night, adjust the time value as needed for your own config<br /> ** Since we modified the first invasion that is designed to be the only one run as the first invasion, your mob should be in this one.<br /> ** If you want to test a specific invasion mob spawn template see section &quot;Force specific mob spawn template&quot; in Testing Tips then do the time command above.<br /> <br /> You should get the invasion start message, look around for your husks, they should be there somewhere.<br /> <br /> Switch to survival mode to make sure they are targetting you and pathfinding to you, they wont in creative.<br /> <br /> If everything went well and you are satisfied, you can stop the invasion with:<br /> * /time set 0<br /> <br /> And kill off everything spawned with<br /> * /kill @e[type=!Player]<br /> <br /> And you're set! Start playing around and copying and pasting bits around and changing them up and retesting.<br /> <br /> I tend to use this workflow for fastest testing:<br /> * Edit json and save<br /> * /coroutil reloadData<br /> * /time set 0<br /> * /time set 62000<br /> * Find mobs, make sure setup how you want<br /> * Repeat all steps<br /> <br /> == Testing Tips ==<br /> <br /> === Enable helpfull debug output to diagnose potential problems in json === <br /> * in CoroUtil/General.cfg, set useLoggingDebug to true<br /> <br /> You will be able to see if there were any syntax errors with your json file, and where the error was, if everything went ok it should look like this:<br /> <br /> &lt;code&gt;processing, detected as DifficultyData: ./config/CoroUtil/data/templates/actions/mob_spawns.json<br /> <br /> [19:53:05] [main/INFO]: detected mob spawns to deserialize by detecting: mob_spawns&lt;/code&gt;<br /> <br /> === Live edit normal config options === <br /> * /config<br /> <br /> === Live reload data from the json files ingame === <br /> * /coroutil reloadData<br /> <br /> === See difficulty of area === <br /> * /coroutil difficulty<br /> <br /> === Print out a list of usable entities for invasions ===<br /> * /coroutil printEntities<br /> <br /> The printed entities SHOULD work, especially vanilla ones, but any modded entities you should always test, they could either not work, or worse, crash the game. A surprising amount of modded mobs like to crash the game if they aren't spawned in their own special way, that I cannot support without specifically accounting for them.<br /> <br /> Entities that work best are ones that walk on the ground, flying entities still need better support, and may never work because vanilla minecraft doesn't have a good standard for flying entities that modded entities could use, so every mod out there probably implemented their own way.<br /> <br /> === Test spawn a random mob from a specific mob spawn template ===<br /> * /coroutil testSpawn &lt;TEMPLATENAME&gt;<br /> * eg: /coroutil testSpawn invasion_stage_1<br /> <br /> === Test how your mob spawn template looks parsed ingame ===<br /> * /coroutil testProfile &lt;TEMPLATENAME&gt; &lt;DIFFICULTY&gt;<br /> * eg: /coroutil testProfile invasion_stage_1<br /> ** test with difficulty in current position for player<br /> * eg: /coroutil testProfile invasion_stage_1 0.5<br /> ** test with specific difficulty<br /> <br /> Will print out everything the game knows about your json setup, good for making sure everything loaded in as you expect.<br /> <br /> === Simulate the choosing of a mob spawn template and print out the results ===<br /> * /hw_invasions testInvasion &lt;DIFFICULTY&gt; &lt;WAVE NUMBER&gt;<br /> * both &lt;&gt; are optional, but if you want to specify &lt;WAVE NUMBER&gt; you must specify &lt;DIFFICULTY&gt; so it knows which is which<br /> * eg: /hw_invasions testInvasion 0.5 11<br /> ** Choose an invasion for difficulty 0.5 and wave count of 11<br /> <br /> Will print out the invasion mob spawn profile it chose.<br /> <br /> === Force specific mob spawn template for invasion to be used ===<br /> * in config/CoroUtil/General.cfg, set mobSpawnsWaveToForceUse to the name of your mob spawn template<br /> * eg: invasion_stage_1 or invasion_stage_3_opt_10_illagers<br /> <br /> === Reset dps calculations for 50 chunk area around you === <br /> * /coroutil resetDPS<br /> <br /> Probably not needed, but I've had issues with some situations causing super high DPS resulting in the difficulty being too high, mainly from mods. If you run into issues, use this, or disable DPS in the difficulty calculation, see Dynamic Local Difficulty wiki section for that.</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=51 2019-01-24T02:57:21Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave profiles or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> * The folder is empty, or<br /> * It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> I would recommend copying bits from these files to create and customize your invasions.<br /> <br /> === mob_spawns.json ===<br /> * Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> * Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> * Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> * The spawn profile defines a lot of things<br /> ** What to spawn<br /> ** How it spawns<br /> ** How many spawn<br /> ** What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json<br /> <br /> == Dynamic Local Difficulty ==<br /> <br /> CoroUtil has a local dynamic difficulty systems that tries its best to figure out what stage of the game the player is at, so it can ramp up difficulty along with them.<br /> <br /> Use of this system isn't actually required for invasions, but the default invasion setup uses it for scaling up inventory equipment, health, attack damage, speed, xp of mobs and also how many spawn in an invasion.<br /> <br /> If you want to tweak the default way the difficulty is setup, pop open config/CoroUtil/DynamicDifficulty.cfg<br /> <br /> Play with the configs prefixed with &quot;difficulty_&quot; or &quot;weight&quot; to change how much influence each type has on the average difficulty.<br /> <br /> To test this live in game, you can instead use the /config command to change the values, then run /coroutil difficulty to see the reflected result for your player.<br /> <br /> == Workflow of making and testing invasions ==<br /> <br /> First, do the &quot;Enable helpfull debug&quot; step in Testing Tips section below<br /> <br /> If you want to find a new mob to use from a mod:<br /> * /coroutil printEntities<br /> <br /> Lets use minecraft:husk for a simple example.<br /> <br /> Test a mob you found from the entities list:<br /> * /summon minecraft:husk<br /> * OR /coroutil spawn minecraft:husk<br /> <br /> Didn't crash? great! If it did crash, its probably a modded mob and you can't use that mob :(<br /> <br /> You can keep the game open and paused, we should never need to close it.<br /> <br /> Open up mob_spawns.json in text editor. I will edit the first mob spawn template to use this mob<br /> The first spawn profile is the zombie miner, I will leave that one alone and go down to the second mob spawn profile, that one is the zombie soldier.<br /> In the &quot;entities&quot; list there should be 1 entry, &quot;minecraft:zombie&quot;, lets change that to &quot;minecraft:husk&quot;<br /> <br /> Save the file, then in minecraft, run:<br /> * /coroutil reloadData<br /> * Make sure everything went ok in the console, check for json parse errors and fix anything needed.<br /> <br /> If you want, you can run:<br /> * /coroutil testProfile invasion_stage_1<br /> to see it print out the data for that template, you should see minecraft:husk used in there somewhere if it loaded in correctly.<br /> <br /> To see if your mob spawns with the setup ok, you can run: <br /> * /coroutil testSpawn invasion_stage_1<br /> you might have to run it a few times, as it will randomly choose a mob, so it will either spawn a zombie miner or a husk soldier.<br /> <br /> It should eventually spawn the husk soldier for you.<br /> <br /> Everything should work at this point for a real invasion if all the above worked correctly.<br /> <br /> To test an invasion, we can just set the time to when one should start.<br /> * Make sure you are in the overworld, on the surface for best results (caves will work but will be harder to find them)<br /> * /time set 62000<br /> ** default config has first invasion on the 3rd night, that time sets it to the 3rd night, adjust the time value as needed for your own config<br /> ** Since we modified the first invasion that is designed to be the only one run as the first invasion, your mob should be in this one.<br /> ** If you want to test a specific invasion mob spawn template see section &quot;Force specific mob spawn template&quot; in Testing Tips then do the time command above.<br /> <br /> You should get the invasion start message, look around for your husks, they should be there somewhere.<br /> <br /> Switch to survival mode to make sure they are targetting you and pathfinding to you, they wont in creative.<br /> <br /> == Testing Tips ==<br /> <br /> === Enable helpfull debug output to diagnose potential problems in json === <br /> * in CoroUtil/General.cfg, set useLoggingDebug to true<br /> <br /> You will be able to see if there were any syntax errors with your json file, and where the error was, if everything went ok it should look like this:<br /> <br /> &lt;code&gt;processing, detected as DifficultyData: ./config/CoroUtil/data/templates/actions/mob_spawns.json<br /> <br /> [19:53:05] [main/INFO]: detected mob spawns to deserialize by detecting: mob_spawns&lt;/code&gt;<br /> <br /> === Live edit normal config options === <br /> * /config<br /> <br /> === Live reload data from the json files ingame === <br /> * /coroutil reloadData<br /> <br /> === See difficulty of area === <br /> * /coroutil difficulty<br /> <br /> === Print out a list of usable entities for invasions ===<br /> * /coroutil printEntities<br /> <br /> The printed entities SHOULD work, especially vanilla ones, but any modded entities you should always test, they could either not work, or worse, crash the game. A surprising amount of modded mobs like to crash the game if they aren't spawned in their own special way, that I cannot support without specifically accounting for them.<br /> <br /> Entities that work best are ones that walk on the ground, flying entities still need better support, and may never work because vanilla minecraft doesn't have a good standard for flying entities that modded entities could use, so every mod out there probably implemented their own way.<br /> <br /> === Test spawn a random mob from a specific mob spawn template ===<br /> * /coroutil testSpawn &lt;TEMPLATENAME&gt;<br /> * eg: /coroutil testSpawn invasion_stage_1<br /> <br /> === Test how your mob spawn template looks parsed ingame ===<br /> * /coroutil testProfile &lt;TEMPLATENAME&gt; &lt;DIFFICULTY&gt;<br /> * eg: /coroutil testProfile invasion_stage_1<br /> ** test with difficulty in current position for player<br /> * eg: /coroutil testProfile invasion_stage_1 0.5<br /> ** test with specific difficulty<br /> <br /> Will print out everything the game knows about your json setup, good for making sure everything loaded in as you expect.<br /> <br /> === Simulate the choosing of a mob spawn template and print out the results ===<br /> * /hw_invasions testInvasion &lt;DIFFICULTY&gt; &lt;WAVE NUMBER&gt;<br /> * both &lt;&gt; are optional, but if you want to specify &lt;WAVE NUMBER&gt; you must specify &lt;DIFFICULTY&gt; so it knows which is which<br /> * eg: /hw_invasions testInvasion 0.5 11<br /> ** Choose an invasion for difficulty 0.5 and wave count of 11<br /> <br /> Will print out the invasion mob spawn profile it chose.<br /> <br /> === Force specific mob spawn template for invasion to be used ===<br /> * in config/CoroUtil/General.cfg, set mobSpawnsWaveToForceUse to the name of your mob spawn template<br /> * eg: invasion_stage_1 or invasion_stage_3_opt_10_illagers<br /> <br /> === Reset dps calculations for 50 chunk area around you === <br /> * /coroutil resetDPS<br /> <br /> Probably not needed, but I've had issues with some situations causing super high DPS resulting in the difficulty being too high, mainly from mods. If you run into issues, use this, or disable DPS in the difficulty calculation, see Dynamic Local Difficulty wiki section for that.</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=50 2019-01-24T02:56:46Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave profiles or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> * The folder is empty, or<br /> * It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> I would recommend copying bits from these files to create and customize your invasions.<br /> <br /> === mob_spawns.json ===<br /> * Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> * Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> * Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> * The spawn profile defines a lot of things<br /> ** What to spawn<br /> ** How it spawns<br /> ** How many spawn<br /> ** What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json<br /> <br /> == Dynamic Local Difficulty ==<br /> <br /> CoroUtil has a local dynamic difficulty systems that tries its best to figure out what stage of the game the player is at, so it can ramp up difficulty along with them.<br /> <br /> Use of this system isn't actually required for invasions, but the default invasion setup uses it for scaling up inventory equipment, health, attack damage, speed, xp of mobs and also how many spawn in an invasion.<br /> <br /> If you want to tweak the default way the difficulty is setup, pop open config/CoroUtil/DynamicDifficulty.cfg<br /> <br /> Play with the configs prefixed with &quot;difficulty_&quot; or &quot;weight&quot; to change how much influence each type has on the average difficulty.<br /> <br /> To test this live in game, you can instead use the /config command to change the values, then run /coroutil difficulty to see the reflected result for your player.<br /> <br /> == Workflow of making and testing invasions ==<br /> <br /> First, do the &quot;Enable helpfull debug&quot; step in Testing Tips section below<br /> <br /> If you want to find a new mob to use from a mod:<br /> * /coroutil printentities<br /> <br /> Lets use minecraft:husk for a simple example.<br /> <br /> Test a mob you found from the entities list:<br /> * /summon minecraft:husk<br /> * OR /coroutil spawn minecraft:husk<br /> <br /> Didn't crash? great! If it did crash, its probably a modded mob and you can't use that mob :(<br /> <br /> You can keep the game open and paused, we should never need to close it.<br /> <br /> Open up mob_spawns.json in text editor. I will edit the first mob spawn template to use this mob<br /> The first spawn profile is the zombie miner, I will leave that one alone and go down to the second mob spawn profile, that one is the zombie soldier.<br /> In the &quot;entities&quot; list there should be 1 entry, &quot;minecraft:zombie&quot;, lets change that to &quot;minecraft:husk&quot;<br /> <br /> Save the file, then in minecraft, run:<br /> * /coroutil reloadData<br /> * Make sure everything went ok in the console, check for json parse errors and fix anything needed.<br /> <br /> If you want, you can run:<br /> * /coroutil testProfile invasion_stage_1<br /> to see it print out the data for that template, you should see minecraft:husk used in there somewhere if it loaded in correctly.<br /> <br /> To see if your mob spawns with the setup ok, you can run: <br /> * /coroutil testSpawn invasion_stage_1<br /> you might have to run it a few times, as it will randomly choose a mob, so it will either spawn a zombie miner or a husk soldier.<br /> <br /> It should eventually spawn the husk soldier for you.<br /> <br /> Everything should work at this point for a real invasion if all the above worked correctly.<br /> <br /> To test an invasion, we can just set the time to when one should start.<br /> * Make sure you are in the overworld, on the surface for best results (caves will work but will be harder to find them)<br /> * /time set 62000<br /> ** default config has first invasion on the 3rd night, that time sets it to the 3rd night, adjust the time value as needed for your own config<br /> ** Since we modified the first invasion that is designed to be the only one run as the first invasion, your mob should be in this one.<br /> ** If you want to test a specific invasion mob spawn template see section &quot;Force specific mob spawn template&quot; in Testing Tips then do the time command above.<br /> <br /> You should get the invasion start message, look around for your husks, they should be there somewhere.<br /> <br /> Switch to survival mode to make sure they are targetting you and pathfinding to you, they wont in creative.<br /> <br /> == Testing Tips ==<br /> <br /> === Enable helpfull debug output to diagnose potential problems in json === <br /> * in CoroUtil/General.cfg, set useLoggingDebug to true<br /> <br /> You will be able to see if there were any syntax errors with your json file, and where the error was, if everything went ok it should look like this:<br /> <br /> &lt;code&gt;processing, detected as DifficultyData: ./config/CoroUtil/data/templates/actions/mob_spawns.json<br /> <br /> [19:53:05] [main/INFO]: detected mob spawns to deserialize by detecting: mob_spawns&lt;/code&gt;<br /> <br /> === Live edit normal config options === <br /> * /config<br /> <br /> === Live reload data from the json files ingame === <br /> * /coroutil reloadData<br /> <br /> === See difficulty of area === <br /> * /coroutil difficulty<br /> <br /> === Print out a list of usable entities for invasions ===<br /> * /coroutil printEntities<br /> <br /> The printed entities SHOULD work, especially vanilla ones, but any modded entities you should always test, they could either not work, or worse, crash the game. A surprising amount of modded mobs like to crash the game if they aren't spawned in their own special way, that I cannot support without specifically accounting for them.<br /> <br /> Entities that work best are ones that walk on the ground, flying entities still need better support, and may never work because vanilla minecraft doesn't have a good standard for flying entities that modded entities could use, so every mod out there probably implemented their own way.<br /> <br /> === Test spawn a random mob from a specific mob spawn template ===<br /> * /coroutil testSpawn &lt;TEMPLATENAME&gt;<br /> * eg: /coroutil testSpawn invasion_stage_1<br /> <br /> === Test how your mob spawn template looks parsed ingame ===<br /> * /coroutil testProfile &lt;TEMPLATENAME&gt; &lt;DIFFICULTY&gt;<br /> * eg: /coroutil testProfile invasion_stage_1<br /> ** test with difficulty in current position for player<br /> * eg: /coroutil testProfile invasion_stage_1 0.5<br /> ** test with specific difficulty<br /> <br /> Will print out everything the game knows about your json setup, good for making sure everything loaded in as you expect.<br /> <br /> === Simulate the choosing of a mob spawn template and print out the results ===<br /> * /hw_invasions testInvasion &lt;DIFFICULTY&gt; &lt;WAVE NUMBER&gt;<br /> * both &lt;&gt; are optional, but if you want to specify &lt;WAVE NUMBER&gt; you must specify &lt;DIFFICULTY&gt; so it knows which is which<br /> * eg: /hw_invasions testInvasion 0.5 11<br /> ** Choose an invasion for difficulty 0.5 and wave count of 11<br /> <br /> Will print out the invasion mob spawn profile it chose.<br /> <br /> === Force specific mob spawn template for invasion to be used ===<br /> * in config/CoroUtil/General.cfg, set mobSpawnsWaveToForceUse to the name of your mob spawn template<br /> * eg: invasion_stage_1 or invasion_stage_3_opt_10_illagers<br /> <br /> === Reset dps calculations for 50 chunk area around you === <br /> * /coroutil resetDPS<br /> <br /> Probably not needed, but I've had issues with some situations causing super high DPS resulting in the difficulty being too high, mainly from mods. If you run into issues, use this, or disable DPS in the difficulty calculation, see Dynamic Local Difficulty wiki section for that.</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=49 2019-01-24T02:39:48Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave profiles or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> * The folder is empty, or<br /> * It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> I would recommend copying bits from these files to create and customize your invasions.<br /> <br /> === mob_spawns.json ===<br /> * Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> * Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> * Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> * The spawn profile defines a lot of things<br /> ** What to spawn<br /> ** How it spawns<br /> ** How many spawn<br /> ** What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json<br /> <br /> == Dynamic Local Difficulty ==<br /> <br /> CoroUtil has a local dynamic difficulty systems that tries its best to figure out what stage of the game the player is at, so it can ramp up difficulty along with them.<br /> <br /> Use of this system isn't actually required for invasions, but the default invasion setup uses it for scaling up inventory equipment, health, attack damage, speed, xp of mobs and also how many spawn in an invasion.<br /> <br /> If you want to tweak the default way the difficulty is setup, pop open config/CoroUtil/DynamicDifficulty.cfg<br /> <br /> Play with the configs prefixed with &quot;difficulty_&quot; or &quot;weight&quot; to change how much influence each type has on the average difficulty.<br /> <br /> To test this live in game, you can instead use the /config command to change the values, then run /coroutil difficulty to see the reflected result for your player.<br /> <br /> == Workflow of making and testing invasions ==<br /> <br /> First, do the &quot;Enable helpfull debug&quot; step in Testing Tips section below<br /> <br /> If you want to find a new mob to use from a mod:<br /> * /coroutil printentities<br /> <br /> Test a mob you found from the entities list:<br /> * /summon zombie_players:zombie_player<br /> * OR /coroutil spawn zombie_players:zombie_player<br /> <br /> Didn't crash? great! If it did crash, you can't use that mob :(<br /> <br /> You can keep the game open and paused, we should never need to close it.<br /> <br /> Open up mob_spawns.json in text editor. I will edit the first mob spawn template to use this mob<br /> The first spawn profile is the zombie miner, I will leave that one alone and go down to the second mob spawn profile, that one is the zombie soldier.<br /> In the &quot;entities&quot; list there should be 1 entry, &quot;minecraft:zombie&quot;, lets change that to &quot;zombie_players:zombie_player&quot;<br /> <br /> Save the file, then in minecraft, run:<br /> * /coroutil reloadData<br /> * Make sure everything went ok in the console, check for json parse errors and fix anything needed.<br /> <br /> == Testing Tips ==<br /> <br /> === Enable helpfull debug output to diagnose potential problems in json === <br /> * in CoroUtil/General.cfg, set useLoggingDebug to true<br /> <br /> You will be able to see if there were any syntax errors with your json file, and where the error was, if everything went ok it should look like this:<br /> <br /> &lt;code&gt;processing, detected as DifficultyData: ./config/CoroUtil/data/templates/actions/mob_spawns.json<br /> <br /> [19:53:05] [main/INFO]: detected mob spawns to deserialize by detecting: mob_spawns&lt;/code&gt;<br /> <br /> === Live edit normal config options === <br /> * /config<br /> <br /> === Live reload data from the json files ingame === <br /> * /coroutil reloadData<br /> <br /> === See difficulty of area === <br /> * /coroutil difficulty<br /> <br /> === Print out a list of usable entities for invasions ===<br /> * /coroutil printEntities<br /> <br /> The printed entities SHOULD work, especially vanilla ones, but any modded entities you should always test, they could either not work, or worse, crash the game. A surprising amount of modded mobs like to crash the game if they aren't spawned in their own special way, that I cannot support without specifically accounting for them.<br /> <br /> Entities that work best are ones that walk on the ground, flying entities still need better support, and may never work because vanilla minecraft doesn't have a good standard for flying entities that modded entities could use, so every mod out there probably implemented their own way.<br /> <br /> === Test spawn a random mob from a specific mob spawn template ===<br /> * /coroutil testSpawn &lt;TEMPLATENAME&gt;<br /> * eg: /coroutil testSpawn invasion_stage_1<br /> <br /> === Test how your mob spawn template looks parsed ingame ===<br /> * /coroutil testProfile &lt;TEMPLATENAME&gt; &lt;DIFFICULTY&gt;<br /> * eg: /coroutil testProfile invasion_stage_1<br /> ** test with difficulty in current position for player<br /> * eg: /coroutil testProfile invasion_stage_1 0.5<br /> ** test with specific difficulty<br /> <br /> Will print out everything the game knows about your json setup, good for making sure everything loaded in as you expect.<br /> <br /> === Simulate the choosing of a mob spawn template and print out the results ===<br /> * /hw_invasions testInvasion &lt;DIFFICULTY&gt; &lt;WAVE NUMBER&gt;<br /> * both &lt;&gt; are optional, but if you want to specify &lt;WAVE NUMBER&gt; you must specify &lt;DIFFICULTY&gt; so it knows which is which<br /> * eg: /hw_invasions testInvasion 0.5 11<br /> ** Choose an invasion for difficulty 0.5 and wave count of 11<br /> <br /> Will print out the invasion mob spawn profile it chose.<br /> <br /> === Force specific mob spawn profile for invasion to be used ===<br /> * in config/CoroUtil/General.cfg, set mobSpawnsWaveToForceUse to the name of your mob spawn profile<br /> * eg: invasion_stage_1 or invasion_stage_3_opt_10_illagers<br /> <br /> === Reset dps calculations for 50 chunk area around you === <br /> * /coroutil resetDPS<br /> <br /> Probably not needed, but I've had issues with some situations causing super high DPS resulting in the difficulty being too high, mainly from mods. If you run into issues, use this, or disable DPS in the difficulty calculation, see Dynamic Local Difficulty wiki section for that.</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=48 2019-01-24T02:37:02Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave profiles or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> * The folder is empty, or<br /> * It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> I would recommend copying bits from these files to create and customize your invasions.<br /> <br /> === mob_spawns.json ===<br /> * Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> * Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> * Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> * The spawn profile defines a lot of things<br /> ** What to spawn<br /> ** How it spawns<br /> ** How many spawn<br /> ** What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json<br /> <br /> == Dynamic Local Difficulty ==<br /> <br /> CoroUtil has a local dynamic difficulty systems that tries its best to figure out what stage of the game the player is at, so it can ramp up difficulty along with them.<br /> <br /> Use of this system isn't actually required for invasions, but the default invasion setup uses it for scaling up inventory equipment, health, attack damage, speed, xp of mobs and also how many spawn in an invasion.<br /> <br /> If you want to tweak the default way the difficulty is setup, pop open config/CoroUtil/DynamicDifficulty.cfg<br /> <br /> Play with the configs prefixed with &quot;difficulty_&quot; or &quot;weight&quot; to change how much influence each type has on the average difficulty.<br /> <br /> To test this live in game, you can instead use the /config command to change the values, then run /coroutil difficulty to see the reflected result for your player.<br /> <br /> == Workflow of making and testing invasions ==<br /> <br /> First, do the &quot;Enable helpfull debug&quot; step in Testing Tips section below<br /> <br /> If you want to find a new mob to use from a mod:<br /> * /coroutil printentities<br /> <br /> Test a mob you found from the entities list:<br /> * /summon zombie_players:zombie_player<br /> * OR /coroutil spawn zombie_players:zombie_player<br /> <br /> Didn't crash? great! If it did crash, you can't use that mob :(<br /> <br /> You can keep the game open and paused, we should never need to close it.<br /> <br /> Open up mob_spawns.json in text editor. I will edit the first mob spawn template to use this mob<br /> The first spawn profile is the zombie miner, I will leave that one alone and go down to the second mob spawn profile, that one is the zombie soldier.<br /> In the &quot;entities&quot; list there should be 1 entry, &quot;minecraft:zombie&quot;, lets change that to &quot;zombie_players:zombie_player&quot;<br /> <br /> Save the file, then in minecraft, run:<br /> * /coroutil reloadData<br /> * Make sure everything went ok in the console, check for json parse errors and fix anything needed.<br /> <br /> == Testing Tips ==<br /> <br /> === Enable helpfull debug output to diagnose potential problems in json === <br /> * in CoroUtil/General.cfg, set useLoggingDebug to true<br /> <br /> You will be able to see if there were any syntax errors with your json file, and where the error was, if everything went ok it should look like this:<br /> <br /> &lt;code&gt;processing, detected as DifficultyData: ./config/CoroUtil/data/templates/actions/mob_spawns.json<br /> <br /> [19:53:05] [main/INFO]: detected mob spawns to deserialize by detecting: mob_spawns&lt;/code&gt;<br /> <br /> === Live edit normal config options === <br /> * /config<br /> <br /> === Live reload data from the json files ingame === <br /> * /coroutil reloadData<br /> <br /> === See difficulty of area === <br /> * /coroutil difficulty<br /> <br /> === Print out a list of usable entities for invasions ===<br /> * /coroutil printEntities<br /> <br /> The printed entities SHOULD work, especially vanilla ones, but any modded entities you should always test, they could either not work, or worse, crash the game. A surprising amount of modded mobs like to crash the game if they aren't spawned in their own special way, that I cannot support without specifically accounting for them.<br /> <br /> Entities that work best are ones that walk on the ground, flying entities still need better support, and may never work because vanilla minecraft doesn't have a good standard for flying entities that modded entities could use, so every mod out there probably implemented their own way.<br /> <br /> === Test spawn a random mob from a specific mob spawn template ===<br /> * /coroutil testSpawn &lt;TEMPLATENAME&gt;<br /> * eg: /coroutil testSpawn invasion_stage_1<br /> <br /> === Test how your mob spawn template looks parsed ingame ===<br /> * /coroutil testProfile &lt;TEMPLATENAME&gt; &lt;DIFFICULTY&gt;<br /> * eg: /coroutil testProfile invasion_stage_1<br /> ** test with difficulty in current position for player<br /> * eg: /coroutil testProfile invasion_stage_1 0.5<br /> ** test with specific difficulty<br /> <br /> === Simulate the choosing of a mob spawn template ===<br /> * /hw_invasions testInvasion &lt;DIFFICULTY&gt; &lt;WAVE NUMBER&gt;<br /> * both &lt;&gt; are optional<br /> <br /> Will print out everything the game knows about your json setup, good for making sure everything loaded in as you expect<br /> <br /> === Force specific mob spawn profile for invasion to be used ===<br /> * in config/CoroUtil/General.cfg, set mobSpawnsWaveToForceUse to the name of your mob spawn profile<br /> * eg: invasion_stage_1 or invasion_stage_3_opt_10_illagers<br /> <br /> === Reset dps calculations for 50 chunk area around you === <br /> * /coroutil resetDPS<br /> <br /> Probably not needed, but I've had issues with some situations causing super high DPS resulting in the difficulty being too high, mainly from mods. If you run into issues, use this, or disable DPS in the difficulty calculation, see Dynamic Local Difficulty wiki section for that.</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=47 2019-01-24T02:17:31Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave profiles or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> * The folder is empty, or<br /> * It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> I would recommend copying bits from these files to create and customize your invasions.<br /> <br /> === mob_spawns.json ===<br /> * Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> * Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> * Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> * The spawn profile defines a lot of things<br /> ** What to spawn<br /> ** How it spawns<br /> ** How many spawn<br /> ** What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json<br /> <br /> == Dynamic Local Difficulty ==<br /> <br /> CoroUtil has a local dynamic difficulty systems that tries its best to figure out what stage of the game the player is at, so it can ramp up difficulty along with them.<br /> <br /> Use of this system isn't actually required for invasions, but the default invasion setup uses it for scaling up inventory equipment, health, attack damage, speed, xp of mobs and also how many spawn in an invasion.<br /> <br /> If you want to tweak the default way the difficulty is setup, pop open config/CoroUtil/DynamicDifficulty.cfg<br /> <br /> Play with the configs prefixed with &quot;difficulty_&quot; or &quot;weight&quot; to change how much influence each type has on the average difficulty.<br /> <br /> To test this live in game, you can instead use the /config command to change the values, then run /coroutil difficulty to see the reflected result for your player.<br /> <br /> == Workflow of making and testing invasions ==<br /> <br /> If you want to find a new mob to use from a mod:<br /> * /coroutil printentities<br /> <br /> Test a mob you found from the entities list:<br /> * /summon zombie_players:zombie_player<br /> * OR /coroutil spawn zombie_players:zombie_player<br /> <br /> Didn't crash? great! If it did crash, you can't use that mob :(<br /> <br /> Open up mob_spawns.json in text editor. I will edit the first mob spawn template to use this mob<br /> The first spawn profile is the zombie miner, I will leave that one alone and go down to the second mob spawn profile, that one is the zombie soldier.<br /> In the &quot;entities&quot; list there should be 1 entry, &quot;minecraft:zombie&quot;, lets change that to &quot;zombie_players:zombie_player&quot;<br /> <br /> <br /> == Testing Tips ==<br /> <br /> === Enable helpfull debug output to diagnose potential problems in json === <br /> * in CoroUtil/General.cfg, set useLoggingDebug to true<br /> <br /> You will be able to see if there were any syntax errors with your json file, and where the error was, if everything went ok it should look like this:<br /> <br /> &lt;code&gt;processing, detected as DifficultyData: ./config/CoroUtil/data/templates/actions/mob_spawns.json<br /> <br /> [19:53:05] [main/INFO]: detected mob spawns to deserialize by detecting: mob_spawns&lt;/code&gt;<br /> <br /> === Live edit normal config options === <br /> * /config<br /> <br /> === Live reload data from the json files ingame === <br /> * /coroutil reloadData<br /> <br /> === See difficulty of area === <br /> * /coroutil difficulty<br /> <br /> === Print out a list of usable entities for invasions ===<br /> * /coroutil printEntities<br /> <br /> The printed entities SHOULD work, especially vanilla ones, but any modded entities you should always test, they could either not work, or worse, crash the game. A surprising amount of modded mobs like to crash the game if they aren't spawned in their own special way, that I cannot support without specifically accounting for them.<br /> <br /> Entities that work best are ones that walk on the ground, flying entities still need better support, and may never work because vanilla minecraft doesn't have a good standard for flying entities that modded entities could use, so every mod out there probably implemented their own way.<br /> <br /> === Force specific mob spawn profile for invasion to be used ===<br /> * in config/CoroUtil/General.cfg, set mobSpawnsWaveToForceUse to the name of your mob spawn profile<br /> * eg: invasion_stage_1 or invasion_stage_3_opt_10_illagers<br /> <br /> === Reset dps calculations for 50 chunk area around you === <br /> * /coroutil resetDPS<br /> <br /> Probably not needed, but I've had issues with some situations causing super high DPS resulting in the difficulty being too high, mainly from mods. If you run into issues, use this, or disable DPS in the difficulty calculation, see Dynamic Local Difficulty wiki section for that.</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=46 2019-01-24T02:05:17Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave profiles or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> * The folder is empty, or<br /> * It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> I would recommend copying bits from these files to create and customize your invasions.<br /> <br /> === mob_spawns.json ===<br /> * Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> * Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> * Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> * The spawn profile defines a lot of things<br /> ** What to spawn<br /> ** How it spawns<br /> ** How many spawn<br /> ** What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json<br /> <br /> == Dynamic Local Difficulty ==<br /> <br /> CoroUtil has a local dynamic difficulty systems that tries its best to figure out what stage of the game the player is at, so it can ramp up difficulty along with them.<br /> <br /> Use of this system isn't actually required for invasions, but the default invasion setup uses it for scaling up inventory equipment, health, attack damage, speed, xp of mobs and also how many spawn in an invasion.<br /> <br /> If you want to tweak the default way the difficulty is setup, pop open config/CoroUtil/DynamicDifficulty.cfg<br /> <br /> Play with the configs prefixed with &quot;difficulty_&quot; or &quot;weight&quot; to change how much influence each type has on the average difficulty.<br /> <br /> To test this live in game, you can instead use the /config command to change the values, then run /coroutil difficulty to see the reflected result for your player.<br /> <br /> == Testing Tips ==<br /> <br /> === Enable helpfull debug output to diagnose potential problems in json === <br /> * in CoroUtil/General.cfg, set useLoggingDebug to true<br /> <br /> You will be able to see if there were any syntax errors with your json file, and where the error was, if everything went ok it should look like this:<br /> <br /> &lt;code&gt;processing, detected as DifficultyData: ./config/CoroUtil/data/templates/actions/mob_spawns.json<br /> <br /> [19:53:05] [main/INFO]: detected mob spawns to deserialize by detecting: mob_spawns&lt;/code&gt;<br /> <br /> === Live edit normal config options === <br /> * /config<br /> <br /> === Live reload data from the json files ingame === <br /> * /coroutil reloadData<br /> <br /> === See difficulty of area === <br /> * /coroutil difficulty<br /> <br /> === Print out a list of usable entities for invasions ===<br /> * /coroutil printEntities<br /> <br /> The printed entities SHOULD work, especially vanilla ones, but any modded entities you should always test, they could either not work, or worse, crash the game. A surprising amount of modded mobs like to crash the game if they aren't spawned in their own special way, that I cannot support without specifically accounting for them.<br /> <br /> Entities that work best are ones that walk on the ground, flying entities still need better support, and may never work because vanilla minecraft doesn't have a good standard for flying entities that modded entities could use, so every mod out there probably implemented their own way.<br /> <br /> === Reset dps calculations for 50 chunk area around you === <br /> * /coroutil resetDPS<br /> <br /> Probably not needed, but I've had issues with some situations causing super high DPS resulting in the difficulty being too high, mainly from mods. If you run into issues, use this, or disable DPS in the difficulty calculation, see Dynamic Local Difficulty wiki section for that.</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=45 2019-01-24T01:40:37Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave profiles or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> * The folder is empty, or<br /> * It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> I would recommend copying bits from these files to create and customize your invasions.<br /> <br /> === mob_spawns.json ===<br /> * Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> * Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> * Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> * The spawn profile defines a lot of things<br /> ** What to spawn<br /> ** How it spawns<br /> ** How many spawn<br /> ** What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json<br /> <br /> == Dynamic Local Difficulty ==<br /> <br /> CoroUtil has a local dynamic difficulty systems that tries its best to figure out what stage of the game the player is at, so it can ramp up difficulty along with them.<br /> <br /> Use of this system isn't actually required for invasions, but the default invasion setup uses it for scaling up inventory equipment, health, attack damage, speed, xp of mobs and also how many spawn in an invasion.<br /> <br /> <br /> <br /> TODO: <br /> <br /> == Testing Tips ==<br /> <br /> === Enable helpfull debug output to diagnose potential problems in json === <br /> * in CoroUtil/General.cfg, set useLoggingDebug to true<br /> <br /> You will be able to see if there were any syntax errors with your json file, and where the error was, if everything went ok it should look like this:<br /> <br /> &lt;code&gt;processing, detected as DifficultyData: ./config/CoroUtil/data/templates/actions/mob_spawns.json<br /> <br /> [19:53:05] [main/INFO]: detected mob spawns to deserialize by detecting: mob_spawns&lt;/code&gt;<br /> <br /> === Live edit normal config options === <br /> * /config<br /> <br /> === Live reload data from the json files ingame === <br /> * /coroutil reloadData<br /> <br /> === See difficulty of area === <br /> * /coroutil difficulty<br /> <br /> === Reset dps calculations for 50 chunk area around you === <br /> * /coroutil resetDPS</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=44 2019-01-24T01:35:51Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave profiles or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> * The folder is empty, or<br /> * It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> I would recommend copying bits from these files to create and customize your invasions.<br /> <br /> === mob_spawns.json ===<br /> * Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> * Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> * Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> * The spawn profile defines a lot of things<br /> ** What to spawn<br /> ** How it spawns<br /> ** How many spawn<br /> ** What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json<br /> <br /> === Dynamic Local Difficulty ===<br /> <br /> CoroUtil has a local dynamic difficulty systems that tries its best to figure out what stage of the game the player is at, so it can ramp up difficulty along with them.<br /> <br /> Use of this system isn't actually required for invasions, but the default invasion setup uses it for scaling up inventory equipment, health, attack damage, speed, xp of mobs and also how many spawn in an invasion.<br /> <br /> <br /> <br /> TODO: <br /> <br /> === Testing Tips ===<br /> <br /> TODO:<br /> <br /> Enable helpfull debug output to diagnose potential problems in json:<br /> * in CoroUtil/General.cfg, set useLoggingDebug to true<br /> <br /> You will be able to see if there were any syntax errors with your json file, and where the error was, if everything went ok it should look like this:<br /> <br /> &lt;code&gt;processing, detected as DifficultyData: ./config/CoroUtil/data/templates/actions/mob_spawns.json<br /> <br /> [19:53:05] [main/INFO]: detected mob spawns to deserialize by detecting: mob_spawns&lt;/code&gt;<br /> <br /> <br /> Live edit normal config options:<br /> * /config<br /> <br /> <br /> Live reload data from the json files ingame:<br /> * /coroutil reloadData<br /> <br /> <br /> See difficulty of area:<br /> * /coroutil difficulty<br /> <br /> <br /> Reset dps calculations for 50 chunk area around you:<br /> * /coroutil resetDPS</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=43 2019-01-24T01:35:18Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave profiles or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> * The folder is empty, or<br /> * It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> I would recommend copying bits from these files to create and customize your invasions.<br /> <br /> === mob_spawns.json ===<br /> * Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> * Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> * Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> * The spawn profile defines a lot of things<br /> ** What to spawn<br /> ** How it spawns<br /> ** How many spawn<br /> ** What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json<br /> <br /> === Dynamic Local Difficulty ===<br /> <br /> CoroUtil has a local dynamic difficulty systems that tries its best to figure out what stage of the game the player is at, so it can ramp up difficulty along with them.<br /> <br /> Use of this system isn't actually required for invasions, but the default invasion setup uses it for scaling up inventory equipment, health, attack damage, speed, xp of mobs and also how many spawn in an invasion.<br /> <br /> <br /> <br /> TODO: <br /> <br /> === Testing Tips ===<br /> <br /> TODO:<br /> <br /> Enable helpfull debug output to diagnose potential problems in json:<br /> * in CoroUtil/General.cfg, set useLoggingDebug to true<br /> <br /> You will be able to see if there were any syntax errors with your json file, and where the error was, if everything went ok it should look like this:<br /> <br /> &lt;code&gt;processing, detected as DifficultyData: ./config/CoroUtil/data/templates/actions/mob_spawns.json<br /> <br /> [19:53:05] [main/INFO]: detected mob spawns to deserialize by detecting: mob_spawns&lt;/code&gt;<br /> <br /> Live edit normal config options:<br /> * /config<br /> <br /> Live reload data from the json files ingame:<br /> * /coroutil reloadData<br /> <br /> See difficulty of area:<br /> * /coroutil difficulty<br /> <br /> Reset dps calculations for 50 chunk area around you:<br /> * /coroutil resetDPS</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=42 2019-01-24T01:34:46Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave profiles or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> * The folder is empty, or<br /> * It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> I would recommend copying bits from these files to create and customize your invasions.<br /> <br /> === mob_spawns.json ===<br /> * Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> * Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> * Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> * The spawn profile defines a lot of things<br /> ** What to spawn<br /> ** How it spawns<br /> ** How many spawn<br /> ** What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json<br /> <br /> === Dynamic Local Difficulty ===<br /> <br /> CoroUtil has a local dynamic difficulty systems that tries its best to figure out what stage of the game the player is at, so it can ramp up difficulty along with them.<br /> <br /> Use of this system isn't actually required for invasions, but the default invasion setup uses it for scaling up inventory equipment, health, attack damage, speed, xp of mobs and also how many spawn in an invasion.<br /> <br /> <br /> <br /> TODO: <br /> <br /> === Testing Tips ===<br /> <br /> TODO:<br /> <br /> Enable helpfull debug output to diagnose potential problems in json:<br /> * in CoroUtil/General.cfg, set useLoggingDebug to true<br /> <br /> You will be able to see if there were any syntax errors with your json file, and where the error was, if everything went ok it should look like this:<br /> &lt;code&gt;processing, detected as DifficultyData: ./config/CoroUtil/data/templates/actions/mob_spawns.json<br /> [19:53:05] [main/INFO]: detected mob spawns to deserialize by detecting: mob_spawns&lt;/code&gt;<br /> <br /> Live edit normal config options:<br /> * /config<br /> <br /> Live reload data from the json files ingame:<br /> * /coroutil reloadData<br /> <br /> See difficulty of area:<br /> * /coroutil difficulty<br /> <br /> Reset dps calculations for 50 chunk area around you:<br /> * /coroutil resetDPS</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=41 2019-01-23T01:48:42Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave profiles or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> * The folder is empty, or<br /> * It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> I would recommend copying bits from these files to create and customize your invasions.<br /> <br /> === mob_spawns.json ===<br /> * Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> * Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> * Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> * The spawn profile defines a lot of things<br /> ** What to spawn<br /> ** How it spawns<br /> ** How many spawn<br /> ** What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json<br /> <br /> === Dynamic Local Difficulty ===<br /> <br /> TODO: <br /> <br /> === Testing Tips ===<br /> <br /> TODO:<br /> <br /> Live edit normal config options:<br /> * /config<br /> <br /> Live reload data from the json files ingame:<br /> * /coroutil reloadData<br /> <br /> See difficulty of area:<br /> * /coroutil difficulty<br /> <br /> Reset dps calculations for 50 chunk area around you:<br /> * /coroutil resetDPS</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=40 2019-01-23T01:26:50Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave profiles or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> * The folder is empty, or<br /> * It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> === mob_spawns.json ===<br /> * Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> * Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> * Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> * the spawn profile defines a lot of things<br /> ** What to spawn<br /> ** How it spawns<br /> ** How many spawn<br /> ** What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=39 2019-01-23T01:25:11Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave profiles or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> - The folder is empty, or<br /> - It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> === mob_spawns.json ===<br /> - Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> - Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> - Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> - the spawn profile defines a lot of things<br /> -- What to spawn<br /> -- How it spawns<br /> -- How many spawn<br /> -- What cmods to give them<br /> <br /> Have a look at mob_spawns_example_commented.json to see every piece explained. <br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> To see an up to date list on every cmod possible, the file all_cmods.json will always be where to look for every single thing the cmod system supports, there is also lots of comments in the file to explain them as much as possible.<br /> <br /> === Conditions ===<br /> <br /> A Condition is used to decide if a mob spawns profile can be used at the moment an invasion starts. You can define things like what wave number it should be used, what what difficulty, or for randomizing between various mob spawn profiles like the default spawn templates do.<br /> <br /> To see an up to date list on every condition possible, look at all_conditions.json</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=38 2019-01-23T01:12:15Z

<p>Corosus: </p> <hr /> <div>This page is for customizing the existing invasion wave profiles or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil will overwrite the contents of config/CoroUtil/data/ every game run if:<br /> - The folder is empty, or<br /> - It detects zero file changes by comparing file contents against the info in filehashes.txt (leave this file alone or you might lose data)<br /> <br /> If you make changes to the json files, you should be safe from having files overwritten.<br /> <br /> This is to make sure any new mod updates has the latest json on the filesystem unless files have been manually edited.<br /> <br /> For updating the mods when you have custom files I would recommend backing up your json files, deleting the data folder, then let the mod generate the new files, you could then paste your files back in and see if things work out ok ingame, if not, decide on how to merge in your changes.<br /> <br /> == JSON Structure ==<br /> <br /> The default invasion setup is making use of 3 files: templates/action/mob_spawns.json, templates/cmods/invasions_cmods.json, and templates/conditions/invasions_stages.json.<br /> <br /> Only mob_spawns.json is truely required, you can get away with using only it if you don't use templates at all, the default setup uses templates though, the other 2 files contain pre-made templates referenced in mob_spawns.json to keep down on the copying and pasting.<br /> <br /> === mob_spawns.json ===<br /> - Contains a list of potential spawn templates, defined in the &quot;templates&quot; list object<br /> - Each spawn template can have a list of conditions required to use the spawn profile, defined in the &quot;conditions&quot; list object, this list is optional<br /> - Each spawn template has a list of spawn profiles, defined in the &quot;spawns&quot; list object<br /> - the spawn profile defines a lot of things<br /> -- What to spawn<br /> -- How it spawns<br /> -- How many spawn<br /> -- What cmods to give them<br /> <br /> === Cmods ===<br /> <br /> A Cmod is just short for the more corny term: Coro Modifier. They modify an entity in various ways, from things as simple as health to more complex things like preset AI routines.<br /> <br /> === Conditions ===<br /> <br /> asdasdasd</div>

Corosus http://coros.us/wiki/index.php?title=Hostile_Worlds_-_Invasions_-_Customizing&diff=37 2019-01-23T00:46:49Z

<p>Corosus: Created page with &quot;This page is for customizing the existing invasion wave profiles or creating your own. == Getting setup == You'll need a good text editor, for windows, notepad++ should do,...&quot;</p> <hr /> <div>This page is for customizing the existing invasion wave profiles or creating your own.<br /> <br /> == Getting setup ==<br /> <br /> You'll need a good text editor, for windows, notepad++ should do, but something that can do syntax checking would help make sure things are formatted correctly, and editor like IntelliJ IDEA can do this. If you just use notepad++ you can find out if anything went wrong reading your json file later.<br /> <br /> The first thing you'll need to do is run the game with coroutil and hw-invasions installed, this will generate the needed files in your minecraft config folder, you can leave the game open or close it at this point, doesn't matter. If you leave it open you can live edit and reload json files, to save from having to reload large modpacks.<br /> <br /> The main file you will be working in is mob_spawns.json, once you have run the game, you can find it in config/CoroUtil/data/templates/actions/<br /> <br /> == Resetting files or updating CoroUtil ==<br /> <br /> CoroUtil scans for changes in any file in config/CoroUtil/data/. If the folder is empty, or if there have been no changes to any file, it will overwrite the contents of everything in there, this is so when there is a new update to the json files, it can make sure anyone who had CoroUtil and HW-Invasions installed before will get the most up to date json files.<br /> <br /> This also means that if you make any changes to the files, your files wont be overwritten on each run of the game, but also if there was any json changes for a newer version of the mod, you wont have those either.</div>

Corosus http://coros.us/wiki/index.php?title=Weather2_Main_Page&diff=36 2018-06-24T15:07:54Z

<p>Corosus: </p> <hr /> <div>== Useful Links ==<br /> <br /> [//coros.us/mods/weather2 Mod Showcase and Download]<br /> <br /> [//coros.us/wiki/index.php?title=Weather2_FAQ Weather2 FAQ]<br /> <br /> == How it works ==<br /> <br /> Simulates a weather system around each player, spawning warm and cold cloud formations depending on the biome. As the cloud formations travel due to the wind added by the mod, when they collide they have a chance of developing into thunderstorms, which can progress into deadlier storms such as wall clouds, hailstorms, tornadoes, or hurricanes.<br /> <br /> The cloud formations also build up moisture as they travel over humid or wet biomes, and will rain locally in an area after it builds up enough moisture.<br /> <br /> Since the weather is localized, the mod does its best to be compatible with vanilla global weather features, but if you need better cross mod compatibility, you can make weather2 not override global rain by turning on global overcast in the ingame weather2 gui &quot;storms when&quot;, or set overcastMode to true in Misc.cfg. With this mode on, weather2 will do light rain everywhere when vanilla server rain is active, and rain more heavily as storms pass by above, otherwise weather2 forces server side weather off and performs its own logic on it.<br /> <br /> There are also other aesthetic features and wind systems in the mod, shown on the showcase page.<br /> <br /> == Items ==<br /> <br /> === Weather Item ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_weather_item.png<br /> <br /> Used for crafting recipes only.<br /> <br /> === Placeable Sand Layer ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_placeable_sand_layer.png<br /> <br /> The item version of the Sand Layer block. Places down a single layer of sand, can stack up like snow layers<br /> <br /> === Pocket Sand! ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_pocket_sand.png<br /> <br /> The power of a sandstorm in your hands. Fires off a blast of sand particles and places down sand layer blocks just like a sandstorm would. Aim it at other players to blind them.<br /> <br /> == Blocks ==<br /> <br /> === Tornado Sensor ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_tornado_sensor.png<br /> <br /> Emits a redstone signal when deadly weather is near.<br /> <br /> === Tornado Siren ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_tornado_siren.png<br /> <br /> Emits a siren sound when deadly weather is near.<br /> <br /> === Manual Redstone Siren ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_manual_redstone_siren.png<br /> <br /> Use the tornado siren sound by activating with redstone.<br /> <br /> === Wind Vane ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_wind_vane.png<br /> <br /> Points in the direction of the wind.<br /> <br /> === Anemometer ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_anemometer.png<br /> <br /> Spins based on speed of wind.<br /> <br /> === Weather Radar ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_weather_radar.png<br /> <br /> Shows active weather activity on the block<br /> <br /> === Weather Machine ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_weather_machine.png<br /> <br /> Creates and maintains various types of weather at the blocks location and keeps them there.<br /> <br /> Right click to cycle, shift right click to reverse cycle.<br /> <br /> === Weather Deflector ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_weather_deflector.png<br /> <br /> By default, kills off bad weather within an area around the block.<br /> <br /> Can right click cycle to just block protection mode, storms will still come but cannot grab blocks.</div>

Corosus http://coros.us/wiki/index.php?title=Weather2_Main_Page&diff=35 2018-06-24T00:58:03Z

<p>Corosus: </p> <hr /> <div>== Useful Links ==<br /> <br /> [//coros.us/mods/weather2 Mod Showcase and Download]<br /> <br /> [//coros.us/wiki/index.php?title=Weather2_FAQ Weather2 FAQ]<br /> <br /> == Items ==<br /> <br /> === Weather Item ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_weather_item.png<br /> <br /> Used for crafting recipes only.<br /> <br /> === Placeable Sand Layer ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_placeable_sand_layer.png<br /> <br /> The item version of the Sand Layer block. Places down a single layer of sand, can stack up like snow layers<br /> <br /> === Pocket Sand! ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_pocket_sand.png<br /> <br /> The power of a sandstorm in your hands. Fires off a blast of sand particles and places down sand layer blocks just like a sandstorm would. Aim it at other players to blind them.<br /> <br /> == Blocks ==<br /> <br /> === Tornado Sensor ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_tornado_sensor.png<br /> <br /> Emits a redstone signal when deadly weather is near.<br /> <br /> === Tornado Siren ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_tornado_siren.png<br /> <br /> Emits a siren sound when deadly weather is near.<br /> <br /> === Manual Redstone Siren ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_manual_redstone_siren.png<br /> <br /> Use the tornado siren sound by activating with redstone.<br /> <br /> === Wind Vane ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_wind_vane.png<br /> <br /> Points in the direction of the wind.<br /> <br /> === Anemometer ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_anemometer.png<br /> <br /> Spins based on speed of wind.<br /> <br /> === Weather Radar ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_weather_radar.png<br /> <br /> Shows active weather activity on the block<br /> <br /> === Weather Machine ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_weather_machine.png<br /> <br /> Creates and maintains various types of weather at the blocks location and keeps them there.<br /> <br /> Right click to cycle, shift right click to reverse cycle.<br /> <br /> === Weather Deflector ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_weather_deflector.png<br /> <br /> By default, kills off bad weather within an area around the block.<br /> <br /> Can right click cycle to just block protection mode, storms will still come but cannot grab blocks.</div>

Corosus http://coros.us/wiki/index.php?title=Weather2_FAQ&diff=34 2018-06-23T18:04:37Z

<p>Corosus: </p> <hr /> <div>== Weather2 lags my game, how can I fix this? ==<br /> <br /> Assuming its a frame rate issue, here are some steps to minimize Weather2's impact on your fps.<br /> <br /> === Improving it in-game ===<br /> <br /> Before touching any config files, open up the ingame weather2 config gui at the top of the escape menu.<br /> <br /> In the performance tab, lower everything to either low or none, save, then wait up to 30 seconds or so while any actively spawned particles despawn, then see if your fps improves.<br /> <br /> Another option that might help is setting &quot;Particle precipitation&quot; to Off in the Compatibility tab.<br /> <br /> === Improving with config files ===<br /> <br /> If the in-game way wasn't enough, here are some config file options to take it even further.<br /> <br /> You can edit the config files live in-game by typing /config or edit the actual files in config/weather2/ with a text editor, either or works.<br /> <br /> As a test, in Misc.cfg or weather2Misc in-game, set Client_PotatoPC_Mode to true.<br /> * this is the best performance you can get, if this is not enough, your computer probably isn't powerful enough for the mod.<br /> * This flat out disables a lot of visuals of weather2 however, and is not recommended unless you are trying to connect to a server that has weather2.<br /> <br /> Turn the setting back off and try some other ones:<br /> <br /> In Storm.cfg or weather2Storm in-game:<br /> * Increase value of Storm_ParticleSpawnDelay to reduce how often cloud particles spawn in the sky.<br /> <br /> In Misc.cfg or weather2Misc in-game:<br /> * Increase value of Cloud_ParticleSpawnDelay to reduce how often cloud particles spawn in the sky.<br /> <br /> ==== Reducing thread workload to maybe help fps ====<br /> <br /> In Misc.cfg or weather2Misc in-game:<br /> * Increase value of Thread_Particle_Process_Delay to reduce how often weather2 scans the terrain for places to spawn particles.<br /> <br /> In Particle.cfg or weather2Particle in-game:<br /> * Set Wind_Particle_leafs and Wind_Particle_waterfall both to false to stop terrain scanning for particle spawning entirely.<br /> <br /> <br /> <br /> == How do I make it look better with optifine shaders? ==<br /> <br /> I need to investigate more still, but SEUS Renewed 1.0.0 might work better.<br /> <br /> You can also try setting useEntityRenderHookForShaders to false in CoroUtil/General.cfg to see if it plays nice, you can change this ingame to test via the /config command gui<br /> <br /> == I want less deadly storms ==<br /> <br /> Many ways to go about this:<br /> <br /> === Less frequent ===<br /> <br /> You can change this in the ingame weather gui<br /> <br /> === Change rate of each type ===<br /> <br /> See Storm.cfg, you can change the percent chance of any of the storm types, eg the Storm_PercentChanceOf_F5_Tornado setting, and other &quot;Storm_PercentChanceOf&quot; settings.<br /> <br /> === Deadly storms but they dont impact your base ===<br /> <br /> Chose any of these options depending on how you want it<br /> <br /> * Disable block destruction in the ingame weather2 config gui or...<br /> * Storm_Tornado_grabBlocks to false in Storm.cfg<br /> <br /> * In Tornado.cfg, change these as you see fit, the config file has notes on them as well:<br /> ** Storm_Tornado_grabPlayersOnly<br /> ** Storm_Tornado_grabPlayer<br /> ** Storm_Tornado_grabVillagers<br /> ** Storm_Tornado_grabMobs<br /> ** Storm_Tornado_grabAnimals<br /> ** Storm_Tornado_grabItems (already false)<br /> <br /> === Go full aesthetic only mode ===<br /> ** set Aesthetic_Only_Mode to true in Misc.cfg<br /> *** This will disable clouds, storms, and leave just wind and pretty particle effects</div>

Corosus http://coros.us/wiki/index.php?title=Weather2_FAQ&diff=33 2018-06-23T18:02:02Z

<p>Corosus: </p> <hr /> <div>== Weather2 lags my game, how can I fix this? ==<br /> <br /> Assuming its a frame rate issue, here are some steps to minimize Weather2's impact on your fps.<br /> <br /> === Improving it in-game ===<br /> <br /> Before touching any config files, open up the ingame weather2 config gui at the top of the escape menu.<br /> <br /> In the performance tab, lower everything to either low or none, save, then wait up to 30 seconds or so while any actively spawned particles despawn, then see if your fps improves.<br /> <br /> Another option that might help is setting &quot;Particle precipitation&quot; to Off in the Compatibility tab.<br /> <br /> === Improving with config files ===<br /> <br /> If the in-game way wasn't enough, here are some config file options to take it even further.<br /> <br /> You can edit the config files live in-game by typing /config or edit the actual files in config/weather2/ with a text editor, either or works.<br /> <br /> As a test, in Misc.cfg or weather2Misc in-game, set Client_PotatoPC_Mode to true.<br /> * this is the best performance you can get, if this is not enough, your computer probably isn't powerful enough for the mod.<br /> * This flat out disables a lot of visuals of weather2 however, and is not recommended unless you are trying to connect to a server that has weather2.<br /> <br /> Turn the setting back off and try some other ones:<br /> <br /> In Storm.cfg or weather2Storm in-game:<br /> * Increase value of Storm_ParticleSpawnDelay to reduce how often cloud particles spawn in the sky.<br /> <br /> In Misc.cfg or weather2Misc in-game:<br /> * Increase value of Cloud_ParticleSpawnDelay to reduce how often cloud particles spawn in the sky.<br /> <br /> ==== Reducing thread workload to maybe help fps ====<br /> <br /> In Misc.cfg or weather2Misc in-game:<br /> * Increase value of Thread_Particle_Process_Delay to reduce how often weather2 scans the terrain for places to spawn particles.<br /> <br /> In Particle.cfg or weather2Particle in-game:<br /> * Set Wind_Particle_leafs and Wind_Particle_waterfall both to false to stop terrain scanning for particle spawning entirely.<br /> <br /> <br /> <br /> == How do I make it look better with optifine shaders? ==<br /> <br /> I need to investigate more still, but SEUS Renewed 1.0.0 might work better.<br /> <br /> You can also try setting useEntityRenderHookForShaders to false in CoroUtil/General.cfg to see if it plays nice, you can change this ingame to test via the /config command gui<br /> <br /> == I want less deadly storms ==<br /> <br /> Many ways to go about this:<br /> <br /> === Deadly storms but they dont impact your base ===<br /> <br /> Chose any of these options depending on how you want it<br /> <br /> * Disable block destruction in the ingame weather2 config gui or...<br /> * Storm_Tornado_grabBlocks to false in Storm.cfg<br /> <br /> * In Tornado.cfg, change these as you see fit, the config file has notes on them as well:<br /> ** Storm_Tornado_grabPlayersOnly<br /> ** Storm_Tornado_grabPlayer<br /> ** Storm_Tornado_grabVillagers<br /> ** Storm_Tornado_grabMobs<br /> ** Storm_Tornado_grabAnimals<br /> ** Storm_Tornado_grabItems (already false)<br /> <br /> === Go full aesthetic only mode ===<br /> ** set Aesthetic_Only_Mode to true in Misc.cfg<br /> *** This will disable clouds, storms, and leave just wind and pretty particle effects</div>

Corosus http://coros.us/wiki/index.php?title=ZombieAwareness_FAQ&diff=32 2018-06-23T17:45:49Z

<p>Corosus: </p> <hr /> <div>== The mod lags my game, how can I fix this? ==<br /> <br /> The mod increases the amount of mob pathfinding being done, which might be a problem on lower end hardware or with modpacks that increase mob counts, here are some ways you can improve this:<br /> <br /> * Note: the following suggestions assume you have a default config setup, otherwise there might have been something else you changed that affects performance, delete the config files to restore deafult configs if required:<br /> <br /> === Stop the extra spawning ===<br /> <br /> * Set maxZombiesNight to 0 in Spawning.cfg<br /> <br /> === Slow down how hard the mod pathfinds ===<br /> <br /> * Increase tickRateAILoop in General.cfg, default is 5, 20 = 1 second<br /> <br /> * Reduce maxPFRangeSense in General.cfg</div>

Corosus http://coros.us/wiki/index.php?title=ZombieAwareness_FAQ&diff=31 2018-06-23T17:43:42Z

<p>Corosus: Created page with &quot;== The mod lags my game, how can I fix this? == The mod increases the amount of mob pathfinding being done, which might be a problem on lower end hardware or with modpacks th...&quot;</p> <hr /> <div>== The mod lags my game, how can I fix this? ==<br /> <br /> The mod increases the amount of mob pathfinding being done, which might be a problem on lower end hardware or with modpacks that increase mob counts, here are some ways you can improve this:<br /> <br /> === Stop the extra spawning ===<br /> <br /> * Set maxZombiesNight to 0 in Spawning.cfg<br /> <br /> === Slow down how hard the mod pathfinds ===<br /> <br /> * Increase tickRateAILoop in General.cfg, default is 5, 20 = 1 second<br /> <br /> * Reduce maxPFRangeSense in General.cfg</div>

Corosus http://coros.us/wiki/index.php?title=ZombieAwareness_Main_Page&diff=30 2018-06-23T17:40:25Z

<p>Corosus: </p> <hr /> <div>== Useful Links ==<br /> <br /> [//coros.us/mods/zombieawareness Mod Showcase and Download]<br /> <br /> [//coros.us/wiki/index.php?title=ZombieAwareness_FAQ Zombie Awareness FAQ]<br /> <br /> == How it works ==<br /> <br /> The mod makes it seem like mobs are aware of you more from the sounds you make or the smells you emit.<br /> <br /> When you perform certain actions like mining blocks or taking damage, the mod will spawn or buff an invisible &quot;sense&quot; entity that other mobs use to pathfind to. These decay over time to simulate the mobs eventually &quot;forgetting&quot; about it and caring more about the most recent senses.<br /> <br /> The current actions that trigger senses are:<br /> * Block breaking<br /> * Taking damage (configurable)<br /> ** Shows blood splatter on the ground<br /> * Having low health (as if you are bleeding over time)<br /> * Arrows hitting/shooting<br /> * Explosions<br /> * Chests and doors opening and closing<br /> * Pistons activating (can be heard from far, configurable)<br /> * Zombies growling (configurable)<br /> * Being near light sources they can see (configurable)<br /> <br /> You can enable or disable sound based triggers as a whole in Features.cfg<br /> <br /> If you want to see what is making sound senses ingame, turn on client_debugSensesVisual in ClientConfig.cfg<br /> <br /> You can decide what mobs are enhanced with all this extra awareness by editing MobLlists.cfg<br /> * As noted in the cfg file, won't work for all mobs if they arent using ground pathfinding or if a modded mob does its own special ways of ground pathfinding.<br /> <br /> === Other small features ===<br /> <br /> * Mobs make investigation and agression noises when they are pathing to you or see you<br /> * Random speed boost to mobs on spawn (configurable via General.cfg)<br /> * Spawns extra clusters of mobs at night from an existing zombie if its far enough away from you, (configurable via maxZombiesNight in Spawning.cfg)<br /> * Turns off baby zombies and random chance of re-enforcement feature (configurable via Features.cfg)<br /> <br /> == Extra features default off in config ==<br /> <br /> * Extra mob spawning on surface<br /> ** Turn on with extraSpawningSurface in Features.cfg, more detailed choices in Spawning.cfg<br /> <br /> * Extra mob spawning in caves<br /> ** Turn on with extraSpawningCave in Features.cfg, more detailed choices in Spawning.cfg<br /> <br /> * Mob Omniscience<br /> ** Turn on in General.cfg<br /> <br /> * Mobs See through walls<br /> ** Turn on in General.cfg</div>

Corosus http://coros.us/wiki/index.php?title=ZombieAwareness_Main_Page&diff=29 2018-06-23T17:36:28Z

<p>Corosus: </p> <hr /> <div>== Useful Links ==<br /> <br /> [//coros.us/mods/zombieawareness Mod Showcase and Download]<br /> <br /> [//coros.us/wiki/index.php?title=ZombieAwareness_FAQ Zombie Awareness FAQ]<br /> <br /> == How it works ==<br /> <br /> The mod makes it seem like mobs are aware of you more from the sounds you make or the smells you emit.<br /> <br /> When you perform certain actions like mining blocks or taking damage, the mod will spawn or buff an invisible &quot;sense&quot; entity that other mobs use to pathfind to. These decay over time to simulate the mobs eventually &quot;forgetting&quot; about it and caring more about the most recent senses.<br /> <br /> The current actions that trigger senses are:<br /> * Block breaking<br /> * Taking damage (configurable)<br /> ** Shows blood splatter on the ground<br /> * Having low health (as if you are bleeding over time)<br /> * Arrows hitting/shooting<br /> * Explosions<br /> * Chests and doors opening and closing<br /> * Pistons activating (can be heard from far, configurable)<br /> * Zombies growling (configurable)<br /> * Being near light sources they can see (configurable)<br /> <br /> You can enable or disable sound based triggers as a whole in Features.cfg<br /> <br /> If you want to see what is making sound senses ingame, turn on client_debugSensesVisual in ClientConfig.cfg<br /> <br /> === Other small features ===<br /> <br /> * Mobs make investigation and agression noises when they are pathing to you or see you<br /> * Random speed boost to mobs on spawn (configurable via General.cfg)<br /> * Spawns extra clusters of mobs at night from an existing zombie if its far enough away from you, (configurable via maxZombiesNight in Spawning.cfg)<br /> * Turns off baby zombies and random chance of re-enforcement feature (configurable via Features.cfg)<br /> <br /> == Extra features default off in config ==<br /> <br /> * Extra mob spawning on surface<br /> ** Turn on with extraSpawningSurface in Features.cfg, more detailed choices in Spawning.cfg<br /> <br /> * Extra mob spawning in caves<br /> ** Turn on with extraSpawningCave in Features.cfg, more detailed choices in Spawning.cfg<br /> <br /> * Mob Omniscience<br /> ** Turn on in General.cfg<br /> <br /> * Mobs See through walls<br /> ** Turn on in General.cfg</div>

Corosus http://coros.us/wiki/index.php?title=ZombieAwareness_Main_Page&diff=28 2018-06-23T17:35:22Z

<p>Corosus: </p> <hr /> <div>== Useful Links ==<br /> <br /> [//coros.us/mods/zombieawareness Mod Showcase and Download]<br /> <br /> [//coros.us/wiki/index.php?title=ZombieAwareness_FAQ Zombie Awareness FAQ]<br /> <br /> == How it works ==<br /> <br /> The mod makes it seem like mobs are aware of you more from the sounds you make or the smells you emit.<br /> <br /> <br /> When you perform certain actions like mining blocks or taking damage, the mod will spawn or buff an invisible &quot;sense&quot; entity that other mobs use to pathfind to. These decay over time to simulate the mobs eventually &quot;forgetting&quot; about it and caring more about the most recent senses.<br /> <br /> The current actions that trigger senses are:<br /> * Block breaking<br /> * Taking damage (configurable)<br /> ** Shows blood splatter on the ground<br /> * Having low health (as if you are bleeding over time)<br /> * Arrows hitting/shooting<br /> * Explosions<br /> * Chests and doors opening and closing<br /> * Pistons activating (can be heard from far, configurable)<br /> * Zombies growling (configurable)<br /> * Being near light sources they can see (configurable)<br /> <br /> You can enable or disable sound based triggers as a whole in Features.cfg<br /> <br /> If you want to see what is making sound senses ingame, turn on client_debugSensesVisual in ClientConfig.cfg<br /> <br /> === Other small features ===<br /> <br /> * Mobs make investigation and agression noises when they are pathing to you or see you<br /> * Random speed boost to mobs on spawn (configurable via General.cfg)<br /> * Spawns extra clusters of mobs at night from an existing zombie if its far enough away from you, (configurable via maxZombiesNight in Spawning.cfg)<br /> * Turns off baby zombies and random chance of re-enforcement feature (configurable via Features.cfg)<br /> <br /> == Extra features default off in config ==<br /> <br /> * Extra mob spawning on surface<br /> ** Turn on with extraSpawningSurface in Features.cfg, more detailed choices in Spawning.cfg<br /> <br /> * Extra mob spawning in caves<br /> ** Turn on with extraSpawningCave in Features.cfg, more detailed choices in Spawning.cfg<br /> <br /> * Mob Omniscience<br /> ** Turn on in General.cfg<br /> <br /> * Mobs See through walls<br /> ** Turn on in General.cfg</div>

Corosus http://coros.us/wiki/index.php?title=Weather2_Main_Page&diff=27 2018-06-23T17:34:46Z

<p>Corosus: </p> <hr /> <div>== Useful Links ==<br /> <br /> [//coros.us/mods/weather2 Mod Showcase and Download]<br /> <br /> [//coros.us/wiki/index.php?title=Weather2_FAQ Weather2 FAQ]<br /> <br /> == Items ==<br /> <br /> === Weather Item ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_weather_item.png<br /> <br /> Used for crafting recipes only.<br /> <br /> === Placeable Sand Layer ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_placeable_sand_layer.png<br /> <br /> The item version of the Sand Layer block. Places down a single layer of sand, can stack up like snow layers<br /> <br /> === Pocket Sand! ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_pocket_sand.png<br /> <br /> The power of a sandstorm in your hands. Fires off a blast of sand particles and places down sand layer blocks just like a sandstorm would. Aim it at other players to blind them.<br /> <br /> == Blocks ==<br /> <br /> === Tornado Sensor ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_tornado_sensor.png<br /> <br /> === Tornado Siren ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_tornado_siren.png<br /> <br /> === Manual Redstone Siren ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_manual_redstone_siren.png<br /> <br /> === Wind Vane ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_wind_vane.png<br /> <br /> === Anemometer ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_anemometer.png<br /> <br /> === Weather Radar ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_weather_radar.png<br /> <br /> === Weather Machine ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_weather_machine.png<br /> <br /> === Weather Deflector ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_weather_deflector.png</div>

Corosus http://coros.us/wiki/index.php?title=ZombieAwareness_Main_Page&diff=26 2018-06-23T17:31:55Z

<p>Corosus: </p> <hr /> <div>== How it works ==<br /> <br /> The mod makes it seem like mobs are aware of you more from the sounds you make or the smells you emit.<br /> <br /> <br /> When you perform certain actions like mining blocks or taking damage, the mod will spawn or buff an invisible &quot;sense&quot; entity that other mobs use to pathfind to. These decay over time to simulate the mobs eventually &quot;forgetting&quot; about it and caring more about the most recent senses.<br /> <br /> The current actions that trigger senses are:<br /> * Block breaking<br /> * Taking damage (configurable)<br /> * Having low health (as if you are bleeding over time)<br /> * Arrows hitting/shooting<br /> * Explosions<br /> * Chests and doors opening and closing<br /> * Pistons activating (can be heard from far, configurable)<br /> * Zombies growling (configurable)<br /> * Being near light sources they can see (configurable)<br /> <br /> You can enable or disable sound based triggers as a whole in Features.cfg<br /> <br /> === Other small features ===<br /> <br /> * Mobs make investigation and agression noises when they are pathing to you or see you<br /> * Random speed boost to mobs on spawn (configurable via General.cfg)<br /> * Spawns extra clusters of mobs at night from an existing zombie if its far enough away from you, (configurable via maxZombiesNight in Spawning.cfg)<br /> * Turns off baby zombies and random chance of re-enforcement feature (configurable via Features.cfg)<br /> <br /> == Extra features default off in config ==<br /> <br /> * Extra mob spawning on surface<br /> ** Turn on with extraSpawningSurface in Features.cfg<br /> <br /> * Extra mob spawning in caves<br /> ** Turn on with extraSpawningCave in Features.cfg<br /> <br /> * Mob Omniscience<br /> ** Turn on in General.cfg<br /> <br /> * Mobs See through walls<br /> ** Turn on in General.cfg</div>

Corosus http://coros.us/wiki/index.php?title=ZombieAwareness_Main_Page&diff=25 2018-06-23T14:49:03Z

<p>Corosus: </p> <hr /> <div>== How it works ==<br /> <br /> The mod makes it seem like mobs are aware of you more from the sounds you make or the smells you emit.<br /> <br /> <br /> When you perform certain actions like mining blocks or taking damage, the mod will spawn or buff an invisible &quot;sense&quot; entity that other mobs use to pathfind to. These decay over time to simulate the mobs eventually &quot;forgetting&quot; about it and caring more about the most recent senses.<br /> <br /> <br /> The current actions that trigger senses are:<br /> * Block breaking<br /> * Taking damage<br /> * Having low health (as if you are bleeding over time)<br /> * Arrows hitting/shooting<br /> * Explosions<br /> * Chests and doors opening and closing<br /> <br /> <br /> Extra configurable options:<br /> * Pistons extending</div>

Corosus http://coros.us/wiki/index.php?title=ZombieAwareness_Main_Page&diff=24 2018-06-23T14:48:35Z

<p>Corosus: Created page with &quot;== How it works == The mod makes it seem like mobs are aware of you more from the sounds you make or the smells you emit. When you perform certain actions like mining blocks...&quot;</p> <hr /> <div>== How it works ==<br /> <br /> The mod makes it seem like mobs are aware of you more from the sounds you make or the smells you emit.<br /> <br /> When you perform certain actions like mining blocks or taking damage, the mod will spawn or buff an invisible &quot;sense&quot; entity that other mobs use to pathfind to. These decay over time to simulate the mobs eventually &quot;forgetting&quot; about it and caring more about the most recent senses.<br /> <br /> The current actions that trigger senses are:<br /> * Block breaking<br /> * Taking damage<br /> * Having low health (as if you are bleeding over time)<br /> * Arrows hitting/shooting<br /> * Explosions<br /> * Chests and doors opening and closing<br /> <br /> Extra configurable options:<br /> * Pistons extending</div>

Corosus http://coros.us/wiki/index.php?title=Weather2_Main_Page&diff=23 2018-06-22T21:31:27Z

<p>Corosus: </p> <hr /> <div>== Main Links ==<br /> <br /> [//coros.us/mods/weather2 Mod Showcase and Download]<br /> <br /> [//coros.us/wiki/index.php?title=Weather2_FAQ Weather2 FAQ]<br /> <br /> == Items ==<br /> <br /> === Weather Item ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_weather_item.png<br /> <br /> Used for crafting recipes only.<br /> <br /> === Placeable Sand Layer ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_placeable_sand_layer.png<br /> <br /> The item version of the Sand Layer block. Places down a single layer of sand, can stack up like snow layers<br /> <br /> === Pocket Sand! ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_pocket_sand.png<br /> <br /> The power of a sandstorm in your hands. Fires off a blast of sand particles and places down sand layer blocks just like a sandstorm would. Aim it at other players to blind them.<br /> <br /> == Blocks ==<br /> <br /> === Tornado Sensor ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_tornado_sensor.png<br /> <br /> === Tornado Siren ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_tornado_siren.png<br /> <br /> === Manual Redstone Siren ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_manual_redstone_siren.png<br /> <br /> === Wind Vane ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_wind_vane.png<br /> <br /> === Anemometer ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_anemometer.png<br /> <br /> === Weather Radar ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_weather_radar.png<br /> <br /> === Weather Machine ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_weather_machine.png<br /> <br /> === Weather Deflector ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_weather_deflector.png</div>

Corosus http://coros.us/wiki/index.php?title=Weather2_Main_Page&diff=22 2018-06-22T21:30:36Z

<p>Corosus: </p> <hr /> <div>== Main Links ==<br /> <br /> [//coros.us/mods/weather2 Mod Showcase and Download]<br /> <br /> [//coros.us/wiki/index.php?title=Weather2_FAQ Weather2 FAQ]<br /> <br /> == Items ==<br /> <br /> === Weather Item ===<br /> <br /> https://coros.us/wiki/images/weather2/recipes/recipe_weather_item.png<br /> <br /> Used for crafting recipes only.<br /> <br /> === Placeable Sand Layer ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_placeable_sand_layer.png<br /> <br /> The item version of the Sand Layer block. Places down a single layer of sand, can stack up like snow layers<br /> <br /> === Pocket Sand! ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_pocket_sand.png<br /> <br /> The power of a sandstorm in your hands. Fires off a blast of sand particles and places down sand layer blocks just like a sandstorm would. Aim it at other players to blind them.<br /> <br /> == Blocks ==<br /> <br /> === Tornado Sensor ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_tornado_sensor.png<br /> <br /> === Tornado Siren ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_tornado_siren.png<br /> <br /> === Manual Redstone Siren ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_manual_redstone_siren.png<br /> <br /> === Wind Vane ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_wind_vane.png<br /> <br /> === Anemometer ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_anemometer.png<br /> <br /> === Weather Radar ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_weather_radar.png<br /> <br /> === Weather Machine ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_weather_machine.png<br /> <br /> === Weather Deflector ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_weather_deflector.png</div>

Corosus http://coros.us/wiki/index.php?title=Weather2_Main_Page&diff=21 2018-06-22T21:30:13Z

<p>Corosus: </p> <hr /> <div>== Main Links ==<br /> <br /> [//coros.us/mods/weather2 Mod Showcase and Download]<br /> <br /> [//coros.us/wiki/index.php?title=Weather2_FAQ Weather2 FAQ]<br /> <br /> == Items ==<br /> <br /> === Weather Item ===<br /> <br /> //coros.us/wiki/images/weather2/recipes/recipe_weather_item.png<br /> <br /> Used for crafting recipes only.<br /> <br /> === Placeable Sand Layer ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_placeable_sand_layer.png<br /> <br /> The item version of the Sand Layer block. Places down a single layer of sand, can stack up like snow layers<br /> <br /> === Pocket Sand! ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_pocket_sand.png<br /> <br /> The power of a sandstorm in your hands. Fires off a blast of sand particles and places down sand layer blocks just like a sandstorm would. Aim it at other players to blind them.<br /> <br /> == Blocks ==<br /> <br /> === Tornado Sensor ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_tornado_sensor.png<br /> <br /> === Tornado Siren ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_tornado_siren.png<br /> <br /> === Manual Redstone Siren ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_manual_redstone_siren.png<br /> <br /> === Wind Vane ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_wind_vane.png<br /> <br /> === Anemometer ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_anemometer.png<br /> <br /> === Weather Radar ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_weather_radar.png<br /> <br /> === Weather Machine ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_weather_machine.png<br /> <br /> === Weather Deflector ===<br /> <br /> http://coros.us/wiki/images/weather2/recipes/recipe_weather_deflector.png</div>

Corosus