Skip to content

Goal ~ Messages Outlined #153

Open
Open

Description

@Exerosis

We need to outline all of the messages we will need to make the server function correctly... so the message class name.... what it extends... and what fields it has... however we can start with just a list of what messages we have... As soon as this is done, other devs can create said messages.

Might sound easy, but after you take a look you will find it very difficult, remeber that some logic can be involved. For example, the MessageBlockRemoved will be a BlockRemovedPacket on PE, and for PC it will be a BlockChangePacket with the value of air.(just an example)

Protocol:
http://wiki.vg/Protocol
http://wiki.vg/Pocket_Minecraft_Protocol

Activity

  1. added this to the milestone on Dec 10, 2015
  2. alejzeis commented on Dec 10, 2015

    @alejzeis
    Contributor
  3. Exerosis commented on Dec 10, 2015

    @Exerosis
    ContributorAuthor

    What do you mean? Lol the converters need to be made and I promise you need
    an outline. Also is there a new wiki.vg

    On Thu, Dec 10, 2015, 4:52 PM jython234 notifications@github.com wrote:

    @Exerosis that doesn't matter, leave the translations to the converters

    —
    Reply to this email directly or view it on GitHub
    #153 (comment)
    .

  4. alejzeis commented on Dec 10, 2015

    @alejzeis
    Contributor

    @Exerosis the message names don't matter, name them of what they represent such as BlockPlaceMessage for placing a block.

  5. Exerosis commented on Dec 10, 2015

    @Exerosis
    ContributorAuthor

    Yea IK... but what happens when somebody does networkmodule.sendMessage(blockPlaceMessage)? obviously that need to be turned into a packet for PC and a packet for PE... IK those packets AREN"T the same... so what about the packets that PE doesn't even have? or PC doesn't even have?

  6. PEMapModder commented on Dec 11, 2015

    @PEMapModder
    Member

    That's why the request/response system is good ;)

  7. Exerosis commented on Dec 11, 2015

    @Exerosis
    ContributorAuthor

    I'm so confused... as far as IK there is ONLY one way to get info to clients :|

  8. alejzeis commented on Dec 11, 2015

    @alejzeis
    Contributor

    You still don't get it, message names do not matter! The converter checks
    what instance of message it is and translates it. If there are no packets
    for it, it is dropped.

    On Thursday, December 10, 2015, Exerosis notifications@github.com wrote:

    I'm so confused... as far as IK there is ONLY one way to get info to
    clients :|

    —
    Reply to this email directly or view it on GitHub
    #153 (comment)
    .

  9. Exerosis commented on Dec 11, 2015

    @Exerosis
    ContributorAuthor

    WTF????? I mean what message classes will we have??

  10. PEMapModder commented on Dec 11, 2015

    @PEMapModder
    Member

    @jython234 a message refers to a type of info, which will be converted into PE/PC protocol when being sent. Correct?

  11. Exerosis commented on Dec 11, 2015

    @Exerosis
    ContributorAuthor

    I thought they where kind of like packets but instead of being sent they
    are converted. So they have all the fields a packet might but nice getters
    and setter etc.

    On Fri, Dec 11, 2015, 3:28 AM PEMapModder notifications@github.com wrote:

    @jython234 https://github.com/jython234 a message refers to a type of
    info, which will be converted into PE/PC protocol when being sent. Correct?

    —
    Reply to this email directly or view it on GitHub
    #153 (comment)
    .

  12. 7 remaining items

  13. Exerosis commented on Dec 13, 2015

    @Exerosis
    ContributorAuthor

    ;( there is no API ;( ;( ;( ;(

  14. PEMapModder commented on Dec 13, 2015

    @PEMapModder
    Member

    No, by API I mean the internal methods.

  15. Exerosis commented on Dec 13, 2015

    @Exerosis
    ContributorAuthor

    Oh ok, well what I mean... is a document... that lists the MessageName(class) and the two(or more) corrisponding packets.

  16. PEMapModder commented on Dec 13, 2015

    @PEMapModder
    Member

    You mean protocol documentation right? Well, there isn't, we will put them into code directly when we figure them out.

  17. Exerosis commented on Dec 13, 2015

    @Exerosis
    ContributorAuthor

    :( >:( ;(I just mean a plan... a google docs... that we can give to other devs who can then make the message classes and add to the converters

  18. PEMapModder commented on Dec 13, 2015

    @PEMapModder
    Member

    I suggested a concept of Protocol Documentation Format (PRDF), which is a file, in similar syntax to .htaccess, declaring packets and gets loaded by a server.

  19. Exerosis commented on Dec 13, 2015

    @Exerosis
    ContributorAuthor

    ERMMMMM I think I like that idea?

  20. Exerosis commented on Dec 13, 2015

    @Exerosis
    ContributorAuthor

    Hummm IDK that it would work out tho ;( we will see.. but either way... for now we need a document that would let us hand off the creation of 5 or 10 of the packets to other devs without explaing the whole opperation... and that invloves lookng at both documentations... and deciding what messages we will have and what not...

  21. PEMapModder commented on Dec 13, 2015

    @PEMapModder
    Member

    And that document can be in PRDF :) if we are planning to implement such thing, of course. Something like this. https://github.com/RedstoneLamp/RedstoneLamp/blob/npd/src/main/resources/protocol/example-protocol.npd

  22. Exerosis commented on Dec 13, 2015

    @Exerosis
    ContributorAuthor

    TBH that confuses me a tiny bit but either way we do need an outline or at
    least a list of every message we plan to implement and what fields they
    will have.

    On Sun, Dec 13, 2015 at 9:08 AM PEMapModder notifications@github.com
    wrote:

    And that document can be in PRDF :) if we are planning to implement such
    thing, of course. Something like this.
    https://github.com/RedstoneLamp/RedstoneLamp/blob/npd/src/main/resources/protocol/example-protocol.npd

    —
    Reply to this email directly or view it on GitHub
    #153 (comment)
    .

  23. Exerosis commented on Dec 13, 2015

    @Exerosis
    ContributorAuthor

    sigh lol look... if somebody makes a a list of each module we need... and what fields it has... or at leaset the list... I could quickly create a message higherarchy and then begin work on the core modules.

  24. alejzeis commented on Dec 13, 2015

    @alejzeis
    Contributor

    @Exerosis I made the messages as I went implementing packets, in RL.

  25. modified the milestones: , Beta 1.0.0 on Jan 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions