Spider Nest +

fixed wrong import

Now natively support Spanish and German as a language. If you wish to have your plugin translated into one of those, simply choose "es_ES" or "ger" as your language-setting. If you see any spelling errors or typos, please let me know

Now supports WorldGuard regions New Features: · Selectors may now include WorldGuard-regions (denoted by the option "region" · added /sn info to display the loaded spider-nests including their selectors, and effects WorldGuard support: As mentioned above, you can now also use defined WorldGuard regions inside a selector. Suppose you have claimed a region called "myRegion" that you do not want spiders to spawn out of cobwebs out. You would, in that case, include the option: Code (YAML): - notIf [region=myRegion ] The special region "__global__" may be used to access any region that does not contain any claimed regions. Suppose you only want to spawn spiders out of cobwebs, if no one has claimed that region; you could use: Code (YAML): - onlyIf [region=__global__ ] in your global selector section.

There are some more changes on the way soon, but I wanted to split up that one big change into two small changes to adapt better Changes · Effects can now be applied when spiders spawn. Read more below this · Selectors can now be applied globally, meaning to any Spider-set (in addition to only applying them to a certain set/a certain set-content) · Added generic biomes. Instead of having to apply the selector to all sorts of variants, you can instead write for example generic:desert to include minecraft:desert, minecraft:desert_hills and minecraft:desert_lakes Effect-Selector Go even more custom by adding effects! Those effects are written like selectors and can be introduced wherever selectors are. The syntax is the following: Code (YAML): - effect [id='id', duration='duration', amplifier='amplifier', chance='chance' ] The effect has to be a Minecraft-key, for example minecraft:invisibility The duration is not mandatory and will default to -1 (meaning an infinite duration of the effect) The amplifier is not mandatory as well and will default to 1 The chance is not mandatory as well, however, it will default to 0, therefore it should be specified every time. Different effects can be separated the same way selectors can be separated (using the '|' identifier). If multiple effects are given and only one (resp. less than the number of ids are given), the last id is taken. For example: Code (YAML): - effect [id=minecraft:invisibility|minecraft:speed, duration=-1, amplifier=1|255, chance=0.01 ] will apply the effects of invisibility and speed. Both will have a duration of -1 (meaning infinite), however, invisibility will have an amplifier of 1 while the effect 'speed' will have an amplifier of 255. What is upcoming? One feature-request is that cobwebs that have been placed by the player should not spawn spiders if that is specified in the config. The other thing that I will be looking into pretty soon is the ability to include WorldGuard-regions into the selectors (still haven't found the time to do so, unfortunately) Thank you for reading and I hope you enjoy this update!

As promised, the new update brings some enhancements to selectors New Features · Added options 'permission' (checks for the permission of the player that broke the cobweb) and 'world' (checks for the world that the cobweb is in). The latter option can be seen as an addition to the blacklist/whitelist behavior of the selected worlds to fine-tune the spawning behavior · Selectors can now be applied to a whole set. To do this, you have to add 'option' in the 'spawns' section. Doing this is equivalent to setting the Selector to both SPIDER and CAVE_SPIDER Bug-fixes / Enhancement · If an error occurred while parsing a Selector, the message will now be more informative · Fixed a bug where only the last letter of the debug-message would be shown · Fixed a bug where a chance higher than one would not be correctly displayed as an error · Fixed a typo in the default config ('desert' vs 'dessert')

This is a small update front-end but it's gonna enable a lot of features that are coming soon. New Features: · Introducing Selectors. Read more below this · Soft-depends on Multiverse-Core and MultiWorld for better compatibility with Multiverse-plugins. · More Infos in the debug-message (date, location, spawners are more precise), if broadcast_to_op is active, a reduced version will be sent · Added some missing prefixes in several messages · Spiders will now spawn inside the block, not on the edge Selectors Selectors enable you to be even more precise on how to control spider nets. You can control, for example, if certain SpiderNest's should only spawn in certain biomes or only on the surface/underworld. Please note: Selectors are a relatively new feature. Even thou they have been tested quite exhaustively, they might still not be perfect. They will, for example, fail silently if any biome-key has typos. If you notice anything strange (other than that), please report it here. How do you add Selectors? Selectors can currently only be applied to the SPIDER/CAVE_SPIDER section of your config. There can be multiple selectors for a single SPIDER/CAVE_SPIDER-section. See the ending example for details. What is the Syntax for Selectors? A Selector has the following Syntax: type[option1=value1|value2,option2=value1|value2] The type is a general function that should be applied. Currently, there are two options: onlyIf and notIf The option is what should be filtered out. There are also only two options (more to come soon). These two options are: biome and surface The values are the things that should be filtered out. You can define multiple values using this '|' symbol. Currently, the only value that this makes sense for is the biome value. In this case, the biomes that should be included or excluded have to be in a valid Minecraft format (e.g. minecraft:forest) What will future updates bring? I'm open to any feature requests! The plan is to enable Selectors not only for a certain section but for a whole net as well as for a world. After that's done, I'm looking to add an option for WorldGuard regions. Stay tuned for that! Great! Can I have an example? Here you go: Code (YAML): sets : # If you want to apply the selectors to both spiders and cave-spiders, # you currently will have to apply these selectors to both SMALL: chance : 1.0 spawns : # The old Syntax still works. If you want to apply selectors, however, # you will have to put the number of spiders to spawn into a separate field. CAVE_SPIDER : 1 SPIDER: count : 1 # all selectors have to be put under options options : # Regular spiders will not spawn if the cobweb got destroyed in overworld - notIf [surface=overworld ] # Regular spiders will only spawn if the cobweb got destroyed in a forest or desert - onlyIf [biome=minecraft:forest|minecraft:desert ]

The bug should be fixed. For a simple example that I tried (creating a server with the options --universe), the plugin worked as expected New Features: · Added command /sn reload to reload the config · A verbosity level can be set in config. This has 3 configuration options: silent: Will not log any debug messages; console: will log debug messages to the console. Those consist of the destroyed spider nest and the player that destroyed it; broadcast_to_op: Will additionally broadcast any debug messages to any op's on the server Changes: · fixed some naming in-consistencies · renamed 'default_config.yml' to 'config.yml' · now uses standard entity names SPIDER and CAVE_SPIDER (the legacy names will no longer work) Removals: · The plugin will no longer save the config on disabling thus preserving the config's state Bug-Fixes: · Fixed a bug that would not load worlds correctly when using the --universe option

New day, new update! additions: · choose on which worlds you want to enable this plugin. You can make a selection of worlds and the choose between blacklist (all worlds except the blacklisted will spawn spiders out of nests), whitelist (all worlds defined will spawn spiders out of nests), or any (the list will be ignored and any world will spawn spiders). The default is "any". If the name is incorrect, nothing will spawn · Now supports multiple languages. Languages can be added in a '.lang' format. The default language is en_US.lang and will be added on a first startup (or if no other language-file exists) · You can now change the plugin-prefix (defaults to SpiderNest) changes: · The surprise messages are now in the language-file and can no longer be set in the config. Messages that will get recognized as such surprise-messages must start with the prefix 'message.surprise'. The postfix is irrelevant but should be set to something sensible

· Set a flag to determine whether or not spider should spawn if the player broke the cobweb without destroying it (for example using shears or a silk-touch enchanted item) · Set custom messages that appear whenever spider nests get destroyed · spiders will spawn exactly where the cobweb was · spiders will now be instantly aggressive towards the player, even on daytime · added a default-config that will get set if no config is available