Posts by UnderTails

  • The Case for Block Gravity

    Quote

    @wild1145#17986 I won't sacrifice the stability and performance of the server over this.

    i don’t know what exactly you’re referring to, if you think that like a week ago the server was drastically less stable, i personally have experienced 0 change


    The bug you are referring to was something we’ve had for over a year, and it’s never been a major cause of problems, to the point it’s not really a bug anymore, that was just something we liked having.


    If it was causing rampant stability issues, frequent crashes and other issues someone by now would have noticed and made a suggestion to disable gravel. This has never happened.


    Tbh the fact you only found out that gravel has been enabled for a full year this evening proves my point. But i’m willing to hear your opinion.


    With what video said above I personally have no problems with gravity being disabled by default, but it should absolutely be toggleable by admin commands, if you disagree and think it should be completely hard coded, no exceptions ever I’m curious to hear why.


    I don’t want to get in another jousting match with you so why don’t we just let the community express what they think of this first.

  • The Case for Block Gravity

    @videogamesm12#17983 it was changed recently to no longer work, and is always off now.


    I am perfectly happy with it being the way it was where an admin had to to toggle it, i would prefer the way it was before before though.

  • The Case for Block Gravity

    @wild1145#17952


    3 options because I feel like you wouldn’t be happy with option #3

    1. We have it the way it was a couple weeks ago, gravity always enabled, those certain blocks disabled, and gravel enabled

    2. The one you did which i am upset about, where you disable it all together, but reenable those certain blocks

    3. We make a compromise and make gravity automatically disabled, but ops can ask admins to enable it when they want to use it to build (all blocks enabled)

  • The Case for Block Gravity

    Over the past few weeks a very large change in the server has happened, and it has affected some people while others have been completely unaware.


    Block Gravity has been disabled.


    This is one of the biggest problems we’ve had since coreprotect, and it is a complete mistake in my view, and is harming the way many people build.


    Let me explain why we can not disable block gravity.


    For over a year now gravity has been enabled on TF, and it has had relatively 0 consequences.


    I don’t recall a single crash in the past year, or a single lag machine I’ve seen that used Block Gravity to lag the server. I’m sure there have been atleast a few incidents, but they have been extreme rarities and have not at all been a major cause of crashes.


    Why we need it to be enabled


    Gravel has been enabled, and the whole player base has been aware of this, and it shocked me to hear that Ryan didn’t know. He told me gravel being enabled was a “bug” and I say thank god for that bug for terraforming everything i’ve ever built on TF.


    Gravel has been enabled for a year, and it has almost never caused any issues, and it has been a beneficial tool for terraforming.


    I have used this on a daily basis all of last year and this year, and have used it to make mountains, plateaus, landscapes, valleys.


    The method I have used has been making a brush with //sphere 5 or 6 and making piles of gravel, the gravity that affects the block makes it fall in a natural looking way, and afterwards i turn it all to grass blocks, and then turn the dirt that formed under the grass to stone.


    This has given me some incredible looking landscapes and incredible plateaus for builds to be placed on.


    It would be remarkably devastating for me, and for many other builders who use this method of terraforming, to lose such a great great tool that is block gravity.


    The benefits have been very worth it, and the consequences are near none.


    I am currently putting a map I am working on for the ECM on hold, because I’m unable to terraform the land for it, and I don’t know how I am going to be able to complete it. I will resume work building once I have access to terraforming tools.


    Here are some options we could choose from on solutions to the block gravity debate.


    What are our options


    Option 1. The way it’s been


    Option 1 is going back to the way it’s been for the past year which is block gravity has been enabled, and so has gravel, builders are able to utilise gravel, and crashes from it are relatively rare.


    Ryan has said that gravel being enabled is a bug, but to me and builders who’ve always used it it’s a bug we cannot stand to lose.


    With this option gravel will remain enabled.


    Option 2. The way it’s been made


    Currently with option 2 it is that block gravity has been disabled, and builders like myself who have used it for a year in order to build practically everything, are cut off from it, and terraforming is made near impossible on a large scale.


    While some argue that this is in order to enable gravity affected blocks such as sand, concrete powder, and others, it is a trade off which in my opinion is absolutely not worth it.


    And enabling those blocks in my opinion would not even cause much of a problem with block gravity being the way it is.


    Which leads me to option 3.


    Option 3. We do an experiment.


    I suggest we enable block gravity like how it has been enabled, and along it enable all gravity affected blocks. We test it for a week or a month, or however long is necessary to see if the server is in shambles from lag, and crashes.


    If it isn’t going terribly wrong in that amount of time, we can conclude that the problem this whole ideal is based off of may not have existed in the first place.


    If these ideas seems problematic to you why don’t we go to option 4.


    Option 4. A Compromise


    If the risk in having gravity affected blocks is true, which I highly doubt, we should make it the way it was a couple days ago, where block gravity is toggled off by default, but can be toggled on by a command done by an admin.


    This option will allow builders to use gravity when they need it, and for the admins not deal with these supposed issues when it isn’t in use.


    I do not think there is any issue with having it that way, with a compromise.


    and I’m curious to hear the community’s views on it.


    Griefing


    One common issue that has been brought up is griefing with block gravity.


    Overall I would say that this is a rarity. It isn’t common that people grief things with falling blocks, but in the isolated incidents when it does happen, here is what can be done.


    An admin can fly above the place the gravel or the gravity affect block has fallen, and use /ins to find who did it.


    Falling blocks do not create untraceable griefs, they just need to be traced above the spot it’s fallen at.


    If the gravel has made a giant mess and is not able to be rolled back, an admin or the builder can use //replace gravel with air to fix it.


    I would also like to point out that there are other ways to make hard to trace, or hard to fix griefs.


    Such as flying machines.


    As an off topic I need to point out we don’t straight up ban redstone because it could theoretically be used to cause griefs, and I ask we apply that same logic to block gravity, and deal with the incidents that do happen, instead of banning of the method of griefing all together.


    This problem would also be nearly impossible to exist with option 4.


    Conclusion


    I once again must state that losing gravity is an absolute devastating blow to me and to the building community as a whole, and is not worth it for a couple new block choices.


    This is one of the most passionate posts I have ever made, and I make this for the sake of all builders on the server, and for the future of terraforming.


    I urge you all to read all of my points before you give your opinion, and you take this as seriously as it needs to be, because the wrong decision for this will and has already had major consequences for the builders who relied on gravity.


    The importance of this cannot be understated.


    Thank you

  • Admin Application - Folfy_Blue

    neutral


    you are a very active op, but i personally haven’t observed that many qualities of an admin in you, and as said above you do seem to stir up drama occasionally.


    i’ll make a decision later i’m on the fence for this one

  • Add player vaults

    Vouch


    I have been using my /echest for this for the past year and it’s getting pretty cluttered,


    and no
    @Fleek#17806, @videogamesm12#17776 i don’t want to clutter my saved toolbars for stuff i only want on TF

  • Stop disabling vanilla features ever again

    I’m tired of having simple issues on here and the solution being to disable an entire vanilla feature.


    It happened with spawn eggs, books, block gravity, Literally dropping items.


    We have gone too long in my opinion with so many things disabled, and we have to face the fact that it makes our server a below average experience, and is a main factor in turning away new players.


    If i was a new player and i heard that dropping items was disabled, i would be like "wtf is this autocracy i’m outta here" and i would leave and never come back.


    We need to work to enable all the things we have disabled, and not treat banning simple minecraft actions as a permenant solution to isolated problems.


    What we should do is treat the issues like why we can’t enable dropping items, spawn eggs, and other things as bugs we need to fix, instead of actions we need to block. And if it is absolutely necessary to block these things it should be a temporary thing, and the devs should be working to reenable them with real fixes.


    We should in my opinion not ever again disable vanilla features to fix problems, and work to reenable the ones we currently have blocked.