You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
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?
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.
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.
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.
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...
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.
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.
Activity
alejzeis commentedon Dec 10, 2015
Exerosis commentedon Dec 10, 2015
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:
alejzeis commentedon Dec 10, 2015
@Exerosis the message names don't matter, name them of what they represent such as BlockPlaceMessage for placing a block.
Exerosis commentedon Dec 10, 2015
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?
PEMapModder commentedon Dec 11, 2015
That's why the request/response system is good ;)
Exerosis commentedon Dec 11, 2015
I'm so confused... as far as IK there is ONLY one way to get info to clients :|
alejzeis commentedon Dec 11, 2015
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:
Exerosis commentedon Dec 11, 2015
WTF????? I mean what message classes will we have??
PEMapModder commentedon Dec 11, 2015
@jython234 a message refers to a type of info, which will be converted into PE/PC protocol when being sent. Correct?
Exerosis commentedon Dec 11, 2015
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:
7 remaining items
Exerosis commentedon Dec 13, 2015
;( there is no API ;( ;( ;( ;(
PEMapModder commentedon Dec 13, 2015
No, by API I mean the internal methods.
Exerosis commentedon Dec 13, 2015
Oh ok, well what I mean... is a document... that lists the MessageName(class) and the two(or more) corrisponding packets.
PEMapModder commentedon Dec 13, 2015
You mean protocol documentation right? Well, there isn't, we will put them into code directly when we figure them out.
Exerosis commentedon Dec 13, 2015
PEMapModder commentedon Dec 13, 2015
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.Exerosis commentedon Dec 13, 2015
ERMMMMM I think I like that idea?
Exerosis commentedon Dec 13, 2015
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...
PEMapModder commentedon Dec 13, 2015
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
Exerosis commentedon Dec 13, 2015
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:
Exerosis commentedon Dec 13, 2015
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.
alejzeis commentedon Dec 13, 2015
@Exerosis I made the messages as I went implementing packets, in RL.