@endel I didn't know about specifying multiple database using the URI. Thanks!

For the moment I'm using a single process, but I may scale these games in the future. I'll stop using redis presence now but it looks like a temporal fix. Thanks @endel !
Is there any plan to support different games with a single redis database? It would be very useful when using more than a process per game. I mean something like choosing a namespace in the redis presence configuration:

const gameServer = new Server({
  server: http.createServer(app),
  ...
  presence: new RedisPresence({ namespace: 'my-game-one' }),  // <--
});

That namespace could be used like a preffix in any redis-key used.

Hello,

I'm using Colyseus for managing multiplayer logic in my one-week game challenge. It worked like a charm when I deployed my first project, but after adding another one I've observed errors sometimes when a user tries to create a new room.

colyseus:errors Error: seat reservation expired.

The funny thing is that I've seen room creation log message in game server A when I was really creating the room in game server B. So I guess something is getting crazy when I use redis presence in both servers.

Am I right? Could redis presence be the source of the problem when two servers use the same redis server? Is there a way, like setting a namespace or similar, to share a redis among many servers?