Inactive [ADMN/GEN/INFO/TP/RPG] MyWorlds v1.48 - Multi-world plugin with a touch [2320]

Discussion in 'Inactive/Unsupported Plugins' started by bergerkiller, Aug 15, 2011.

  1. Offline

    bergerkiller

    [​IMG]

    You may wonder, why so many tags? Well, that is because this plugin simply contains a lot of features that fall under those tags! I originally made (parts of) this plugin for our server, but it proofed to be a 'publishable' plugin as well. :)

    Description

    This plugin features everything related to worlds. Features:
    • Load, unload, copy, delete, save and create worlds
    • Show information of worlds and list available chunk generators and worlds
    • Set world game mode, difficulty, time, weather, autosaving, PvP
    • Set world mob spawn restrictions
    • Evacuate worlds to clear them from players
    • Repair broken worlds to some extend
    • Make portals cross-world, one-way, simple, no commands needed
    • World-specific chat rooms using permissions
    • Automatically load worlds when the server starts and persistent settings
    • Extensive permission system, you can even set who can enter what world
    • Can act as a tool for other plugins to teleport players from one world to the other
    • Simple teleportation commands
    • Set OP lists for specific worlds to make players operator on certain worlds
    • Easy-to-remember commands: with aliases and chat-message help
    A nice tutorial by FrozdY



    BukkitDev page

    For configuration, commands, etc, look on the BukkitDev page under Links.
    All documentation pages are now on Bukkit Dev.

    Known bugs:
    - None
    Disclaimer (because things CAN go wrong)

    I am not responsible for world damages done by this plugin or by certain commands this plugin performs. If you, for example, loaded 20 worlds and hosted it on a buggy computer with 30 players, odds are the server (and your computer) will crash and worlds become corrupted. Repair can fix worlds, but this does not recover damaged chunks, so don't think you are always covered. Also, never forget to make backups of your worlds, but I guess this is common sense...

    FAQ:
    - Different inventories per world? No, you can use World Inventories for that.
    - Or try MultiInv while it is still maintained.
    - Repair ruined your world? Backup of region files can be found in the region folder, simply restore.


    Important links:

    Download the MyWorlds.jar from GitHub
    Look at the source at GitHub
    BukkitDev page

    Changelog

    Show your appreciation for my plugins by donating
    [​IMG]
     
  2. Offline

    Race Pro Kid

    That's what I do. I press Ctrl+Q in Pail to close it. Wait... does it matter?
     
  3. Offline

    kaasinees

    you have to type stop in the console otherwise nothing is saved... i dont think the sevrer handles ctrl+q
     
  4. Offline

    Race Pro Kid

    It only started happening a couple days ago... It was fine before then.
     
  5. Offline

    bergerkiller

    @Race Pro Kid you probably disabled auto saving (/save-off), right then you need to perform a (global) world save before closing. And yes, /stop is a golden rule.
     
    xVEGASxJUGGALOx likes this.
  6. Offline

    KaLul

    yes its worlguard and essentials what iam using for what i know its able to change the weather or let it keep.... wel i think i try some things out now. i tell u if i got it working! danke :)

    GREAT! I had always_rain set to true :S in worldguard for all worlds. thanks! now it works!
     
  7. Offline

    jespertheend

    hey,

    I think I've found a bug:
    when you delete a portal in the porals.txt and log in with a player that was in the map from the portal. The console will crash without any errors
     
  8. Offline

    bergerkiller

    @jespertheend that is highly unlikely, since the portals.txt is never touched while the plugin runs. Only when using /stop or /reload will it save the portals.txt, and only when loading and /reloading will it load it.
     
  9. Offline

    ledhead900

    @bergerkiller
    I found a flaw in "/world spawn worldname"

    If I give "myworlds.world.spawn" to a group it allows them to spawn to any world loaded, but if I do something like "myworlds.world.spawn.worldname" I lose permissions.

    I think you might want to fix this by making nodes per world spawn or not allow spawning to other worlds.
     
  10. Offline

    bergerkiller

    @ledhead900 If you want to restrict world entering, use:
    Instead. The spawn permission only applies for the /world spawn command.

    You need to set it to false/no by default first, since it's set on true for everyone by default.
     
  11. Offline

    ledhead900

    Huh, well that makes no sense I would assume that spawn would only let them spawn in the current world they are in, Not also allow them to spawn in other worlds by doing.

    /world spawn
    /world spawn worldb

    The later is what I want to stop I only want spawn command to allow spawning back to the spawn of the world they are in not limit the worlds in general I want all groups to have unrestricted access to all worlds I just don't want them using the spawn command to jump to worlds, You already have a /world tp worldname so I don't know why you let /world spawn worldname do the same thing.
     
  12. Offline

    bergerkiller

    @ledhead900 Shall I add a teleport permission too?
    Which will only apply for the /tpp and /world spawn commands?
     
  13. Offline

    ledhead900

    Na I am just confused on what its doing, I thought the world enter permissions were only to enable the requirement of permissions nodes to enter a world, Just like the portal enter permission setting in config, That is 100% not what I want to do. I don't need to restrict people from entering worlds per say like currently I have a 2 worlds, world and nether.

    I just was expecting the /world spawn command to not allow users to travel to the spawns of other worlds with out permissions like myworlds.world.spawn.*, you get what I mean now?, Its not that I want to enable permissions nodes per world as I don't I'm not trying to choose groups who can enter A but not B.

    It just surprised me as it was the first time I bothered to test if the spawn command would let a guest spawn to the spawn of any world on the server, I only tested it under OP and admin '*' until now so those rules did not apply to me, Hence why I was shocked since no other world-manger would let a user spawn to another worlds spawn with out a permissions node letting them do so.

    What I meant in my other post was that instead of allowing /world spawn to tp any group to any worlds spawn just make a sub node like myworld.world.spawn.any, to allow the user to jump to the spawn of any loaded world and if the user does not have this node make it act every other spawn command where they get sent to the current worlds spawn only.
     
  14. Offline

    bergerkiller

    @ledhead900 yup, that's why I added the world.enter permission: to prevent your guests from spawning/entering/teleporting to other worlds. /world spawn and /tpp share the same characteristics, only difference is that /tpp also works for portals. My guess is that you don't want players to teleport to world1 from world1_nether without entering a portal...yeah then it could be an issue. /world spawn and /tpp are basically fast-portals.
     
  15. Offline

    ledhead900

    Yea that is the issue, I edited my above post btw, I'm just surprised it worked that way as it was never explained in the OP that in order to prevent that you had to setup permissions and enable it per group. To me it read like if I wanted to restrict access to worlds in general not just via portals I would then enable it.

    If I wanted guests to not go to world B but members group could I would choose per world permission nodes but as for /spawn commands the rule of thumb I tend to see on every single plugin dealing with spawns is that if a user does not have a node to allow xross world spawn travel they can't, normally /spawn should only spawn you on the current world your on. Most developers have an alternate command such as /world tp to quick travel to other worlds.

    So it's half my mistake I guess by reading it wrong.


    I was used to multiverse tho as well, they have groups in config to enable or disable certain groups traveling to the world period regardless if it was from portal or not. The /spawn command always acted like it should it was not a quick tp command it a re-spawn command that's just my opinion, I rather not setup per world permissions as I said I'm not trying to prevent people from accessing the worlds normally thru a portal I just want don't them quick traveling via spawn command.

    I'm going to bed so If I have to I will muck around with world nodes later on but it would be a lot simpler to just re factor how it worked so that you only enable the permissions options if you to to physically limit groups going to a certain world in any possible way. I understand the portal nodes they let me stop a certain group from using a portal named hurr but allow travel thru durr.
     
  16. Offline

    Pixiio

    Every time i restart the server, i have to load my creative map again. Why is this?

    Thank you!
     
  17. Offline

    bergerkiller

    @Pixiio make sure you stop the server using /stop and don't close the console window instead.

    ok updated it to add teleport permissions (only apply to /tpp and /world spawn) and to add additional gamemode setters.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 18, 2016
  18. Offline

    Silentshok23

    LOVE THIS PLUGIN OMFG!!!!! gj - one suggestion ... can you make it so that in one world you OP in other your not? since i have a build world and the other is legit i dont want people using their toomanyitems in the legit world .. Much aprreciated
     
  19. Offline

    bergerkiller

    @Silentshok23
    - You can set an OP list for worlds-specific (disobiding the general op info)
    I could add a /world op and /world deop command to set this list. Note that the default (global) OP list is then no longer used as soon a world has at least on OP player set.

    I'll add that tomorrow, is a nice addition.
     
    ledhead900 and xVEGASxJUGGALOx like this.
  20. Offline

    kaasinees

    /wold allowspawn does not show which mobs are allowed to spawn.
    edit: can you make it so global OP list persists? i dont want to lose OP just because i didnt set myself on the OP list of a world.
     
  21. Offline

    bergerkiller

    @kaasinees I'll see if I can read and set world OP lists to the default OP list if it is empty.
     
    kaasinees likes this.
  22. Offline

    gimli59

    Why only I can build in the worlds?
    Can you explaim it
     
  23. Offline

    bergerkiller

    @gimli59 you are not OP or haven't set up the permissions correctly?
     
  24. Offline

    TheCrazyOne

    Is it possible to remove a portal? Because removing it from the portals.txt doesnt work.
     
  25. Offline

    bergerkiller

    @TheCrazyOne you will have to stop the server and then remove from portals.txt, else it won't work. Other than that, you can use /tpp to look for missing portals. Place a portal block nearby, enter it and it auto-removes the missing portal.
     
  26. Offline

    TheCrazyOne

    Thnx fixed the problem ;) I just deleted the lines inside the document.
     
  27. Offline

    gimli59

    So I need to install permissions 3?
     
  28. Offline

    bergerkiller

    @gimli59 I recommend looking into the Bukkit permissions: it is natively supported. I believe Permissions 3.* broke in the last few builds, but I still support it for the heck of it. :)
     
  29. Offline

    gimli59

    I can't still build in the worlds. O i hate it :(
     
  30. Offline

    bergerkiller

    @gimli59 what if you remove regions made by Worldguard or Regios?
     
  31. Offline

    gimli59

    Thanks now i can build :D
     

Share This Page