Jump to content

BungeeCord login bug - Forge 11.14.0.1239 - MC 1.8 - OS X 10.10.1 - Java 8u25


Jofkos

Recommended Posts

When i log in into a BungeeCord Proxy, it get kicked with this message:

kyzHpjR.png

Now you'll think it's a BungeeCord bug. I though that too, but i can still connect running a "clean" Minecraft 1.8, so it can't be a BungeeCord bug.

I've not installed any mods and i researched about this bug, but i found nothing about this bug running MC 1.8

Here is my fml-client-latest.log

Here a screen of my Forge/Mc Version:

Fg3gr0L.png

 

Link to comment
Share on other sites

It is a bungeecord bug.

We use the same field to identify ourselves as they do to forward ip information.

They need to update to support both. {We nativly do because well its simple -.-}

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Link to comment
Share on other sites

It is a bungeecord bug.

We use the same field to identify ourselves as they do to forward ip information.

They need to update to support both. {We nativly do because well its simple -.-}

The problem is: Bungee updates will only be for newer versions, like 1.8 and 1.8.1.

Some servers still use Bungee 1.7 to have compatibility with both clients. I don't want to not be able to join servers just because I have Forge, specially because the mod I've done is for a server, that uses Bungee 1.7. (It's not server-side, it's client-side, but blocks some special messages from the server chat, when you press a key.)

Link to comment
Share on other sites

Well, sucks to be you. If you're joining a 1.7 server, then you can use 1.7 Forge which works just fine.

If a server admin is trying to get both 1.7 and 1.,8 clients then they are being rather stupid as the protocol changed and with the introduction of new items it's bound to crash people. And thus we wont support it.

It was requested of us by the BungeeCord people that we make FML easier to deal with. We have, its now up to them to update.

 

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Link to comment
Share on other sites

Well, sucks to be you. If you're joining a 1.7 server, then you can use 1.7 Forge which works just fine.

If a server admin is trying to get both 1.7 and 1.,8 clients then they are being rather stupid as the protocol changed and with the introduction of new items it's bound to crash people. And thus we wont support it.

It was requested of us by the BungeeCord people that we make FML easier to deal with. We have, its now up to them to update.

I won't join with 1.7 because one of the games of the server I am joining is 1.8 only.

They do it because some players CAN'T play on 1.8.

Also, did you just call all the devs from Hypixel, HiveMC and Mineplex stupid?

Btw, fix your forum please. I clicked thanks on mistake, and now I can't 'unthank'.

Link to comment
Share on other sites

Lex, the guys at Spigot have a protocol hack in place in their 1.7 builds that allow 1.8 clients to connect. 1.7 clients simply aren't shown the new 1.8 blocks.

 

LCastr0, fixed.

Read the EAQ before posting! OR ELSE!

 

This isn't building better software, its trying to grab a place in the commit list of a highly visible github project.

 

www.forgeessentials.com

 

Don't PM me, I don't check this account unless I have to.

Link to comment
Share on other sites

I won't join with 1.7 because one of the games of the server I am joining is 1.8 only.

They do it because some players CAN'T play on 1.8.

Also, did you just call all the devs from Hypixel, HiveMC and Mineplex stupid?

If they are hacking support for multiple versions of the minecraft client into there servers then yes, I am calling them stupid.

This is something I will never support if they feel like doing it then it is on there end to support it.

If you claim people "can't" run 1.8 then give me a valid reason they can't. Nothing in 1.8 save for EXTREMELY old graphics cards, i'm talking 15-20 year old cards, would cause them to not be able to use it.

 

Our 1.8 protocol is rather simple to do this error that you're encountering is simple to address on there end as well. There is nothing I can do on my end that doesn't end with me getting bitched at by Spigot/BungeeCord people to change things so its done.

 

Either way this is not my problem, so locking the thread.

 

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Hello everyone, I'm making this post to seek help for my modded block, It's a special block called FrozenBlock supposed to take the place of an old block, then after a set amount of ticks, it's supposed to revert its Block State, Entity, data... to the old block like this :  The problem I have is that the system breaks when handling multi blocks (I tried some fix but none of them worked) :  The bug I have identified is that the function "setOldBlockFields" in the item's "setFrozenBlock" function gets called once for the 1st block of multiblock getting frozen (as it should), but gets called a second time BEFORE creating the first FrozenBlock with the data of the 1st block, hence giving the same data to the two FrozenBlock :   Old Block Fields set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=head] BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@73681674 BlockEntityData : id:"minecraft:bed",x:3,y:-60,z:-6} Old Block Fields set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} Frozen Block Entity set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockPos{x=3, y=-60, z=-6} BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} Frozen Block Entity set BlockState : Block{minecraft:black_bed}[facing=east,occupied=false,part=foot] BlockPos{x=2, y=-60, z=-6} BlockEntity : net.minecraft.world.level.block.entity.BedBlockEntity@6d1aa3da BlockEntityData : {id:"minecraft:bed",x:2,y:-60,z:-6} here is the code inside my custom "freeze" item :    @Override     public @NotNull InteractionResult useOn(@NotNull UseOnContext pContext) {         if (!pContext.getLevel().isClientSide() && pContext.getHand() == InteractionHand.MAIN_HAND) {             BlockPos blockPos = pContext.getClickedPos();             BlockPos secondBlockPos = getMultiblockPos(blockPos, pContext.getLevel().getBlockState(blockPos));             if (secondBlockPos != null) {                 createFrozenBlock(pContext, secondBlockPos);             }             createFrozenBlock(pContext, blockPos);             return InteractionResult.SUCCESS;         }         return super.useOn(pContext);     }     public static void createFrozenBlock(UseOnContext pContext, BlockPos blockPos) {         BlockState oldState = pContext.getLevel().getBlockState(blockPos);         BlockEntity oldBlockEntity = oldState.hasBlockEntity() ? pContext.getLevel().getBlockEntity(blockPos) : null;         CompoundTag oldBlockEntityData = oldState.hasBlockEntity() ? oldBlockEntity.serializeNBT() : null;         if (oldBlockEntity != null) {             pContext.getLevel().removeBlockEntity(blockPos);         }         BlockState FrozenBlock = setFrozenBlock(oldState, oldBlockEntity, oldBlockEntityData);         pContext.getLevel().setBlockAndUpdate(blockPos, FrozenBlock);     }     public static BlockState setFrozenBlock(BlockState blockState, @Nullable BlockEntity blockEntity, @Nullable CompoundTag blockEntityData) {         BlockState FrozenBlock = BlockRegister.FROZEN_BLOCK.get().defaultBlockState();         ((FrozenBlock) FrozenBlock.getBlock()).setOldBlockFields(blockState, blockEntity, blockEntityData);         return FrozenBlock;     }  
    • It is an issue with quark - update it to this build: https://www.curseforge.com/minecraft/mc-mods/quark/files/3642325
    • Remove Instant Massive Structures Mod from your server     Add new crash-reports with sites like https://paste.ee/  
    • Update your drivers: https://www.amd.com/en/support/graphics/amd-radeon-r9-series/amd-radeon-r9-200-series/amd-radeon-r9-280x
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.