1. Community
  2. Plugin Support
  3. Auto Doors
Why has the command changed?Solved
Plugin Page
Posted 6 years ago
Last updated 6 years ago
#1
It used to be /ad.

Once again I always like it when people try to takeover plugins. But autodoors is a very much used plugin that has been used on alot of servers for years. And then after years something this big is suddenly changed? Literally everybody is complaining /ad not working blabla.

So why change this? It has been the same command for years. Now you need to explain to all players on all modded rust servers that the command has changed. Why? Something like this should not be allowed unless it is absolutely necesarry and there is no way around of changing the command.

Lately there is a big problem going on with lots of plugins that get updates but these updates do nothing but destroy something that was working fine before or change commands, make config files corrupt and so on. It is a literal nightmare for server owners. Not just talking about this plugin, i'm talking about alot of plugins.

Please can we get some quality control?
Posted 6 years ago
Last updated 6 years ago
#2
I know what you mean, Arainrr shouldn't have changed the default command from ad to autodoor, but...
Posted 6 years ago
Last updated 6 years ago
#3
5df121d013ded.png runescape
I know what you mean, Arainrr shouldn't have changed the default command from ad to autodoor, but...

That is not solving anything though. That will only result in half the servers using the old /ad command and half the servers using the new /autodoor command. Which is even more confusing.

At least keep the original command or make it very clear somewhere that it has changed.

But /ad has been a command on modded rust servers for literal years. It's that I deleted the data file so alot of people had to re-enable it that I found out it wasn't working. Alot more servers owners will face this problem soon once they clean their data files.

The best solution for now would be to allow both commands.

But the most important lesson: DON'T TRY TO FIX WHAT ISN'T BROKEN

for years everybody types /ad.  Why start the confusion? What was wrong with it? Did another plugin need the /ad command?

Posted 6 years ago
Last updated 6 years ago
#4
Goldie

That is not solving anything though. That will only result in half the servers using the old /ad command and half the servers using the new /autodoor command. Which is even more confusing.

At least keep the original command or make it very clear somewhere that it has changed.

But /ad has been a command on modded rust servers for literal years. It's that I deleted the data file so alot of people had to re-enable it that I found out it wasn't working. Alot more servers owners will face this problem soon once they clean their data files.

The best solution for now would be to allow both commands.

But the most important lesson: DON'T TRY TO FIX WHAT ISN'T BROKEN

for years everybody types /ad.  Why start the confusion? What was wrong with it? Did another plugin need the /ad command?

I agree totally, I will not be updating the plugin as the original is working with no problems and see no point in the changes for that reason, It will be the fourth plugin that has unneeded changes made to it where i am still using the original working "recipe" , I suppose that every "chef" needs to add their own "flavour" but there is no point when it spoils the meal.

Posted 6 years ago
Last updated 6 years ago
#5
Updated...
Posted 6 years ago
Last updated 6 years ago
#6
5c18c7da631b5.jpg Arainrr
Updated...

Thanks alot for the quick fix and allowing both commands to work +1

Posted 6 years ago
Last updated 6 years ago
#7
And don't update your plugins without first reading the update notes, always check the config files after updating a plugin.
This is just common sense.
Posted 6 years ago
Last updated 6 years ago
#8
5df121d013ded.png runescape
And don't update your plugins without first reading the update notes, always check the config files after updating a plugin.
This is just common sense.

It said "new command" and not "the command everyone has been using for years won't work anymore".

 But the author has fixed it fast and nicely by allowing both commands to work.

Locked automatically