Posts by Noah_Dekka

The Aternos forums are now deprecated

Learn more about this change here.

For help regarding Aternos, we recommend you to visit our support center.

    Fabric and forge mods work differently. And it's not like just because the forge version works, the fabric version would work exactly the same and just as well and vice versa.


    There's no punishment. It's simply making sure the mod is compatible and meets our requirements.

    Except. . . this wouldn't apply if it was kept on the same page. The system doesn't judge "new versions", it judges "new mods". Even if the first build of that port of the mod didn't work, if the port was on the same page, it would still automatically be approved because that's how the system works. After one version gets approved from a page, they all get approved.

    What I am trying to point out is that it's an arbitrary double-standard between if a port is on it's own page. . . . or if it's not. Punishment doesn't mean it's intentional, it means if you do it the wrong way, something negative happens as a result. It's still punishing, even if it is unintentionally so since there is a way to avoid it.

    To reverse what I am saying, the system rewards developers who keep both versions on the same page.

    As I explained already, the actual cause for this is that CF did not have a proper implementation for multiple mod loaders for a long time.

    CF is currently reworking that whole Fabric/Forge hell on their site, let's hope that their new solution solves this in an adequate way.

    This is blame shifting.

    Quote

    99% of users would not understand this. They don't even now the difference between Forge and Fabric.

    And this is a staw man's argument. And a non-sensical one at that. By this logic, no one should know how mods work. . . yet still figure out how to 1.) run a server with them and 2.) Pick the SOFTWARE option that LITERALLY SAYS FORGE or FABRIC in order to get the mods working in the first place.

    Listen, if you don't want to accommodate for a fault of the developers not putting it on the same page, fine, but don't put that on us. Don't give a false excuse that we are too stupid to figure out how to use mods. That's not how this works. This train of logic defies common sense of basic knowledge you need to even get to that point in the first place. Maybe attach it to a forum/survey with a drop-down list where you have to fill things out like you are telling us to do here.

    All I am saying is that what you are asking us to do here with "Nevertheless, feel free to report such cases here in the forum and we will add them then." remark. . . . that much should be built into the suggestion system itself, even if it's just a re-direct link to the forums with a brief line explaining this, cause as it stands now, I didn't even know I was supposed to go to the forums when a "suggest mod" event fails in the first place. Having a "If you still wish to pursue this, please head to [FORUM LINK] and suggest it there. I even clicked on the (?) that is supposed to explain how the system works and it mentioned nothing about how users should come to the forums.

    I guess what I am asking for is a way to make it known and then standardize it as to what we are supposed to do for stuff like this. Sure, it's mentioned here in a reply, but at minimum, it really should state such here:

    https://support.aternos.org/hc/en-us/articles/360052255311

    I just find that there's alot of hoop jumping and red tape you are setting up for us to have gotten to this point. This kind of issue is going to keep popping up for other users if the system isn't updated to provide proper instructions as ports are a very common thing.

    Never the less, thank you for atleast somewhat reading the issue and then causally disregarding it there-after.

    All versions of a mod-page are listed if it's uploaded to that page. The only time it's not is if the mod has multiple curseforge pages. An example of when it's not is when it has a fabric page and a separate page for the forge version. . . and yes. . . THAT MUCH is something they DO need to fix.

    Arbitrary example:

    I don't mind the amount of ads, the only thing I mind is the ads that I have to click "X" on because they scroll as you scroll and are actually blocking what you need to click on. All ads should be locked to the page off to the side. They shouldn't ever be overlapping something you need to click on (and yes, I mean "ever"). They shouldn't ever impede you on managing your server. "Background ads" are fine, "pop-up ads" are not. If there was still the same amount of ads, but they were all background ads that I can scroll past, it would be fine.

    What I mean is there are mods that are already approved for say forge. . . then that same creator makes a fabric port but it doesn't get approved. . . enough though it's the EXACT same mod but just more compatible???


    Popularity shouldn't matter for ports of a mod by the same creator where the original mod was already popular and approved.


    An example I found was:

    https://www.curseforge.com/minecraft/mc-mods/bountiful

    vs

    https://www.curseforge.com/minecraft/mc-mods/bountiful-fabric


    BOTH are made by the same guy, only difference is one is a newer version.

    I get the staff of this site doesn't want to risk it with new untested stuff. . . But creators like this ALREADY proven to you that they know what they are doing with the mod that you already approved for another instance. The "suggestion" system needs to be updated to account for "official ports".



    Here is the MAIN issue:

    If they upload this file to the SAME mod page as the forge version, but still be a fabric version. . . it would already be approved because it's the same mod.


    As it stands now, this system only serves to punish mod developers for giving their mod separate pages for forge vs fabric loaders. This needs to be addressed.


    Solution:

    When a mod fails to verify, give users the a second option of "Is this mod an official port of another mod? if so, link the original mod here:" where it checks to see if the owners match up between the original mod and the port and then it gets sent in for review by a human, not an automated system. Either that, or allow mod developers to connect their mod account (curseforge or alternative) to their aternos account so that they can manage ports of already approved mods themselves and thus do the work for you of saying "it's the same mod".


    Please stop punishing mod developers for making a separate page for their fabric/forge versions. You are only forcing a loophole of them uploading both to the same page by doing this and this forced loophole doesn't help you, the mod developers, your curation system, the users here. . . it unfortunately only serves to get in it's own way.

    It's not a new mod, it's a new version of the same mod. If it was on the same page, it would already would allow any new versions after the first version of a mod is approved. It shouldn't be any different just because it's on a new page. This is an issue with your mod suggestion system that needs to be fixed.