Thread: Dusk | #oshd | [easter weekend early access]

Originally Posted by Chance

Not at all.

Not entirely sure where your head has gone as of recent, but you've got to start going the other direction. It's simply delusional. Or this project will just be taking up space on github.

Is it delusion or strategy



Finishing up update server real quick.
[Only registered and activated users can see links. ]

-- edit

Done the basic functionality for the update server.



Much thanks to these threads:

https://www.rune-server.ee/runescape-development/rs-503-client-server/informative-threads/639009-550-update-protocol.html
https://www.rune-server.ee/runescape-development/rs-503-client-server/informative-threads/191916-update-protocol.html

Originally Posted by JayArrowz

[Only registered and activated users can see links. ]

I do not think that you require that many boss loop groups. Waste of resource to spin these up. At most you need 1

[Only registered and activated users can see links. ]

NioEventLoopGroup is a multithreaded event loop that handles I/O operation. Netty provides various EventLoopGroup implementations for different kind of transports. We are implementing a server-side application in this example, and therefore two NioEventLoopGroup will be used. The first one, often called 'boss', accepts an incoming connection. The second one, often called 'worker', handles the traffic of the accepted connection once the boss accepts the connection and registers the accepted connection to the worker. How many Threads are used and how they are mapped to the created Channels depends on the EventLoopGroup implementation and may be even configurable via a constructor.

[Only registered and activated users can see links. ] - Netty dev
"Anyway let me answer this one quickly... It only makes sense to use more than 1 when you bind multiple times (to different ports) or re-use it between different ServerBootStrap. Often it is good enough to just use the same group for boss and worker"

Also the pure laziness [Only registered and activated users can see links. ] the logger is right here yet e.printStackTrace()

Ez stuff, cheers. Did a bit of the start last night late.

Goodluck man

Originally Posted by Jord

Why do I have credits lmao I want nothing to do with this

This wouldn't be possible without you betting me $5000 I won't get 3000 players by the end of 2021.

Originally Posted by Tyluur

I love that this is the first reply.

You've been working on the same project for 3 years and have only now made a thread.
I'm getting bored of the lack of competition.

I didn't share the github link because I'm trying to poach your community of 20 loyal players .
I figured you need help. It's rather obvious isn't it?

Anyways this isn't about your feelings, keep the thread on track.

Those who live in glass houses shouldn't throw stones. You can't even commit to a project for more than a couple of weeks.

Originally Posted by hc747

Those who live in glass houses shouldn't throw stones. You can't even commit to a project for more than a couple of weeks.

These projects have literally been years in the making.

Originally Posted by Tyluur

This wouldn't be possible without you betting me $5000 I won't get 3000 players by the end of 2021.

This project, like any of your other projects won't even make it till the end of 2021. Your complete lack of commitment is astonishing. All of the projects you've started so far are more boilerplate and academic mastrubation rather than programming something useful.

Have you even had a few hundred players online? What I'm more curious about is if your boilerplate code server can even handle a hundred players tick based, it will most likely start lagging. Try focusing on that instead of bashing people who actually know what they're doing. I honestly think that is the best contribution you can give to this community, stick to what you know.