???Daniel
Veteran Member
Thanks for the epic time I had years ago.
Posts: 821
| Likes: 208
|
Post by ???Daniel on Jun 17, 2018 7:23:26 GMT
Hi. /echo is a copy of the command /ping in essentials. It normally displays the message that you give afterwards, but now it just says "Pong". Is it possible to change this back?
|
|
Video
Forum Admin 
An op's rights activist
Posts: 5,585
| Likes: 5,893
IGN: VideoGameSmash12, videogamesm12
Old IGN: https://namemc.com/profile/VideoGameSmash12.2, https://namemc.com/profile/videogamesm12.1
Discord: Video#9801
Birthdate (MM/DD): 07/16
Timezone: UTC-07:00
Member is Staff. Need immediate assistance? Send a PM
|
Post by Video on Jun 17, 2018 7:29:38 GMT
it was modified to be that way on purpose
maybe you should actually administrate instead of using /echo to do silly shit
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 17, 2018 7:30:16 GMT
I on purposely removed the functionality of ping. I blocked it to prevent wildcard gcmd ? eping spam. This also makes framing logs harder. However, the functionality of /ping was an easter egg, and not its intentional use. You can use the regular /ping to check your TPS. So no, "/echo is not broken"
|
|
rylie.
Veteran Member
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Posts: 3,932
| Likes: 5,664
IGN: breedingslave/breedme
Old IGN: Typhlosion147
Discord: Xeoda#2839
Birthdate (MM/DD): 04/26
Timezone: UTC-05:00
|
Post by rylie. on Jun 17, 2018 14:51:56 GMT
However, the functionality of /ping was an easter egg, and not its intentional use. It was an easter egg? I actually use it intentionally, a lot, when seeing if the server is responding or not, since it just returns "Pong!" without actually doing anything else. |
|
Wild1145
Club 4000 Member
Inactive Player & Inactive Senior Admin
Posts: 10,414
| Likes: 9,680
|
Post by Wild1145 on Jun 17, 2018 15:00:58 GMT
It is actually intended functionality... Instead of removing perfectly valid functionality perhaps work on adding new useful stuff?  |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 17, 2018 15:12:14 GMT
However, the functionality of /ping was an easter egg, and not its intentional use. It was an easter egg? I actually use it intentionally, a lot, when seeing if the server is responding or not, since it just returns "Pong!" without actually doing anything else. I said that wrong sorry: being able to echo your own messages is NOT the way the command was supposed to be used |
|
rylie.
Veteran Member
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Posts: 3,932
| Likes: 5,664
IGN: breedingslave/breedme
Old IGN: Typhlosion147
Discord: Xeoda#2839
Birthdate (MM/DD): 04/26
Timezone: UTC-05:00
|
Post by rylie. on Jun 17, 2018 15:14:15 GMT
It was an easter egg? I actually use it intentionally, a lot, when seeing if the server is responding or not, since it just returns "Pong!" without actually doing anything else. I said that wrong sorry: being able to echo your own messages is NOT the way the command was supposed to be used Yeah, I figured that was said incorrectly /shrug |
|
Wild1145
Club 4000 Member
Inactive Player & Inactive Senior Admin
Posts: 10,414
| Likes: 9,680
|
Post by Wild1145 on Jun 17, 2018 17:10:40 GMT
It was an easter egg? I actually use it intentionally, a lot, when seeing if the server is responding or not, since it just returns "Pong!" without actually doing anything else. I said that wrong sorry: being able to echo your own messages is NOT the way the command was supposed to be used It absolutely is... |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 17, 2018 17:31:30 GMT
I said that wrong sorry: being able to echo your own messages is NOT the way the command was supposed to be used It absolutely is... No in the code they even say it's an Easter egg. Regardless I don't see it serving any purpose except for buffoonery |
|
Wild1145
Club 4000 Member
Inactive Player & Inactive Senior Admin
Posts: 10,414
| Likes: 9,680
|
Post by Wild1145 on Jun 17, 2018 17:40:10 GMT
No in the code they even say it's an Easter egg. Regardless I don't see it serving any purpose except for buffoonery Then you're exceptionally short sighted. It serves as an excellent debugging tool if a server is lagging for an extended period of time. For example you would use "/ping <timestamp>" and could then work out when things broke. Again, I stand by my original point. Don't waste valuable dev effort removing functionality that serves a purpose when there are hundreds of better things to be doing... |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 17, 2018 18:12:19 GMT
EssentialsX [and its corresponding changes to the plugin] looked like a bad idea to me from the beginning; and the multitude of slight, but detrimental changes (unregulated) made to Essentials are seemingly lacking.
If given a choice, I would vouch for the removal of this fork; as its implementation, from beginning to now, has consisted of nothing but issues.
|
|
Lemon
Veteran Member
Insert status here.
Posts: 2,491
| Likes: 2,165
|
Post by Lemon on Jun 17, 2018 19:41:39 GMT
EssentialsX [and its corresponding changes to the plugin] looked like a bad idea to me from the beginning; and the multitude of slight, but detrimental changes (unregulated) made to Essentials are seemingly lacking. If given a choice, I would vouch for the removal of this fork; as its implementation, from beginning to now, has consisted of nothing but issues. When I added it, I told all issues had to be reported to me. Issues can be fixed, and changing from a 4 year old plugin to a new one will consist of a lot of them. They'll have to be ironed out. |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 17, 2018 21:05:25 GMT
EssentialsX [and its corresponding changes to the plugin] looked like a bad idea to me from the beginning; and the multitude of slight, but detrimental changes (unregulated) made to Essentials are seemingly lacking. If given a choice, I would vouch for the removal of this fork; as its implementation, from beginning to now, has consisted of nothing but issues. Essentials [and its lack of support] will make updating for 1.13 really hard. Instead of having to rewrite many of the code. The way Essentials works with items.csv in 1.13 will not work, because Mojang is dropping data values. Instead of having to waste development resources on that, all I have to do is git pull www.github.com/EssentialsX/Essentials.git 2.x If you want to go ahead and rewrite that for 1.13, and get it reverted, be my guest. If you think that any plugin is not going to have issues with the nature of how TotalFreedomMod is written, boy do I have news for you. Better to get the issues sorted out now, before it's too late. All of the issues reported have been minor bugs that do not break the servers functionality (except for TotalFreedomMod not blocking /time's aliases). |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 17, 2018 21:41:27 GMT
EssentialsX [and its corresponding changes to the plugin] looked like a bad idea to me from the beginning; and the multitude of slight, but detrimental changes (unregulated) made to Essentials are seemingly lacking. If given a choice, I would vouch for the removal of this fork; as its implementation, from beginning to now, has consisted of nothing but issues. When I added it, I told all issues had to be reported to me. Issues can be fixed, and changing from a 4 year old plugin to a new one will consist of a lot of them. They'll have to be ironed out. I have no objection to introducing the plugin, once it is compatible with a production environment; but nevertheless, it is profound to me that the plugin [EssentialsX] needs another round of 'the development process' before it is introduced to this server. We should all keep in mind that TotalFreedom is not a free-for-all repository, which plugins may be tested on; rather, we should effectively (and concisely) implement changes to the server. EssentialsX [and its corresponding changes to the plugin] looked like a bad idea to me from the beginning; and the multitude of slight, but detrimental changes (unregulated) made to Essentials are seemingly lacking. If given a choice, I would vouch for the removal of this fork; as its implementation, from beginning to now, has consisted of nothing but issues. Essentials [and its lack of support] will make updating for 1.13 really hard. Instead of having to rewrite many of the code. The way Essentials works with items.csv in 1.13 will not work, because Mojang is dropping data values. Instead of having to waste development resources on that, all I have to do is git pull www.github.com/EssentialsX/Essentials.git 2.x If you want to go ahead and rewrite that for 1.13, and get it reverted, be my guest. If you think that any plugin is not going to have issues with the nature of how TotalFreedomMod is written, boy do I have news for you. Better to get the issues sorted out now, before it's too late. All of the issues reported have been minor bugs that do not break the servers functionality (except for TotalFreedomMod not blocking /time's aliases). I'm fairly certain that we are not running 1.13, thus I don't see your point. As for the 'doomsday' proposition, I am still at loss for a valid reason as to why a developmentally incomplete (with significant problems, and ill-advised changes to barebone Essentials) belongs in-game. Once more, that is no excuse for keeping the plugin. Until EssentialsX becomes suitable [stable; and at a glance, free of bugs] for production; you should hold off, and continue with your progress [if any] towards that goal. |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 17, 2018 23:25:27 GMT
Once more, that is no excuse for keeping the plugin. Until EssentialsX becomes suitable [stable; and at a glance, free of bugs] for production; you should hold off, and continue with your progress [if any] towards that goal. Nothing will ever be free of bugs. but nevertheless, it is profound to me that the plugin [EssentialsX] needs another round of 'the development process' before it is introduced to this server. It does not. All of the major changes were made and tested before it went on the server. Software gets bug fixes. I'm fairy certain that we are not running 1.13, thus I don't see your point. We certainly will be running 1.13 in the future We should all keep in mind that TotalFreedom is not a free-for-all repository, which plugins may be tested on; rather, we should effectively (and concisely) implement changes to the server. Ever heard of test servers? Maybe not, as you offer to make a forum for my server for testing. you should hold off, and continue with your progress [if any] towards that goal. I have been very responsive to pushing out appropriate patches for the issues raised. |
|
[/spoler]
