Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 17, 2018 23:36:33 GMT
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. 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. I suggest to temporarily remove EssentialsX from this server, until the above can be voided; through development, and a state of further 'readiness' for application on the server. This suggestion was drafted in response to this thread, and is a rebuttal of the correlative suggestion. - The initial suggestion, which aimed to implement EssentialsX, was accepted; even though the suggestion received two objects, and three vouches. The amount of input sustained on this suggestion was measly; and ultimately, the proportion [of acceptance and denial] was slim.
- EssentialsX has presented multiple functional problems, and has been documented to introduce several redundancies; in terms of repository commits, and changes to the functionality of in-game commands.
- From the beginning, several valid reasons to postpone the implementation of this plugin were present; although, even with notable problems coupling this fork, it was brought to the production server.
A multitude of changes made in EssentialsX were never voted upon (no suggestion was made outlining the changes), and went unannounced. I believe that this warrants current removal. |
|
Wild1145
Club 4000 Member
Inactive Player & Inactive Senior Admin
Posts: 10,414
| Likes: 9,680
|
Post by Wild1145 on Jun 18, 2018 1:06:24 GMT
Agreed.
|
|
super
Veteran Member
Among Us
Posts: 1,282
|
Post by super on Jun 18, 2018 3:12:17 GMT
I agree
|
|
Panther
Veteran Member
Posts: 721
| Likes: 604
|
Post by Panther on Jun 18, 2018 3:16:18 GMT
I too agree
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 18, 2018 4:02:18 GMT
A multitude of changes made in EssentialsX were never voted upon (no suggestion was made outlining the changes), and went unannounced. I believe that this warrants current removal. All of the changes were communicated in the thread you linked: * Sending players to spawn has been restricted to admins
* Warping players has been restricted to admins
* Nicknaming other players has been restricted
* Clearing other players inventories has been restricted to admins and console
* Mass messaging can only be done by seniors
* Super Admins and up may only see IPs in /seen
* Let TotalFreedomMod handle when the server is full
* Block regular players from going into others /echest
* Admins and console can use /give, and for non-players it would just be an alias for /i.
-- improvements from before this thread was edited for the first time --
* Removes /unban, /unbanip, /ignore, and /createkit
* Adds /kittycannon back
-- improvements from before this thread was edited for the second time --
* Admins can now heal other players
* Admins can now change other players nicknames
* Senior admins can AFK other players
* Command /ping has been restricted, so you can no longer create custom messages with it. This is useful for preventing framing admins
* EssentialsX now has a fallback, so if a command wasn't modified for use on TotalFreedom, it will attempt to restrict the full usage of the command to super admins only
* EssentialsX will now have the correct versioning on the server and on GitHub - VideoGameSmash12 If you didn't like any of the changes, you should have said so. All programmes have room for improvement. I'd like to know what changes were undocumented, and what functional problems it has introduced. I've been trying to find a solution so that the release page does not have to be updated as frequently, but this does not relate to any server functionality. |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 18, 2018 4:12:38 GMT
A multitude of changes made in EssentialsX were never voted upon (no suggestion was made outlining the changes), and went unannounced. I believe that this warrants current removal. All of the changes were communicated in the thread you linked: <snip> If you didn't like any of the changes, you should have said so. All programmes have room for improvement. I'd like to know what changes were undocumented, and what functional problems it has introduced. I've been trying to find a solution so that the release page does not have to be updated as frequently, but this does not relate to any server functionality. The clearing of peer inventories is, and has been, a useful feature for operators; in the sense that their alternates can be cleared of 'crash items.' Significant privacy amendment, which was never voted upon. Significant freedom amendment. A command with a genuine usage, which was needlessly modified. As for functional problems; the layout for administrator social-spy has been changed, which presents unprecedented clutter for administrators -- your plugin has introduced several redundancies, many of which you acknowledged on your 'test server' -- and, as demonstrated above, you have docked functionality. The suggestion stands, and it's clear that there's a valid initiative to revoke the plugin; until it's production-ready, and the aforementioned issue(s) have been concisely solved. That's what we are doing here; this suggestion is to, in present time, remove the plugin's in-game presence until a proper analysis [and conclusion to the numerous changes, which were made despite the lack of any corresponding suggestion to proceed with them] can be done. |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 18, 2018 4:22:25 GMT
As for functional problems; the layout for administrator social-spy has been changed, which presents unprecedented clutter for administrators -- your plugin has introduced several redundancies, many of which you acknowledged on your 'test server' -- and, as demonstrated above, you have docked functionality. Significant privacy amendment, which was never voted upon. /echest is supposed to be blocked in TFM You still fail to list changes that were not mentioned. |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 18, 2018 4:25:23 GMT
As for functional problems; the layout for administrator social-spy has been changed, which presents unprecedented clutter for administrators -- your plugin has introduced several redundancies, many of which you acknowledged on your 'test server' -- and, as demonstrated above, you have docked functionality. Significant privacy amendment, which was never voted upon. /echest is supposed to be blocked in TFM You still fail to list changes that were not mentioned. I did -- read my post again. Nevertheless, I maintain my stance; and the suggestion will stand. |
|
Lemon
Veteran Member
Insert status here.
Posts: 2,491
| Likes: 2,165
|
Post by Lemon on Jun 18, 2018 8:55:25 GMT
* Admins and console can use /give, and for non-players it would just be an alias for /i.
Significant freedom amendment.
Not a freedom amendment, both serve the same function but /give allows giving items to other players. |
|
StevenNL2000
Forum Admin 
Posts: 6,415
| Likes: 6,936
IGN: StevenNL2000
Timezone: UTC+01:00
Member is Staff. Need immediate assistance? Send a PM
|
Post by StevenNL2000 on Jun 18, 2018 11:51:04 GMT
Not to say "I told you so", but we already had this exact discussion before it was implemented (see the original suggestion). I didn't keep insisting on a full code review because I like giving you work: there are bound to be at least 20 more undocumented changes like the new /socialspy format irix mentions.
|
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 18, 2018 16:54:50 GMT
* Admins and console can use /give, and for non-players it would just be an alias for /i. Significant freedom amendment. Not a freedom amendment, both serve the same function but /give allows giving items to other players. In effect, the blockage of a command with which one [typically] may bestow activity unto others -- whether negative, or positive -- is a significant amendment to the 'freedom' element encapsulating this server; and when coming to terms with that, it seems clear to me that no general consensus was developed [between the administrators and those who have contributed to this plugin] regarding the propriety of such a modification. Secondly, the 'identity' element when it comes to figuring any profound negativity in a command, sensibly, should be coupled with any [and all] pertinent aspects of free-usage. Several other changes, which have conformed to the fallacious -- but within this plugin's developmental process, inherent -- lack of reasoning, were put into effect once this fork was added. |
|
blackedout
Veteran Member
Posts: 2,884
| Likes: 1,405
|
Post by blackedout on Jun 18, 2018 16:59:03 GMT
All of the changes were communicated in the thread you linked: <snip> If you didn't like any of the changes, you should have said so. All programmes have room for improvement. I'd like to know what changes were undocumented, and what functional problems it has introduced. I've been trying to find a solution so that the release page does not have to be updated as frequently, but this does not relate to any server functionality. The clearing of peer inventories is, and has been, a useful feature for operators; in the sense that their alternates can be cleared of 'crash items.' Significant privacy amendment, which was never voted upon. Significant freedom amendment. A command with a genuine usage, which was needlessly modified. As for functional problems; the layout for administrator social-spy has been changed, which presents unprecedented clutter for administrators -- your plugin has introduced several redundancies, many of which you acknowledged on your 'test server' -- and, as demonstrated above, you have docked functionality. The suggestion stands, and it's clear that there's a valid initiative to revoke the plugin; until it's production-ready, and the aforementioned issue(s) have been concisely solved. That's what we are doing here; this suggestion is to, in present time, remove the plugin's in-game presence until a proper analysis [and conclusion to the numerous changes, which were made despite the lack of any corresponding suggestion to proceed with them] can be done. 1. Most of the time people just clear other people's inventories to be annoying or to troll. 2. People may not want other players stealing their stuff from their enderchest. 3. For /give, people would just use it to put items into other player's inventories to troll. /i doesn't allow you to do that, but it provides the same functionality. |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 18, 2018 17:03:38 GMT
The clearing of peer inventories is, and has been, a useful feature for operators; in the sense that their alternates can be cleared of 'crash items.' Significant privacy amendment, which was never voted upon. Significant freedom amendment. A command with a genuine usage, which was needlessly modified. As for functional problems; the layout for administrator social-spy has been changed, which presents unprecedented clutter for administrators -- your plugin has introduced several redundancies, many of which you acknowledged on your 'test server' -- and, as demonstrated above, you have docked functionality. The suggestion stands, and it's clear that there's a valid initiative to revoke the plugin; until it's production-ready, and the aforementioned issue(s) have been concisely solved. That's what we are doing here; this suggestion is to, in present time, remove the plugin's in-game presence until a proper analysis [and conclusion to the numerous changes, which were made despite the lack of any corresponding suggestion to proceed with them] can be done. 1. Most of the time people just clear other people's inventories to be annoying or to troll. 2. People may not want other players stealing their stuff from their enderchest. 3. For /give, people would just use it to put items into other player's inventories to troll. /i doesn't allow you to do that, but it provides the same functionality. The majority of these statements are entirely unsubstantiated, and were formed entirely upon a basis of subjective reasoning; which was derived from identity, but carried nil fact that what you said just happened to be factual. While the 'what if' inquiries are certainly valid when surfacing a change to the method in which commands are treated, they do not warrant their removal; and following that twisted logic, it would be equally sensible to block the entirety of WorldEdit -- in the event that 'people may use it to grief.' |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Jun 18, 2018 18:19:16 GMT
Actually the way /ci is written is that it will not clear your armor slot (i.e. where the death boot would actually be). /smite on the other hand removes everything from a players inventory. So, asking an administrator to smite you would warrant 100% success rate. So your argument of /ci'ing via an alt account is invalid. Using /ci does not clear a players armor
|
|
Lemon
Veteran Member
Insert status here.
Posts: 2,491
| Likes: 2,165
|
Post by Lemon on Jun 22, 2018 6:39:30 GMT
I've reverted till all the code changes are reviewed.
|
|
