I think Miwo's comment fits this thread just as well as your previous one:
Quote@Miwojedk#15457 If an Admin is griefing via a feature, then I don't think we should point the blame at said feature.
I think Miwo's comment fits this thread just as well as your previous one:
Quote@Miwojedk#15457 If an Admin is griefing via a feature, then I don't think we should point the blame at said feature.
@wild1145#15452 Does it have any negative consequences if some of our logs are only slightly useful? Is there a specific problem you are thinking of?
@elmon#15456 You're looking for https://discordpy.readthedocs.…discord.Message.reference in discord.py.
@wild1145#15409 I don't see any reason not to log as much as possible. It can only make admins' lives easier.
@wild1145#15389 "feature" is the right term. It's a technical necessity for bending because creative flight prevents you from programmatically pushing the player downwards.
@Fleek#15340 Would that program be running on a schedule? If not, schematics will still be able to contain patched exploits as long as the patch was not in place when the schematic was originally saved or uploaded.
@redeastwood#15348 The fact that we can have a discussion about it is enough evidence for me that others might do the same. In fact, if everyone agreed that it already falls under 1i, this suggestion would not have been created.
The context of the previous suggestion was that we had a master builder who was creating builds depicting bestiality. That is why bestiality is explicitly mentioned in the master builder policy:
https://forum.totalfreedom.me/d/4-master-builder-policy
Quote@Shdwo#15336 object as this should already exist under 1i. in the conduct policy as it is against UK and US law (with minority exceptions)
Bestiality in real life is obviously illegal, but that's not what we deal with on this server. If you do it in Minecraft, it's art, which is much less clear from a legal perspective.
You had a similar suggestion in the past, not about the world system, but about changes that are mainly intended to help servers other than our own. That idea was not very well received:
https://forum.totalfreedom.me/…lexible-for-server-owners
@Folfy_Blue#15283 To be pedantic, a Minecraft username can have 16 characters. Together with the comma and space that need to go between each name at minimum, that's 18 characters, so we can only fit 55 full-length names in the channel topic. It's still not a realistic issue, though.
@videogamesm12#15252 I guess that is always a possibility, although we'll have to reimplement all our exploit patches. There are a few inside TFM itself as well.
@videogamesm12#15198 I believe that runs into this problem:
Quote@Fleek#15125
VulnerabilityPatcher can’t check for WorldEdit, and if it could, it is most likely going to slow down to check each block in large edits.
WorldEdit doesn’t offer any API that we could use.
It seems odd to me that we would treat nicknames in Discord different than nicknames ingame. I would personally like to see shdwo's second suggestion applied to both Discord nicknames and ingame nicknames.
Unbanned.
@wild1145#15169
Relevant threads:
https://totalfreedom.boards.net/thread/66078/jwmphall
https://totalfreedom.boards.ne…147/email-appeal-jwmphall
This ban was added by Seth without a formal request.
1. jwmphall
2 jwmphallbeans#6704
3.2 years ago or something
4. No reason stated before or after ban
5.yes
@Ashaz#15149 It's mainly that you can prepare exploits instead of having to create them on the spot. For example, you can store a crash chest in a schematic to easily grab it. You might also be able to use some exploits that have already been patched, because most patches only check the player, but WorldEdit doesn't go through the player.
The three former executive positions, for reference:
Advertising Manager
Associated Server Liaison
TotalFreedom Evangelist
Interestingly, the modern Server Liaison is the first time we have had an executive position responsible for player retention. I think it makes sense to split it out, though, now that it has become a significant responsibility by itself.
What I see in this thread is an OP who is frustrated because an issue that is important to them has gone unsolved for 8 months. While I agree with Wild that we should not be allocating development resources to a workaround if we can fix the original issue, I also agree with UnderTails that 8 months is a long time, regardless of whether the right people were aware of the issue or had time to work on it.
@wild1145#15134 NBT is stored when you save your build as a schematic.