Search results

unless he's aware, it looks like he's using it as a singleton, so potentially being accessed by multiple threads are a possibility

https://mega.nz/file/oYsByBjA#LlVnMGoRJpIlnVoRvF8scn0v8DxMEjBDPtg4r1Zdkxo patched or whatever dump the common_config file and change to whatever exp: 3 mod...

\> api in go \> ws in dotnetty \> doesnt like reinventing the wheel well i wish you the best of luck not reinventing the wheel a third time. can't wait to see your progress though.

DotNetty is literally re-inventing the wheel nowadays, since WS is natively supported by MS. (what is GB?) Nitro doesn't just have quirks, I think @TheGeneral mentioned that the way it processes incoming packets are incorrect, hence why you cannot just switch been Nitro and Air without hassle...

regarding pathfinding, use reverse dijkstra - its what habbo uses currently. its fast and pretty reliable.

Yeah, the flash client definitely serves as a good base, for testing. Nitro was built around Arc/MS which did do a lot eh to make it work :-D. Yeah - DotNetty doesn't cut it for me, because you have to "make your own" http protocol initially, which .net web already does for you and then expands...

why not use EFCore? why use DotNetty when .net core offers a perfectly good TCP socket framework internally? (makes you able to support both WS and TCP with the same handlers) also remember Nitro is iffy, so you can't build it around Nitro and expect it to work with Air (for example)

habbo.dk, dec 2004 joined in the literal opening month of habbo :) my name was AQS and was literally just the headslap on the keyboard

comet>morningstar>plus>arcturus>plus++

im personally not a fan of the inertia stuff. also using laravel; don't use the __invoke method, their DI is lacking in performance

You fail to realize they live together....

care to elaborate

you change this through whatever UI editor that's available

n0minal used to have it, he left the scene though :-(

No, but I'll help you. PM me your Discord

Nothing of these sorts, no. I have to force it to join a room in the FlatAccessibleMessageComposer

My LetUserInEvent never gets called :P

Yeah this didn't do the job for me, I had to manually add my enter room method in the FlatAccessible composer, after the user has been accepted. @JMG thanks for the like, bud. However I don't find this solution suitable, it should actually be requesting LetUserIn event afterwards.

That's what I ended up with, although I had to switch back to older revision, due to doorbell bugging out

What do you exactly mean by this?