Navigation

    • Register
    • Login
    • Search
    • Categories
    • Popular
    • Users
    1. Home
    2. dpastorini
    3. Topics
    • Continue chat with dpastorini
    • Start new chat with dpastorini
    • Flag Profile
    • block_user
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    Topics created by dpastorini

    • Reldens - MMORPG Platform
      Showcase • • dpastorini

      10
      1
      Votes
      10
      Posts
      4479
      Views

      New beta released! https://www.reldens.com/beta-15-released
    • MMORPG - V1.2.6
      Showcase • • dpastorini

      4
      0
      Votes
      4
      Posts
      2451
      Views

      Still quite lagged, poor server but it shows the point: http://dev.reldens.com :)
    • Plane P2JS tiledmap demo - How to use Phaser 3 physics engine on the server
      Links & Resources • • dpastorini

      1
      1
      Votes
      1
      Posts
      1027
      Views

      No one has replied

    • Client left room before receiving session id
      Questions & Help • • dpastorini

      2
      0
      Votes
      2
      Posts
      1195
      Views

      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,
    • Join rooms sharing auth
      Questions & Help • • dpastorini

      11
      0
      Votes
      11
      Posts
      4311
      Views

      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,
    • State update and onJoin timing
      Questions & Help • • dpastorini

      2
      0
      Votes
      2
      Posts
      1589
      Views

      FYI: just updated https://github.com/damian-pastorini/dwdgame with the last code changes I made.
    • Base MMORPG - Node, MySQL, Colyseus, Parcel and Phaser 3
      Showcase • • dpastorini

      1
      1
      Votes
      1
      Posts
      3462
      Views

      No one has replied

    • Phaser 3 Integration - Server and client?
      Questions & Help • • dpastorini

      3
      0
      Votes
      3
      Posts
      2379
      Views

      Thanks for the reply @lw1990 I'll look for the solution like it's mentioned in the old post then.
    • Persistent sessions
      Questions & Help • • dpastorini

      10
      0
      Votes
      10
      Posts
      5161
      Views

      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
    • Game Examples not working at all
      Questions & Help • • dpastorini

      5
      0
      Votes
      5
      Posts
      2053
      Views

      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,