Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to remove all restrictions #3013

Open
KeeveeKoomoo opened this issue Jan 29, 2024 · 29 comments
Open

Option to remove all restrictions #3013

KeeveeKoomoo opened this issue Jan 29, 2024 · 29 comments

Comments

@KeeveeKoomoo
Copy link

I wanna run a crossplay server that plays as if I were hosting a vanilla server. To my knowledge vanilla servers don't allow the use of plugins, and I need a crossplay plugin. I just want everybody who joins to be able to build on spawn, or to summon bosses, etc etc.

I'd like it so I could just run a command and then it would remove all the restrictions added by Tshock.

I saw a similar post saying I could run this command:
"group addperm guest tshock.ignore.* tshock.world.modify tshock.partychat tshock.thirdperson tshock.canchat tshock.sendemoji tshock.world.movenpc tshock.npc.startinvasion tshock.npc.summonboss tshock.world.paint tshock.world.converthardmode tshock.tp.rod tshock.tp.pylon tshock.tp.wormhole tshock.npc.hurttown tshock.npc.startdd2 tshock.npc.spawnpets"
and simply adding players to the guest group, however this didn't work and we still can't build on the spawn area, and I worry that means we won't be able to summon bosses and thus progress through the game. I also checked out smthn called "Vanillifier" but their github page doesn't have any releases, and to be completely honest, given my past experience with building and cmake and other stuff in that sort of area, I really can't be bothered with it.

@ghost
Copy link

ghost commented Jan 29, 2024 via email

@ghost
Copy link

ghost commented Jan 29, 2024

Give every role the permission "*" but make sure you have a password so it doesn't go to hell
That's my only thought

@KeeveeKoomoo
Copy link
Author

so like "group addperm guest *" as an example?

@ghost
Copy link

ghost commented Jan 29, 2024

yes

@ghost
Copy link

ghost commented Jan 29, 2024

and repeat that with owner too or log out

@KeeveeKoomoo
Copy link
Author

KeeveeKoomoo commented Jan 29, 2024

Restarted the server after using the command, still can't build on spawn, is this perhaps an issue with the configs rather than the ingame permissions?
(Only asking because I don't know how to check myself)

@sgkoishi
Copy link
Member

Do not give the * permission - it allows everything, including but not limited to, spamming the server with items and projectiles and bosses, killing every player, destroying every tile, banning you and whomever they want, and turning off your server.

For the spawn protection, /group addperm guest tshock.world.editspawn probably

If it still doesn't work if you did the * or editspawn one, you probably did something wrong - e.g. they are not guest or you made some typo or whatever

@ghost
Copy link

ghost commented Jan 29, 2024 via email

@KeeveeKoomoo
Copy link
Author

KeeveeKoomoo commented Jan 29, 2024

I'm playing with a friend I trust, I don't care if he has those perms cuz I know he won't abuse them. Thing is, I've added him and I to the group "owner", and gave said group the * permission, and still can't edit spawn. We've restarted the server a couple times now, it's just not working.

Something that's probably noteworthy, despite the fact we are both owners, I can only access the commands via the command prompt. Neither of use can access the commands ingame.

@ghost
Copy link

ghost commented Jan 29, 2024 via email

@sgkoishi
Copy link
Member

By Neither of use can access the commands ingame. do you mean you can only see a few (like 10 or 15) commands in the game? If so, can you take a screenshot of your command prompt when you add permissions and set the owner?

@KeeveeKoomoo
Copy link
Author

I mean when trying to use any command the game chat simply returns "You do not have access to this command."
The command prompt returns "Player tried to execute /group addperm owner *", as I was attempting to make the change ingame to see if it would make a difference.

@ghost
Copy link

ghost commented Jan 29, 2024 via email

@KeeveeKoomoo
Copy link
Author

I did use the console I already said here that it hasn't made a difference. Unless you're not referring to the server command prompt window.

I'm playing with a friend I trust, I don't care if he has those perms cuz I know he won't abuse them. Thing is, I've added him and I to the group "owner", and gave said group the * permission, and still can't edit spawn. We've restarted the server a couple times now, it's just not working.

Something that's probably noteworthy, despite the fact we are both owners, I can only access the commands via the command prompt. Neither of use can access the commands ingame.

@ghost
Copy link

ghost commented Jan 29, 2024 via email

@sgkoishi
Copy link
Member

sgkoishi commented Jan 29, 2024

Run the group addperm guest tshock.world.editspawn with your command prompt (not in the game). And, no need to restart, try if you can edit the spawn in the game. If so, run the long command you posted with your command prompt. If it doesn't work, take a screenshot of your command prompt showing these steps and their outputs.

@KeeveeKoomoo
Copy link
Author

image
Just to make clear that it has given the same output for every prior command too

@ghost
Copy link

ghost commented Jan 29, 2024 via email

@sgkoishi
Copy link
Member

Run /ui your_player_name from the command prompt and check the output.

@KeeveeKoomoo
Copy link
Author

it says user already exists, I have tried that before when owner didn't work, I assume that they are functionally the same group

@KeeveeKoomoo
Copy link
Author

Run /ui your_player_name from the command prompt and check the output.

It just returned my IP address which I obviously won't send as a screenshot

@sgkoishi
Copy link
Member

Set user group (/user group user_name new_group) never outputs user exists. You are probably creating new users (/user add).

/ui will show your user group if you are logged in - and if you didn't see it, you are in the guest group.

@KeeveeKoomoo
Copy link
Author

KeeveeKoomoo commented Jan 29, 2024

I think I may have misunderstood how to use the group command, I have made myself an owner, and now I can edit the spawn area. Still can't use commands ingame but at this point I'm not fussed about that.

@KeeveeKoomoo
Copy link
Author

I think the issue has been solved, my main concern however is boss summoning, and we aren't at a stage in the game where we can summon a boss yet. Could I close the issue and reopen it, or that not how github works?

@sgkoishi
Copy link
Member

Both user group (set group) and user add (create user) require the user to log in.
When you are not logged in, you are still a guest, not an owner (you didn't authenticate as owner by /login).

You can run the long command you posted (via command prompt), or check the list here and manually add whatever you want to guest: group addperm guest permission_you_want

You can use /item or /give to get a boss summoning item (remember to create an alt account in the game to test if everyone can summon it!)

You can close and reopen the issue when you want, and chat official TShock Discord server.

@serverbread-DEV
Copy link

I think he just want to remove all the restrictions added by Tshock

In fact, every server administrator is annoyed by this problem:
They have to type group addperm default e.g.perm command manually.

In my opinion, TShock should disable these restrictions by default,
if anyone want to enable them, just type group delperm default e.g.perm

@sgkoishi
Copy link
Member

In my opinion, TShock should disable these restrictions by default, if anyone want to enable them, just type group delperm default e.g.perm

Here comes the problem: why use TShock instead of vanilla server? After all, you don't actually need the Crossplay plugin to allow mobile players to join (you do need it a few years ago but not now). The whole point of management is to restrict actions, and if you don't want to restrict anything, you are not managing anything.

@serverbread-DEV
Copy link

In my opinion, TShock should disable these restrictions by default, if anyone want to enable them, just type group delperm default e.g.perm

Here comes the problem: why use TShock instead of vanilla server? After all, you don't actually need the Crossplay plugin to allow mobile players to join (you do need it a few years ago but not now). The whole point of management is to restrict actions, and if you don't want to restrict anything, you are not managing anything.

Just for install plugins.

I prefer to provide more vanilla features for players.

The whole point of management is to restrict actions

I dont think so, for example, I can install a plugin which allowed player to break anything they want to break, can we call this restrict actions? Obviously not.

You think I use TShock just for manage player. In fact, I just want to add some plugins so that player can have a better experience.

But this is clearly not enough to justify the need to disable these restrictions by default.lol

So, Why Should We Disable Them By Default?

  • Many server operator is annoyed by this problem
  • A complete noob can hardly know how to fix it, they even didn't know it's permission node caused the problem
  • It can save the time of me and the people like me.
  • Since we don't have SSC enabled by default, why don't we keep them disabled by default? Keep It Simple & Stupid ;)

@sgkoishi
Copy link
Member

More are annoyed that their servers are getting nuked, that's why TShock exists. All the difficulty and time and other costs you face trying to disable the restrictions, also applies to enabling them.

There are plugins like Vanillafier. It might be nice to have it integrated to TShock and show this hint when the server launch (perhaps during /setup too)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants