I see the dev version is in development

But I looked at the configuration file and it seems that there is no blacklist features, I want to disabled the create and use in some worlds

Like this:

#What worlds should the plugin features be disabled in.
DisabledWorlds:

• 'example_world'

Hello!

Current Per-World Functionality

Per-world functionality is currently handled permission-side (as such, there is currently no config interface)

Stargate-Level Node Handling:

Stargate provides several nodes designed to control any portal interactions which might exit in a specified world:

• Users with sg.use.world.example_world set to false will be unable to use portals that would exit in example_world
• Users with sg.create.world.example_world set to false will not be able to make portals that exit in example_world
• Users with sg.destroy.world.example_world set to false will not be able to destroy portals that exit in example_world

Manager-Level Node Handling:

Any modern perm manager (such as LP) can handle SG's nodes within a per-world context:

• When sg.<node> is set to false within a context of world=example_world, the node will be denied to users in that world.

Current (Permission-Based) Solution:

Using LP syntax as an example, typing the following four commands would effectively disable example_world:

lp group default permission set sg.use.world.example_world false
lp group default permission set sg.create.world.example_world false
lp group default permission set sg.use false world=example_world
lp group default permission set sg.create false world=example_world

Possible Improvements

Improved Permission Solution

We would be open to adding a sg.preset.disable_world.<name> node that groups those four nodes together.
That would probably help to simplify the process while remaining permission-based.

Configuration Solution

We would also be open to adding an advanced key for disabledWorlds.