My suggestion as above. Would it be possible to have a config option in forge where server admins can have all the chunk loaders for a user automatically turn off when they disconnect.

 

That would be a mod option, go and talk to your mod makers.

It does make sense, on a forge level.

When a user logs off, invalidate all chunkloading tickets a user holds. It would have to be done at the forge level, not the mod level. You don't want to have to toggle the setting in 166 different config files, do you?

It does make sense, on a forge level.

When a user logs off, invalidate all chunkloading tickets a user holds. It would have to be done at the forge level, not the mod level. You don't want to have to toggle the setting in 166 different config files, do you?

 

Exactly my point. One config file, one TRUE / FALSE conditional to set in the configs. I know the admins of the server I play on would LOVE this feature.

 

but that requires mods to link the ticket to the user

 

this not trivial once you start using items that can place blocks (RP2 deployers, CC turtles) who is then responsible for the chunk loader

Nah. I think I'll see if the devs have any input.

but that requires mods to link the ticket to the user

 

this not trivial once you start using items that can place blocks (RP2 deployers, CC turtles) who is then responsible for the chunk loader

 

Inherited permissions? Owner of the deployer / turtle owns the chunk loader.

 

-snip-

 

Inherited permissions? Owner of the deployer / turtle owns the chunk loader.

 

that would require ALL tile entities that can place blocks to record who track who owns it and pass that info along to each potential block it places that may place a block itself, there is currently no system in place to do anything like that

that would require ALL tile entities that can place blocks to record who track who owns it and pass that info along to each potential block it places that may place a block itself, there is currently no system in place to do anything like that

 

Okay then, a server config option that if the chunk loader block wasn't placed by a person (no owner) then it will not function.

 

More configs are good.

 

This still is not qualifying for a forge feature, but possibly a dedicated mod feature.

 

One could do this in a mod quite easily, when a player places a chunkloader, map the player to those coordinates, when he logs out, replace it with a unremovable(except by ops) sign with the user and chunkloader that would have been there, and replace it when the user logs back in.

 

Would not be very difficult to accomplish, and would not be hard for the author to keep it updated with the current various chunk loaders(or add in a config for the admins to add to).

 

If the chunkloader has a null player who placed it(like some kind of deployer) then the mod could simply break the chunk loader.

Chicken bones chunkloader does this.