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

Error in --Plugin line after change first motd msg. #410

Open
KMoDwOne opened this issue Feb 10, 2024 · 4 comments
Open

Error in --Plugin line after change first motd msg. #410

KMoDwOne opened this issue Feb 10, 2024 · 4 comments

Comments

@KMoDwOne
Copy link

KMoDwOne commented Feb 10, 2024

Hi, i hope my Title represents my Issue. Im not sure its an issue with the hosting service fileeditor or with the Plugins .yml itself.

This is what happens:
When opening the .yml and change something in the File. For example the Server Name, only the default Name(Minecraft) is replaced with the new one.
Then if i want to save the File i get an Error Message wich says there is an Error in the File, i want to ignore it and still save the file. After checking the File again it shows an Error in the --Plugins Line, altough i didnt change anything there.

I also tryed to add only one single Letter, but still the same result.
This is my first day on Github and also my very first Server, so my knowledge is a little small atm. :D

Would be super Nice if someone knows what can be the issue here.

Edit:
Ive downloaded the file and edited the same with Notepad++. So i guess its something caused by the Apex Hosting Editor or because i want to change the file inside the Server enviorment.
Is it possible that there is an issue with other Plugins wich make exactly the Plugins Line show the Error?

@stephan-gh
Copy link
Member

The --- !Plugin lines used by SLP are a bit "special" so it is not entirely surprising that some online editors might be confused by it. It seems unlikely that the error you mentioned is caused by an issue with other plugins. In retrospect making the SLP configuration so "special" was not an ideal design choice from myself (although it had some positive sides as well).

I recommend that you edit the configuration with Notepad++ instead as you tried and avoid touching it in the web UI. Sorry for the inconvenience :)

@stephan-gh
Copy link
Member

Or if I understand you correctly you could also just ignore the error in the online editor. It sounds like it is wrongly reported (you might want to report this to your server host since the error is likely on their side).

@KMoDwOne
Copy link
Author

KMoDwOne commented Feb 10, 2024

I tryed it out ignoring the Warning. I saved the file and restarted the server. But there was no change. The part i changed wasnt updated. There was only the 3 default messages.

For sure, i alrdy started a ticket :D

I will try to edit the file with notepadd and then try again. Im not to optimistic but we will see.

@stephan-gh
Copy link
Member

You will need to run the /slp enable command once. If you don't do that, it will not apply any of your changes.

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

2 participants