Topics created by dpastorini

Hello everyone! Long time without post any updates and that's because this is a big one. I've created two new websites, one for me dwdeveloper.com, and one for the project reldens.com Along with this I've also deployed a new beta of the project: v4.0.0-beta.14 which includes a lot of new features! The main ones: Inventory system. Equipment. Improvements on responsive screen and mobile experience. A bit better performance related to some recursive unneeded queries to the database. And a lot of other changes that you can check on the change log. For last I've also created accounts on Patreon and Ko-fi so any support will be really appreciated, this project can be a reality sooner if I can get any support. Obviously by support I never mean only money, I'm also looking for anyone that would like to collaborate on the graphics side and improve the demo. Any feedback will be appreciated! I've put a lot of effort on this and I will keep doing it! So I hope you like it! Regards, Damian

Still quite lagged, poor server but it shows the point: http://dev.reldens.com :)

If anyone has this issue and you are trying to use multiple join / left rooms like I was doing, make sure to always be joined in one room. In my case I was leaving one room before join the next one, so I moved the oldroom.leave() action inside the newroom.onJoin() and now everything works fine. Note, this was happening randomly at the beginning until I overloaded the room onInit with data, then I got the issue all the time because the second room was delayed on load. Best,

Hi @endel thanks for you quick reply, as you said... yeah.. too many issues already LOL I'll go for the database option to persist the data between room changes, I'm working on it now, the idea is to save the player progress > leave the room > join the new room > re-authenticate the user with the data in the session and reload the progress. I though it will be too expensive in terms of server response time, but keep a room or persist too much information in the presence could end up been even more expensive than just hit the DB to get the data. Best,

FYI: just updated https://github.com/damian-pastorini/dwdgame with the last code changes I made.

Thanks for the reply @lw1990 I'll look for the solution like it's mentioned in the old post then.

Hi guys, I know this is an old topic, but I've just made a simple demonstration on how to use express-session with colyseus's onAuth() method here: https://github.com/endel/colyseus-express-session

Last one: one of the features in the 04-create-or-join-room.html example seems to be broken. In the client I got: colyseus.js: server error: Failed to join invalid room "a-QUjQJmPs" In the server: CREATING NEW ROOM Error: Failed to join invalid room "a-QUjQJmPs" at MatchMaker.<anonymous> (/var/www/questworld/colyseus-examples/node_modules/colyseus/lib/MatchMaker.js:124:23) at next (native) at fulfilled (/var/www/questworld/colyseus-examples/node_modules/colyseus/lib/MatchMaker.js:4:58) at process._tickDomainCallback (internal/process/next_tick.js:135:7) Best,