[HEADERS] PRODUCTION-201812272209-984739530

[jordynegen11]

Hi,

Here is a header list of PRODUCTION-201812272209-984739530

Changes so far found since PRODUCTION-201707041014-428081343:

• YouAreControllerMessageComposer -> added an extra integar with the roomid
• YouAreOwnerComposer -> added an extra integar with the roomid
• FlatAccessDeniedMessageComposer -> added an extra integar with the roomid
• FlatAccessibleMessageComposer -> added an extra integar with the roomid
• GetBadgesEvent-> BadgesComposer is splitted in 2 outgoing messages (BadgesComposer, HabboUserBadgesComposer)

Incoming:

You must be registered for see links

Outgoing

You must be registered for see links

For the cracked SWF + RSA keys:

You must be registered for see links

 

[harambe]

No RSA keys?

 

[jorydnegen11]

No RSA keys?

I included no habbo.swf so why i should give you any RSA keys?

 

[dominic]

GetBadgesEvent-> BadgesComposer is splitted in 2 outgoing messages (BadgesComposer, HabboUserBadgesComposer)

What do you exactly mean by this?

 

[treebeard]

What do you exactly mean by this?

I'm assuming he means the old BadgesComposer is now split into two different composers that are sent in response to GetBadgesEvent.

I'm not so familiar with the newer protocol but I would guess that one composer prepares the badges in general and the other sends the specific badges being worn by the user.

 

[harambe]

I included no habbo.swf so why i should give you any RSA keys?

Would be nice to have released them too, but thank you for these headers!

 

[dominic]

I'm assuming he means the old BadgesComposer is now split into two different composers that are sent in response to GetBadgesEvent.

I'm not so familiar with the newer protocol but I would guess that one composer prepares the badges in general and the other sends the specific badges being worn by the user.

That's what I ended up with, although I had to switch back to older revision, due to doorbell bugging out

 

[jordynegen11]

What do you exactly mean by this?

I'm assuming he means the old BadgesComposer is now split into two different composers that are sent in response to GetBadgesEvent.

I'm not so familiar with the newer protocol but I would guess that one composer prepares the badges in general and the other sends the specific badges being worn by the user.

@treebeard is right.

New structure BadgesComposer:

INT //unkown
INT //unkown
INT //count
{
  INT // always 1?
  STRING //Badge Name
}

PLUS emulator new GetBadgesEvent.cs:

using System;
using System.Linq;
using System.Text;

using Plus.Communication.Packets.Outgoing.Inventory.Badges;
using Plus.Communication.Packets.Outgoing.Users;

namespace Plus.Communication.Packets.Incoming.Inventory.Badges
{
    class GetBadgesEvent : IPacketEvent
    {
        public void Parse(HabboHotel.GameClients.GameClient Session, ClientPacket Packet)
        {
            Session.SendMessage(new BadgesComposer(Session));
            Session.SendMessage(new HabboUserBadgesComposer(Session.GetHabbo()));
        }
    }
}

PLUS emulator new BadgesComposer.cs:

using System;
using System.Linq;
using System.Text;
using System.Collections.Generic;

using Plus.HabboHotel.GameClients;
using Plus.HabboHotel.Users.Badges;

namespace Plus.Communication.Packets.Outgoing.Inventory.Badges
{
    class BadgesComposer : ServerPacket
    {
        public BadgesComposer(GameClient Session)
            : base(ServerPacketHeader.BadgesMessageComposer)
        {
            List<Badge> EquippedBadges = new List<Badge>();

            base.WriteInteger(1);
            base.WriteInteger(0);
            base.WriteInteger(Session.GetHabbo().GetBadgeComponent().Count);
            foreach (Badge Badge in Session.GetHabbo().GetBadgeComponent().GetBadges().ToList())
            {
                if (Badge != null)
                {
                    base.WriteInteger(1);
                    base.WriteString(Badge.Code);

                    if (Badge.Slot > 0)
                        EquippedBadges.Add(Badge);
                }
                else
                {
                    base.WriteInteger(0);
                    base.WriteString("ABC");
                }
            }
        }
    }
}

PLUS emulator new HabboUserBadgesComposer.cs:

using System;
using System.Linq;
using System.Text;
using System.Collections.Generic;

using Plus.HabboHotel.Users;
using Plus.HabboHotel.Users.Badges;

namespace Plus.Communication.Packets.Outgoing.Users
{
    class HabboUserBadgesComposer : ServerPacket
    {
        public HabboUserBadgesComposer(Habbo Habbo)
            : base(ServerPacketHeader.HabboUserBadgesMessageComposer)
        {
            base.WriteInteger(Habbo.Id);
            base.WriteInteger(Habbo.GetBadgeComponent().EquippedCount);

            foreach (Badge Badge in Habbo.GetBadgeComponent().GetBadges().ToList())
            {
                if (Badge.Slot <= 0)
                    continue;

                base.WriteInteger(Badge.Slot);
                base.WriteString(Badge.Code);
            }
        }
    }
}

 

[jordynegen11]

That's what I ended up with, although I had to switch back to older revision, due to doorbell bugging out

Fix for doorbell:

FlatAccessDeniedMessageComposer -> added an extra integar with the roomid
FlatAccessDeniedMessageComposer.cs

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace Plus.Communication.Packets.Outgoing.Rooms.Session
{
    class FlatAccessibleComposer : ServerPacket
    {
        public FlatAccessibleComposer(int RoomId, string Username)
            : base(ServerPacketHeader.FlatAccessibleMessageComposer)
        {
            base.WriteInteger(RoomId);
            base.WriteString(Username);
        }
    }
}

FlatAccessibleMessageComposer -> added an extra integar with the roomid
FlatAccessibleComposer.CS:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace Plus.Communication.Packets.Outgoing.Rooms.Session
{
    class FlatAccessibleComposer : ServerPacket
    {
        public FlatAccessibleComposer(int RoomId, string Username)
            : base(ServerPacketHeader.FlatAccessibleMessageComposer)
        {
            base.WriteInteger(RoomId);
            base.WriteString(Username);
        }
    }
}

 

[dominic]

Fix for doorbell:

FlatAccessDeniedMessageComposer -> added an extra integar with the roomid
FlatAccessDeniedMessageComposer.cs

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace Plus.Communication.Packets.Outgoing.Rooms.Session
{
    class FlatAccessibleComposer : ServerPacket
    {
        public FlatAccessibleComposer(int RoomId, string Username)
            : base(ServerPacketHeader.FlatAccessibleMessageComposer)
        {
            base.WriteInteger(RoomId);
            base.WriteString(Username);
        }
    }
}

FlatAccessibleMessageComposer -> added an extra integar with the roomid
FlatAccessibleComposer.CS:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Threading.Tasks;

namespace Plus.Communication.Packets.Outgoing.Rooms.Session
{
    class FlatAccessibleComposer : ServerPacket
    {
        public FlatAccessibleComposer(int RoomId, string Username)
            : base(ServerPacketHeader.FlatAccessibleMessageComposer)
        {
            base.WriteInteger(RoomId);
            base.WriteString(Username);
        }
    }
}

Yeah this didn't do the job for me, I had to manually add my enter room method in the FlatAccessible composer, after the user has been accepted.

@JMG thanks for the like, bud. However I don't find this solution suitable, it should actually be requesting LetUserIn event afterwards.

 

[jordynegen11]

Yeah this didn't do the job for me, I had to manually add my enter room method in the FlatAccessible composer, after the user has been accepted.

@JMG thanks for the like, bud. However I don't find this solution suitable, it should actually be requesting LetUserIn event afterwards.

You are right. It only fixes the disconnect. You have to add the EnterRoom function in the LetUserInEvent

 

[dominic]

You are right. It only fixes the disconnect. You have to add the EnterRoom function in the LetUserInEvent

My LetUserInEvent never gets called

 

[jordynegen11]

My LetUserInEvent never gets called

O my friend, then something i really wrong. Is there another header called instead? mabe you have the wrong incoming header id :O

 

[dominic]

O my friend, then something i really wrong. Is there another header called instead? mabe you have the wrong incoming header id :O

Nothing of these sorts, no. I have to force it to join a room in the FlatAccessibleMessageComposer

 

[xXMufaisaXx]

Nothing of these sorts, no. I have to force it to join a room in the FlatAccessibleMessageComposer

Any chance you wanna post the letuserinevent you have and the force enter script you used?

 

[dominic]

Any chance you wanna post the letuserinevent you have and the force enter script you used?

No, but I'll help you. PM me your Discord

 

[Sirgam]

I need some Help...

You must be registered for see images attach

 

[xXMufaisaXx]

No, but I'll help you. PM me your Discord

Hey bro. i got a few things i wanna run by you if you dont mind? help would be amazing. my disc is PythoneX12#7214