Search results

I have this coded in my version of plus. I can make a release thread and tag you in it when I next get access to my computer.

Just remove "0xff" from the variable and you'll get the colour code. I wouldn't worry to much about what it unless you really want to look into Hexadecimals and binary.

Should work on most Plus Emulator edits. If you need further help, just make another post and I'll update the main thread with the required changes.

It's impossible to block packet loggers permanently. You're better off investing more time sanitising the data that gets sent from the client, rather than trying to block the use of these applications. I've posted various fixes for some of them. But just check over all the incoming events and...

Just add a randomly generated string to the end of all the files that get loaded from the client script. Everytime you update something or add something, simply change that string. That way you'll be able to force the users to cache the new data without them having to recache every time.

Replace this: base.WriteInteger(1); base.WriteInteger(Room.OwnerId); base.WriteString(Room.OwnerName);

inside the ObjectsComposer.cs and ItemsComposer.cs classes add this method: private void WriteFurniOwners(Item[] Objects) { Dictionary<int, string> furniOwners = new Dictionary<int, string>(); foreach (Item Item in Objects) { if (!furniOwners.ContainsKey(Item.UserID))...

Sorry I misread the post. I thought the room owner was changing when you placed furniture too. If you give me 5mins I'll quickly code something that'll fix your issue and update my post.

The users name not showing up when you place an item in someone elses room a packet structure issue. Inside ObjectsComposer.cs if you haven't defined all the users who have placed items in the room their usernames wont show up. It should look like this: For the room owner issue. Can you...

No worries, thanks for the updated sql. The commit can be located here for convenience to anyone who finds this easier. Just ignore the assembly changes, since I was too lazy to install the correct framework. https://github.com/DamienJolly/PlusEMU/commit/75d246f5c7a0d7b4c7c24995b867adc6b2d9ba3a

Someone asked me to code this into plus for them, thought I'd share it for everyone. @Meap And you're done.

These look really cool. Would be awesome to see what else you have lurking in those folder ;) Good job!!

As long as you're making it past handshake I wouldn't worry too much. Having unhandled packets means exactly that, but alot of them aren't needed. For instance, new user events, mobile verification events, ext. If you're getting online and it's working okay, it's best just to ignore them unless...

You'll need to update all the packets in the emulator and update the production to have access to that catalog. Either way pm me if you need help.

Or are you stupid? This can work with Phoenix and any other emulator. However the work required to get it to work with Phoenix would be immense due to how outdated it is.

That's how the pathfinding should be. (Well it is on habbo) I guessing someone edited the pathfinder to closer resemble habbos. If you don't like it you'll have to change it yourself, or find someone who knows how.

You could split the data using a different character other than space. For instance a semi colon. Or just have predefined title and descriptions. :event "param1" "param2;param3"

I coded the bundles into r2 *cries* I pretty sure they work by getting the item ids for the item them parsing them as a string split with a semicolon. Example: itemId:count;itemId:count Nvm that's for item bundles. Room bundles you have to create the room then in the catalog_bundles table put...