Official Everybody Edits Forums

Hello there,

simply put: whenever I try to join the first world of the Wintery Wonders Campaign 'Frostbitten' I get disconnected with the following error message: http://prntscr.com/a0dcez
I have had this issues for several days now, tried logging in and out on both beta.everybodyedits.com as well as everybodyedits.com but nothing helped. I am wondering if only I am experiencing
this bug or whether this might bee a frequent issue. In any case I would be delighted if it could be helped.

Best regards,
EuadeLuxe

Hi there,

Some profiles don't seem to be aligned properly when viewing them on the homepage:

As this only happens shortly after worlds are being loaded I suspect it's got to do with the arrangement and sizes of the world minimaps shown on the right.

Meta-Information:
Browser: Google Chrome
Browser Version: 45.0.2454.101 m
Flash version: Shockwave Flash 19.0.0.185 (PPAPI, PepperFlash)

Hope that information is detailed enough.

Best regards,
EuadeLuxe.

Introduction

Hello to all of you out here,

after quite some time I went back to creating bots for EE and soon got into it again. Actually though, I have been disgusted of writing the "message" handlers (as PlayerIO calls them) all by branching for different types of messages and always having to know the order of the messages internally in order to get at the information I want. Therefore I sat down and wrote a small system which might be useful to some of you. Please excuse me, if something similiar already exists, but as I said I just returned to creating bots so i'm not up-to-date when it comes to that.

Below you will find a quick overview of the system and a link to the GitHub-Repository.

----------------------------------------------------------------------------------------------------------------

The Basic Concepts

The basic concept of "MessageLib" (that's what it's called like) is that all messages sent to EE or received from EE are wrapped into classes. Each class may then either be an inbound packet (i.e. a packet which you receive) or an outbound packet (which you may send). Using the Connection object which probably all of you know you are given an extension method called Send(...) which will effectively do all the serialization into the actual Message object for you, i.e. there's no difference in whether or decide to use messages directly or use MessageLib. For inbound packets things even get a bit nicer as MessageLib provides you with something I call a "Dispatcher". Whenever you acquire a new connection object you may hand it over to the dispatcher which will from now on respond to all received messages and dispatch them around all your listeners. I hear you saying: "But what da heck are listeners?" Well, arguably it'd be best, if I'd just show you a little example:

using MessageLib;

namespace MyHyperCoolBot
{
    public class MainClass
    {
        public static void Main()
        {
            // We assume that these instances we're already initialized:
            PlayerIOClient.Connection connection;

            // Here we may now create our dispatcher:
            PacketDispatcher dispatcher = new PacketDispatcher();
            dispatcher.AddConnection( connection );
            dispatcher.RegisterListener( new MyPacketListener() );
        }
    }


    public class MyPacketListener : IPacketListener
    {
        [PacketHandler]
        public void onInit ( Packets.In.PacketInit init )
        {
            // Do something awesome with our packet:
            string worldKey = init.Derot;
        }
    }
}

In this example the onInit(...) method of our listener will be invoked whenever an "init" message is received. Why is that? Because the packet dispatcher does all the work of deserializing the messages appropriately for you and then invokes any methods of listeners registered to it which fulfill the following conditions:

1. The method possesses an PacketHandler attribute

2. The method takes exactly one parameter which is an instantiatable type implementing the IInboundPacket interface

This effectively means that you may treat whatever EE sends to you as some kind of event which may be handled by any object you like. Another example for getting notified whenever a user takes the crown:

[PacketHandler]
public void onPlayerCrown( Packets.In.PacketPlayerCrown crown )
{
    // We might do all kinds of things here. crown.UserID is the ID of the user who has taken the crown.
}

For sending a packet back to EE we would do something like this:

connection.Send( new Packets.Out.PacketPlayerTrophy() );

which would give our bot the silver crown. The library comes with a whole bunch of predefined packet classes. If you find them to be wrong or not working please let me now, or even fix them yourself. If you are missing In- / Outbound packets you may tell me as well or you may even write them yourself. Just have a look at how it's done in the library itself, it's really not that hard. Just don't forget to make your packet known to the PacketDispatcher by doing:

dispatcher.RegisterPacket( typeof( MyVeryAwesomePacket() ) );

----------------------------------------------------------------------------------------------------------------

Conclusion

To me this system has proven its value as it allowed me to decentralize my work a lot more than registering message handlers all the time. Also it allows for much cleaner code in my opinion - that must not be true in yours as well (!).

Finally, here's the link to the project's GitHub-Repository, enjoy: https://github.com/EuadeLuxe/MessageLib

Best regards,
EuadeLuxe.