Kosmos- by Tlatoani 
World management, custom generation, world borders, and more
Events
2
Expressions
28
Effects
7
Conditions
4
Types
6
Sections
0
Structures
0
Total
47
Kosmos- by Tlatoani
BETA.4: Fixed an issue with the normal dimension 1729 days, 18 hours and 40 minutes ago
This is a very small update to address a small issue:
Kosmos has a dimension type that refers to the three dimensions (the overworld, the nether, and the end), but the overworld was referred to as `normal`, which is an issue as `normal` is also used by Skript as a difficulty, which caused `normal` to be recognized as a difficulty in situations where it should have been recognized as a dimension.
To fix this, in Kosmos 1.0-BETA.4, you can now use `overworld` to refer to the overworld. I would recommend no longer using `normal` as a dimension in order to prevent these issues from occurring.
Kosmos 1949 days, 19 hours and 11 minutes ago
Kosmos is a Skript addon focused on providing a variety of world-related features such as world creation and management (including automatic loading on startup of worlds), world border manipulation, custom world generation, and more!
These features allow you create a world management system for your server entirely in Skript - meaning you can delete Multiverse or similar plugins, and fully customize the functionality to what you need, because that's the whole point of Skript.
You can also utilize its custom generation feature to create worlds that are fully customized to your needs, such as your own custom Skyblock worlds or infinitely sized cities. Kosmos also has a variety of other miscellaneous world-related features, like chunk syntaxes and 1.13 gamerule syntaxes. If you can't find your desired feature, just suggest it on the discussion page or in the Discord channel!
Check out Kosmos' website for more info! Also, consider joining the Skript Chat Discord Server to discuss Kosmos and other Skript addons in dedicated channels.
If you find bugs or have certain feature requests, I highly recommend you create an issue on GitHub, as that will ensure that I can address your concern instead of it being buried by other posts/messages.