Posts by taah

    To be honest I get where people are coming from, it would be much more simplistic to just have upvotes and downvotes but why exactly is my ban appeal being used as a reasoning to add it?

    it was unjust as it had only one object and about 8-9 vouches iirc and still got denied

    i think it's stupid how your ban was so long considering you're perfectly knowledgeable in knowing the exploit meaning you know how it works and yet you still didn't commit a harmful use of the exploit, and merely a harmless one. i think you're a trustworthy player compared to many others and might be the most trustworthy on this list of offenders ryan keeps mentioning. i'm sure you could have done something but the point is you didn't and you made a joke with the exploit versus others who have done worse. it's unfair wild1145 calls you our second biggest offender when there exists many who would've actually harmfully used the exploit including many other offenders and we've had worse people attack the network. the point is you're knowledgeable and you didn't use your knowledge to cause any actual harm.

    I've read the article linked in the OP. It seems like Bungeecord actually conflicts with TF's way of doing things for a bumber of reasons.


    I need more time to see how Velocity is being received in general, if it's a solid solution, obvious vouch

    could i get a specific on what it conflicts with please?

    This is in regards to this thread: Development Update - August 1st, 2022


    As we move forward once TFM's final release is dropped, development on the new core has already started and is going by pretty fast.

    Now, I'm not going to explain why Velocity is the better choice because it is listed here --> https://velocitypowered.com/wi…arisons-to-other-proxies/


    NetworkManager IIRC is suitable for Velocity, and since Velocity is maintained by PaperMC's Development Team and we run our backends using a fork of Paper, I believe it'd be better and more suitable for us to also run their proxy software versus md_5's BungeeCord or Paper's Waterfall which is soon to be deprecated and is more recommended to use Velocity over it.


    Velocity also has an API that is up to date with the modern component system versus BungeeCord/Waterfall being out to date and using legacy code that hasn't been updated in years and instead is just being built and updated upon. Velocity doesn't rely on Waterfall or BungeeCord and is its own software that's created more modern as it's much newer (not that new, it's like 2 years old).


    2nd Suggestion: I also request that we begin to use Redis to communicate with backends and frontends. While Velocity does support the Bungee Plugin Messaging Channel, Plugin Messaging in general tends to be buggy and unreliable as you have to send messages through players. Redis supports a publish / subscribe system in which the proxy and backend servers can communicate with each other. Using this, we can also fix the server selector issue as well in the Hub and most likely add other features (global chat, global staff chat, etc.)


    My final suggestion is that we deprecate NetworkManager. I understand that NetworkManager provides a lot of the features to save Ryan from having to be able to do stuff manually and has an epic panel (imo only good thing abt it), it can be unreliable at times. If we do not rid of NetworkManager, I recommend us using LuckPerms for permissions rather than NetworkManager as LuckPerms is more modern and is more commonly used and their support is much more reliable, and it also is an open source plugin. LuckPerms is basically carrying the Minecraft Server community when it comes to permission handling and groups.


    With the new TF-Core being made, we're able to add another module to the repository which can handle a new proxy core. Before you say we're unreliable or will be slow on updates, no, because the only reason TFM was hardly worked on is because the code dates back to many years earlier and has a lot of legacy methods and ways, as well as a legacy codebase that is away from modern times. It's really difficult to work with sometimes but since this new core and new code is much more modernized it will be easy to make changes and updates and fix bugs, as is done with Scissors.