search

jonryf / EpicWorldGenerator-bugtracker

The most powerfull world generator made for minecraft
https://www.spigotmc.org/resources/epicworldgenerator-1-8-8-1-13-2-beta-support-for-1-14-support-all-update-aquatic-features.8067/
10 stars 0 forks source link

Allowing EWG to only work on whitelisted server names #151

Closed RealisticCorn closed 3 years ago

RealisticCorn commented 3 years ago

Hello, I am using a plugin called World System where it creates an individual world for each player when they type /ws get. I don't want EWG to work on the world created by World System but the blacklist feature on EWG doesn't work because the world created by World System has random long names depending on the player's username. If EWG has a whitelist only option, then I can just write the world name that I want EWG to work on there. For my alternative, I tried using RWG instead and it didn't have a conflict with the World System plugin.

JakeNijssen commented 3 years ago

I see where your issue lies, but there is another option, just add a ëmpty file in the created world folder before it iniatilizes called: epicworldgenerator.lock" Then it will not use ewg on that world

reverendjesus commented 3 years ago

I see where your issue lies, but there is another option, just add a ëmpty file in the created world folder before it iniatilizes called: epicworldgenerator.lock" Then it will not use ewg on that world

This is an absolutely, completely unacceptable solution. Some plugins (such as the one the OP is referencing) create worlds on the fly, with dynamic world names; some plugins create a separate world for each player. This workaround would require manually adding a file to the world folder every time a new player logs in/uses their resource world. I have been completely unable to use this plugin for the entire time I've owned it due to this massively fatal flaw, which literally no other current world generator shares.

JakeNijssen commented 3 years ago

I see where your issue lies, but there is another option, just add a ëmpty file in the created world folder before it iniatilizes called: epicworldgenerator.lock" Then it will not use ewg on that world

This is an absolutely, completely unacceptable solution. Some plugins (such as the one the OP is referencing) create worlds on the fly, with dynamic world names; some plugins create a separate world for each player. This workaround would require manually adding a file to the world folder every time a new player logs in/uses their resource world. I have been completely unable to use this plugin for the entire time I've owned it due to this massively fatal flaw, which literally no other current world generator shares.

Can't you just create world presets? With such a file in it? But anyways if this is a real issue then I'll go ahead and change up the config so this issue goes away. I hope to add this once @jonryf pushes his commit to the GitHub.

But as an alternative, isn't it possible to force a certain preset in WorldSystem to always make the file in the world folder?

F9Alejandro commented 3 years ago

@YourPalJake having another plugin do the work for what should already be handled by the EWG plugin is not fair for the other plugin devs, nor for the users who buy the plugin and have to jump through extra hoops just to get one thing working that could be handled easily by another.

jonryf commented 3 years ago

Will be included in next version