#blockserverproject

jython234 ping

PEMapModder_ PEMapModder ping

Pong

PEMapModder_ When is the meeting

When jython234 comes

PEMapModder_ What is the meeting channel?

Here

PEMapModder_ No #xyz-meeting

?

PEMapModder What happend to beaconpe-meeting

PEMapModder ^

PEMapModder_ ^^

We want to make the meeting public

PEMapModder_ Ok

[02BlockServer] 07optrusty commented on issue 03#120: Weekly meeting - 13http://git.io/LSLNSQ

[02BlockServer] 07optrusty commented on issue 03#118: RFC #4: Plugin API - 13http://git.io/tcO-RA

[02BlockServer] 07PEMapModder commented on issue 03#118: RFC #4: Plugin API - 13http://git.io/3lBISw

[02BlockServer] 07optrusty commented on issue 03#118: RFC #4: Plugin API - 13http://git.io/nJNGMA

[02BlockServer] 07PEMapModder commented on issue 03#120: Weekly meeting - 13http://git.io/Vx8iEw

jython234_: ping

PEMapModder__: long

:D

Oops ment pong

Maybe we should start nlw

*now

jython234_: still there?

Yes

I have 23 minutes before the next lesson starts

Let's start by ourselves.

Ok

So first

Yes?

About the new commits this week

The `internal` thing

What do you think?

Y

I don't fully understand it

jython234_: so, our plan is to make BlockServer support any protocols right?

Yes

So to let the same player class support any protocols

We must not handle the protocols there.

Different protocols have different packets

And we need to standardize them

Yes

Ok

A possible method is to convert them all into InternalPacket

Another method is to convert all protocols to MCPE protocol

But then this is not very sustainable for future expansion.

No

So what should we do?

I'm not sure

Which method is better?

Convert to base internal class or to an existing priticil?

Existing I think

But then

for exame

*example

We have many fields for a chat packet in MCPC

But only two fields (author and message) in MCPE

Then it will cause loss of data when we support other platfoems

We should let the protocols handle their own packets

Then?

After handling?

What do you mean by handling?

The server core is only the framework for the extensions

Each extention does its own thing

But they can work togethe

so say for example

It's like a web

I have a plugin that sends a message every 10 ticks

Yes

It wants to broadcast the message to all clients of any protocols

Ok

Then each protocol must implement a method to send that message right?

Yes

Do

So

How will we do that?

jython234_: ^

There are so many possible packets

We can't just make an interface and do all that

Therefore, the best way to do that I can think of is

Yes?

Using internal packets

An internal package that contains different structure definitions (classes)

Yes?

And then let each protocol convert the internal packet into its client-side packet.

This is my thought.

Yes?

So you think?

It's good

I like it

So agreed to continue on the internal package?

I guess

Now second thing

About the plugin API.

Yes

About the APIs

What do you think about them?

(I am on another lesson now)

I think to proceed with my loading idea

Yes?

The comment on github

We should implement all those ideas

Yes

All at PocketBukkit right?

Yes

AFK

jython234_?

Sorry have to go

jython234_: how and when will we implement them?

Optrusty: fix your connection.

[02BlockServer] 07jython234 commented on issue 03#118: RFC #4: Plugin API - 13http://git.io/RcETOg

[02BlockServer] 07PEMapModder commented on issue 03#118: RFC #4: Plugin API - 13http://git.io/kpllLA

[02BlockServer] 07jython234 commented on issue 03#118: RFC #4: Plugin API - 13http://git.io/iVHpCg

[02BlockServer] 07PEMapModder commented on issue 03#118: RFC #4: Plugin API - 13http://git.io/DUbPow