No, you don't NEED a PAID host, I host my server right from my house and it sits right under my main PC. as long as you have a good internet connection with good upload speed then your good.
Agreed, but there are caveats.
Upload speed matters a lot, setup of the connection (NAT or blocked inbound traffic), and terms of service for the service provider (a lot of residential providers specifically forbid servers of any type).
I've been running a small MC server for a few people for years now on my business connection with no issues. For a short amount of time, I used a hosting company, but my users didn't really notice much of a difference, so I left.
That being said, a hosting provider is usually a lot easier, and if someone doesn't know basic networking and server administration (or if the provider simply doesn't allow it), it's strongly suggested to make use of a hosting company.
First, you need to see if your apartment service provider has you behind what is commonly called a NAT (it's a way to have multiple machines use a single public address).
If you are using windows, opening a command prompt and running ipconfig will show your network info. You will need to look for one of two lines, "Default gateway" or "IPv4 Address".
If either one has an address that is between these ranges:
192.168.0.0 -192.168.255.255
172.16.0.0 - 172.31.255.255
10.0.0.0 - 10.255.255.255
then your apartment provider has you behind a NAT and no one outside of your apartment complex, if even that, will be able to connect to you... unless the network admin for the complex is willing for forward some ports for you.
If you don't have an address in those ranges, in theory you should be able to have others connect to your machine, assuming any firewalls and such don't block connection attempts.
Port 25565 is the default used by minecraft, and if someone can reach your machine from the outside, they shouldn't need to specify the port unless you change it or have some fancier DNS SRV records configured (if you don't know what those are, don't worry about them, it's semi-advanced DNS stuff).
When it is red in the /plugin list it normally means its out of date.
Nooooo, the red means the plugin was loaded, or attempted to load, but wasn't activated for some reason. An out of date plugin that isn't compatible with the version of bukkit can cause this, but a config problem can cause it as well.
I don't know if I didn't explain right, I am sorry, but I want people to play and use all the perks from the ranks in the main World called world, and only survive in the World called survive.
So I want people to keep their ranks in main world, and only Survivor rank in survival, but I noticed it is impossible, between answers, I been testing, and trying different things... yet nothing worked, so, I give up, I will remove that world.
Hmm...
So the world "world" has all kinds of goodies, but "survive" is 'vanilla'... What I would look at doing is further splitting the permissions. You can have multiple world permission sets defined per group. A quick example:
Well I made it work perfectly as Survivor, even different perks than Guest, which is what I wanted... using the inherit, everything worked smoothly... and suddenly... once they came back to World "world" they became Guest rank... instead of their Member and Grand ranks...
Worlds used for the testing are "world" and "survive", linked via a pair of portals created using multiverse portals. I am part of the "Survivor" group.
When I connect to the test server in the world named "world", I am unable to do anything but walk thought the portal (multiverse.portal.access.*)
When I walk through the portal into the world "survive", I am able to break blocks and generally interact with the world (modifyworld.*)
When I walk back through the portal, I am once again unable to do anything but walk through the portal. This is what I expect to happen.
What is happening that makes you think that the players are going back to a previous group?
ummm..... I didn't get half of everything you explain I am so sorry.... I read it 6 times.... but I only get that you tried to set you as User with Permissions, instead of Member with permissions... also, I don't know if I miss it, but how do you make everyone that goes to Survival World, just by going there, change their ranks to Survivor?
Ok, there is part of the problem, I think.
When you go to a different world, under PEX, your rank doesn't change, but what sections PEX uses to determine your permissions does change.
Say someone is added to the survivor group, logs in and is in "world". Their permissions for "world" are empty as there is no definition for "world" in the "survivor" group.
Now if they are moved to the world "survive", they will have the modifyworld.* and essentials set home permissions.
If you want members of "survivor" to have the same permissions as the default group, you can either:
- Copy the full permissions from the default group, global and any world specific nodes
- Use group inheritance so the "Survivor" group 'inherits' the permissions that the default group has.
That inheritance line will make PEX check the default group for permissions if it can not find them defined in the "survivor" group. And as the group "default" has only global permissions defined (nothing under a worlds: header), the nodes listed under the "default" group will apply.
Ok, here is what I did for testing:
Set up a clean install of the same bukkit and PEX versions you have
Let the server generate a world set named "world", then made a "survive" world set
Added multiverse core and nether portals for multiworld support
Added your permissions with the following changes:
- removed the worlds: section at the bottom (tests permissions across worlds)
- removed the modifyworld.* from the default group
- removed all permissions from the survivor group for the survive world specific section
- removed the default: true line from the survivor group (there should only be one default line in a PEX permissions file)
Log in, get placed in the world survive
My testing:
mv list
[17:23:36 INFO]: ====[ Multiverse World List ]====
[17:23:36 INFO]: survive - NORMAL
[17:23:36 INFO]: survive_the_end - THE_END
[17:23:36 INFO]: world_the_end - THE_END
[17:23:36 INFO]: world_nether - NETHER
[17:23:36 INFO]: world - NORMAL
[17:23:36 INFO]: survive_nether - NETHER
>pex worlds
[17:41:33 INFO]: Worlds on server:
[17:41:33 INFO]: world
[17:41:33 INFO]: world_nether
[17:41:33 INFO]: world_the_end
[17:41:33 INFO]: survive_the_end
[17:41:33 INFO]: survive_nether
[17:41:33 INFO]: survive
>pex user bacon_avenger
[17:29:44 INFO]: 'bacon_avenger/bacon_avenger' is a member of:
[17:29:44 INFO]: default (not ranked)
[17:29:44 INFO]: bacon_avenger's permissions:
[17:29:44 INFO]:
[17:29:44 INFO]: bacon_avenger's options:
>pex user bacon_avenger list
[17:29:37 INFO]: bacon_avenger's permissions:
[17:29:37 INFO]: minekart.join
[17:29:37 INFO]: multiverse.portal.access.*
[17:29:37 INFO]: battlesheep.player
[17:29:37 INFO]: bmt.default
[17:29:37 INFO]: essentials.kit
[17:29:37 INFO]: essentials.kits
[17:29:37 INFO]: essentials.kit.food
[17:29:37 INFO]: essentials.kits.food
[17:29:37 INFO]: essentials.list
[17:29:37 INFO]: essentials.sethome
[17:29:37 INFO]: essentials.tpaccept
[17:29:37 INFO]: lwc.protect
[17:29:37 INFO]: essentials.tpdeny
[17:29:37 INFO]: essentials.spawn
[17:29:37 INFO]: essentials.signs.use.disposal
[17:29:37 INFO]: essentials.signs.use.info
[17:29:37 INFO]: essentials.signs.use.free
[17:29:37 INFO]: worldguard.region.wand
[17:29:37 INFO]: essentials.ping
[17:29:37 INFO]: essentials.signs.use.warp
[17:29:37 INFO]: essentials.rules
[17:29:37 INFO]: essentials.realname
[17:29:37 INFO]: essentials.msg
[17:29:37 INFO]: essentials.mail.send
[17:29:37 INFO]: essentials.mail
[17:29:37 INFO]: essentials.help
[17:29:37 INFO]: essentials.afk
[17:29:37 INFO]: essentials.home
>pex user bacon_avenger group set survivor
[17:34:48 INFO]: User groups set!
>pex user bacon_avenger list
[17:34:50 INFO]: bacon_avenger's permissions:
>pex user bacon_avenger list world
[17:34:52 INFO]: bacon_avenger's permissions:
>pex user bacon_avenger list survive
[17:34:55 INFO]: bacon_avenger's permissions:
[17:34:55 INFO]: modifyworld.*
If I try to do anything like interact with a block (break, place), I'm denied.
If I place myself into the group survivor, I'm able to interact with things but only in the survive world
This is as it should work.
Now, you might notice that I have a lack of permissions from the default group, such as multiverse.portal.access.*
This is by design. For my player to inherit the global permissions from the default group, I need to either:
- copy the permissions set from the default group, or...
- add an inheritance relationship between the survivor and default group.
>pex group survivor parents list
[17:43:56 INFO]: Group Survivor doesn't have parents
>pex group survivor parents add default
[17:44:00 INFO]: Group Survivor inheritance updated!
>pex group survivor parents list
[17:44:02 INFO]: Group Survivor parents:
[17:44:02 INFO]: default
Now when I do these commands, notice that modifyworld.* only shows up when I specify the survive world?
PEX is, unfortunately, is as picky as ever. If you are modifying the permissions, only do it from one place at a time (directly in the file, from the console, in-game) and always do a pex reload after making a change. With the caching it does now, it's really easy to get things out of sync between the file and what PEX thinks is in the file, or even worse, having PEX overwrite what you changed in the file with what it thinks is in there.
Quick question, where did you get this version number from?
I ask as when I was setting up a clean test server, I noticed that, by default, PEX has the auto-update feature, which updated the 1.21.3 version I had installed to 1.21.4, which isn't fully compatible with the version of bukkit you are using. Thought I'd check that really quick.
Please put your current permissions up somewhere and link to them here.
What version of bukkit and PEX are you using?
Can you give a specific example of what permission is not working as expected?
I'd like to try to reproduce it on a test server, but I need to know the exact details.
Ok, if I'm understanding your problem correctly, the permissions you have set up in the default group are being applied to all worlds, which is not what you want, correct?
As I don't know exactly what you want set up, I'm going to have to make a few assumptions and guesses, but hopefully this will apply and get you thinking in the right direction to apply it to everything else.
I'm only seeing one world defined in that list, named "survive", so I'm assuming that there are some permissions listed in the default group that you want globally and some that should apply to only in "survive".
What I would do is move the ones that should apply only to "survive" into it's own world group. For example (hopefully the code tags don't mangle it too badly for this small example):
Then, each group can inherit the perms from this group and you can add additional group perms per world for each group. As groups gain more permissions, you can inherit that group and PEX will follow the inheritance chain.
BTW, your last entry:
worlds:
survive:
inheritance:
- world
This is incorrect. You have the world named "survive" trying to inherit perms from a world named "world", which isn't defined anywhere in your permissions. If your survival world has a nether and the end set up, you will probably want to have those worlds inherit the permissions from "survive". The exact name to use for them depends on what multiverse named them (IIRC, it's usually something like survive_nether).
0
Agreed, but there are caveats.
Upload speed matters a lot, setup of the connection (NAT or blocked inbound traffic), and terms of service for the service provider (a lot of residential providers specifically forbid servers of any type).
I've been running a small MC server for a few people for years now on my business connection with no issues. For a short amount of time, I used a hosting company, but my users didn't really notice much of a difference, so I left.
That being said, a hosting provider is usually a lot easier, and if someone doesn't know basic networking and server administration (or if the provider simply doesn't allow it), it's strongly suggested to make use of a hosting company.
0
Umm, no, it's not quite that simple.
First, you need to see if your apartment service provider has you behind what is commonly called a NAT (it's a way to have multiple machines use a single public address).
If you are using windows, opening a command prompt and running ipconfig will show your network info. You will need to look for one of two lines, "Default gateway" or "IPv4 Address".
If either one has an address that is between these ranges:
then your apartment provider has you behind a NAT and no one outside of your apartment complex, if even that, will be able to connect to you... unless the network admin for the complex is willing for forward some ports for you.
If you don't have an address in those ranges, in theory you should be able to have others connect to your machine, assuming any firewalls and such don't block connection attempts.
Port 25565 is the default used by minecraft, and if someone can reach your machine from the outside, they shouldn't need to specify the port unless you change it or have some fancier DNS SRV records configured (if you don't know what those are, don't worry about them, it's semi-advanced DNS stuff).
0
Specifically, https://github.com/PEXPlugins/PermissionsEx/wiki/Basic-Permissions-Setup#kitchen-sink-notes
This has bitten quite a few people new to how PEX parses permission nodes.
0
0
The PEX config file uses YAML for it's config format, and YAML is very picky about it's formatting.
If what you put in the post is accurate, your formatting is off.
Also, your server console log should be showing any errors that appear when the server attempts to load PEX, check there as well.
Considering you didn't post your bukkit version, saying that it's simply not compatible is just speculation.
0
0
So the world "world" has all kinds of goodies, but "survive" is 'vanilla'... What I would look at doing is further splitting the permissions. You can have multiple world permission sets defined per group. A quick example:
groups: default: default: true permissions: - multiverse.portal.access.* options: prefix: '&c[&2Guest&c]&7 ' Survivor: inheritance: - default worlds: survive: options: prefix: '&c[&5Survivor&c]&3 ' permissions: - modifyworld.* main: permissions: - modifyworld.* - super.world.only.permWith this, the Survivor group will have the super.world.only.perm permission, but only when they are in the world called "main".
Multiworld and inheritance can become a bit of a tangled mess, I know, but if you break it down step by step, it can do some really nifty things.
0
This is what I have set up right now:
groups: default: default: true permissions: - multiverse.portal.access.* options: prefix: '&c[&2Guest&c]&7 ' Survivor: worlds: survive: options: prefix: '&c[&5Survivor&c]&3 ' permissions: - modifyworld.* inheritance: - defaultWorlds used for the testing are "world" and "survive", linked via a pair of portals created using multiverse portals. I am part of the "Survivor" group.
When I connect to the test server in the world named "world", I am unable to do anything but walk thought the portal (multiverse.portal.access.*)
When I walk through the portal into the world "survive", I am able to break blocks and generally interact with the world (modifyworld.*)
When I walk back through the portal, I am once again unable to do anything but walk through the portal. This is what I expect to happen.
What is happening that makes you think that the players are going back to a previous group?
0
When you go to a different world, under PEX, your rank doesn't change, but what sections PEX uses to determine your permissions does change.
Lets assume your permissions look like this:
groups: default: default: true permissions: - minekart.join - multiverse.portal.access.* - battlesheep.player - bmt.default - essentials.kit - essentials.kits - essentials.kit.food Survivor: worlds: survive: options: prefix: '&c[&5Survivor&c]&3 ' default: true permissions: - modifyworld.* - multiverse.portal.access.* - essentials.sethomeSay someone is added to the survivor group, logs in and is in "world". Their permissions for "world" are empty as there is no definition for "world" in the "survivor" group.
Now if they are moved to the world "survive", they will have the modifyworld.* and essentials set home permissions.
If you want members of "survivor" to have the same permissions as the default group, you can either:
- Copy the full permissions from the default group, global and any world specific nodes
- Use group inheritance so the "Survivor" group 'inherits' the permissions that the default group has.
Survivor: inheritance: - default worlds: survive: options: prefix: '&c[&5Survivor&c]&3 ' default: true permissions: - modifyworld.* - essentials.sethomeThat inheritance line will make PEX check the default group for permissions if it can not find them defined in the "survivor" group. And as the group "default" has only global permissions defined (nothing under a worlds: header), the nodes listed under the "default" group will apply.
0
Ok, here is what I did for testing:
Set up a clean install of the same bukkit and PEX versions you have
Let the server generate a world set named "world", then made a "survive" world set
Added multiverse core and nether portals for multiworld support
Added your permissions with the following changes:
- removed the worlds: section at the bottom (tests permissions across worlds)
- removed the modifyworld.* from the default group
- removed all permissions from the survivor group for the survive world specific section
- removed the default: true line from the survivor group (there should only be one default line in a PEX permissions file)
Log in, get placed in the world survive
My testing:
If I try to do anything like interact with a block (break, place), I'm denied.
If I place myself into the group survivor, I'm able to interact with things but only in the survive world
This is as it should work.
Now, you might notice that I have a lack of permissions from the default group, such as multiverse.portal.access.*
This is by design. For my player to inherit the global permissions from the default group, I need to either:
- copy the permissions set from the default group, or...
- add an inheritance relationship between the survivor and default group.
Now when I do these commands, notice that modifyworld.* only shows up when I specify the survive world?
Does this help any?
PEX is, unfortunately, is as picky as ever. If you are modifying the permissions, only do it from one place at a time (directly in the file, from the console, in-game) and always do a pex reload after making a change. With the caching it does now, it's really easy to get things out of sync between the file and what PEX thinks is in the file, or even worse, having PEX overwrite what you changed in the file with what it thinks is in there.
0
I ask as when I was setting up a clean test server, I noticed that, by default, PEX has the auto-update feature, which updated the 1.21.3 version I had installed to 1.21.4, which isn't fully compatible with the version of bukkit you are using. Thought I'd check that really quick.
0
Please put your current permissions up somewhere and link to them here.
What version of bukkit and PEX are you using?
Can you give a specific example of what permission is not working as expected?
I'd like to try to reproduce it on a test server, but I need to know the exact details.
0
*looks*
Ok, if I'm understanding your problem correctly, the permissions you have set up in the default group are being applied to all worlds, which is not what you want, correct?
As I don't know exactly what you want set up, I'm going to have to make a few assumptions and guesses, but hopefully this will apply and get you thinking in the right direction to apply it to everything else.
I'm only seeing one world defined in that list, named "survive", so I'm assuming that there are some permissions listed in the default group that you want globally and some that should apply to only in "survive".
What I would do is move the ones that should apply only to "survive" into it's own world group. For example (hopefully the code tags don't mangle it too badly for this small example):
Then, each group can inherit the perms from this group and you can add additional group perms per world for each group. As groups gain more permissions, you can inherit that group and PEX will follow the inheritance chain.
BTW, your last entry:
worlds: survive: inheritance: - worldThis is incorrect. You have the world named "survive" trying to inherit perms from a world named "world", which isn't defined anywhere in your permissions. If your survival world has a nether and the end set up, you will probably want to have those worlds inherit the permissions from "survive". The exact name to use for them depends on what multiverse named them (IIRC, it's usually something like survive_nether).Does this help any?
0
Without seeing your full permissions list on something like pastie, pastebin, etc, I'm not able to really say where the problem is.
0
https://github.com/PEXPlugins/PermissionsEx/wiki/Advanced-permissions-setup#pex-multiworld