Jump to content
  • We are looking for staff for the Wiki area!
    If interested please
    click here and select "Documentation Team"

  • Mangos Online Packet Editor (MOPE)


    antz

    Since Mangos was first devised, the knowledge behind the packets sending information to and from the server has always been kept under wraps.

    - Anyone asking about information was normally told to 'go look in the code for details'

    I have long hated this so called cloak and dagger ideal as it harms the community greatly when people who have that information move on.

    I have therefore decided to create a Central Packet Knowledge System which covers all the versions of Wow.

    On that end I have set up a central Database, along with a small application to assist in populating this DB. The eventual goal is to extract all the relevant information back out and populate the Wiki with the information.

    The project is only in it's alpha stage, so any help testing or entering information would be greatly appreciated. Please contact @antz for a copy of the App plus log in credentials.

    MOPE1.jpg

    This is main log in screen.

     

    MOPE2.jpg

    A blank search is automatically done for you, the selected core is Classic by default.

    Click on a packet entry opens up the Edit Packet Screen

    MOPE3.jpg

    This contains various information about the packet as well as the packet field definitions.

    Double-clicking on a field will open the field definition screen.

    MOPE4.jpg

    This screen allows you to enter as much field information is you can, optionally you can also adjust which core this field is valid for (out of a maximum of the cores using this packet). This allows for different fields / field order based on the core it's used for.

    MOPE5.jpg

    You can also use searches to filter the main list of packets.

    Edited by antz


    User Feedback

    Recommended Comments

    Just realized that the project name is misguiding. If I understand correctly, this is an editor for documentation (description) of the packets, not for the packets itself.

    Also, you have no need to port C# code to Linux. There is the .NET port "mono", containing both the compilator and the execution medium for JIT binaries. I've executed the JIT binaries generated under Win by the VS for "any CPU", on a Linux system under mono with no issue.

    Link to comment
    Share on other sites



    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy Terms of Use