Posts by StevenNL2000

This ban should have expired already, but didn't due to a bug in the ban system (FS-147). You have been unbanned.

To determine whether it should be -ci or -noclear, I think it makes the most sense to look at which of the two scenarios is more common. There are not that many offenses where the player keeping their inventory after a smite is really unacceptable, so -ci would probably lead to the least amount of extra typing.

Unbanned.

Your ban message being wrong is my mistake, I accidentally lumped you in with some other players who did use the items to crash the server. You were intended to be added to the list for distributing crash items. I have corrected your ban message to reflect that.

@Fleek#12033 I was more thinking along the lines of hardcoded behavior. The fact remains that it must be a plugin blocking this because it is a vanilla feature.

Is the agent we are using still the one from this repository from 2016?
https://github.com/AtlasMediaGroup/JAgent

Quote

@xfilez#12043 1) all the stickied threads at the top of this forum are really annoying. You have to scroll down a fair bit to get to any new discussion.

It would be preferable to have sticky threads per section like on ProBoards, but that is yet another thing that requires a third-party plugin on Flarum.

Vouch. It sounds like this is an item on the long list of "exploitable features that were blocked instead of properly fixed". I believe we need to make a reasonable attempt to get rid of all of these.

The fact that setting your spawn point is a vanilla feature might mean that this is actually a bug rather than a feature, unless there was some kind of exploit that a developer "fixed" by blocking this.

I want to warn you of looking at 2b2t too closely. Our server should always bring something unique to the table. 2b2t itself is always going to be a better 2b2t than any attempt at cloning it.

@Madea#11897 My main point is that even given the exact phrasing that was used in the thread, I would say there was still a fairly high chance of an image like this being posted:

Quote

!

This is an unfortunate consequence of the way Spam and Drama is used by most people. Of course there can be serious posts in the section, but they are relatively rare.

@Madea#11891 Outlandish claims are made in Spam and Drama all the time. It is very difficult to tell whether a post in that section is serious or not.

The bug (FS-76) has been assigned to Paldiu, but it doesn't look like he has made significant progress on it yet.

Quote

@neo#11789 oft we still dont know who the fuck lea is

Lea is former admin IamzLuck.

TotalFreedom has been online since 11 November 2010. Mark has previously posted proof of this in the form of an invoice, but the image is no longer available.

Also, on the topic of things we can flaunt in advertising, please make use of the fact that we have been featured in The New York Times. This is neither the first nor the fifth time that I've mentioned this.

@Telesphoreo#11468 The only solutions I've been able to find are some rather interesting ones. Try running First Aid on the partition multiple times. There is apparently a known bug where the application will suddenly be able fix the problem after seemingly doing nothing the first few times. Another thing you can try that solved a similar issue for someone is adding a new APFS volume to the drive from Disk Utility.

If the problem turns out to be with the partition table, you will only find it by checking the disk rather than the partition, as Ryan suggests. You might also try reading the S.M.A.R.T. status of the disk (not the partition) to check if it is in good shape physically.

I've updated your post in the original thread: https://forum.totalfreedom.me/…ndragroseheart-ban-appeal. I am going to lock this one.

@shrimp#11349 As Video says, the first order of business is to get all important data onto another drive. After that, you can technically still use this drive, but weird errors like this one are going to become more and more frequent.

@shrimp#11343 That looks like a hard drive that is starting to fail. It's over 4.5 years old now, most hard drives do die around that age.