@endel very cool! I see how that’s handled now. Also very handy to know about the filtering features :). It seems could be really useful in implementing some sort of ranked matchmaking service.

welcome😂

@endel said in How to debug MatchMaker: ming from your application. If you're using TypeScript, the compiler should be able to warn you where the issue is. This could be happening if you have if (yourCon No, it come from the MatchMaker request

@endel Thank you for your reply.But this method is called to return an object. How can I put the object into the database?use JSON.stringify? //serverSide onCreate(options) { //check if need restore if(true){ let roomstate=getRoomStateFromDB(); this.state=JSON.Parse(roomstate);// Is it used like this? } } async onDispose() { let roomtState=JSON.stringify(this.state.toJSON()); storeDataBase(roomtState);// Is it used like this? }

As you can see in this console log from client, I removeAllListeners then I leave room. But after that, I still get message from server. How is that possible ?

@Zielak have been working on one for quite some time 👀 https://github.com/Zielak/cardsGame

@endel said in Can I access gameServer from Room ?: e gameServer, but you can access the matchMaker via Thank you.

Hi @meetsreekanth, filters are experimental right now, but it should work for the use-case you've just described. I think the order of your parameters is not correct, the filter callback type looks like this: export type FilterCallback< T extends Schema = any, V = any, R extends Schema = any > = (this: T, client: Client, value: V, root?: R) => boolean; It's also important not to use arrow functions on filters, so this should work: @filter(function (this: PlayerTurn, client: Client, value: ArraySchema<Card>, root?: GameState) { return // ?? }) Hope this helps, cheers!

I had the idea that onStateChange method includes the current state of the application, but the players MapState comes as an object without relevant data about Players. I changed that call to room.state.onChange = () => {} and it seems to be a better way to update my client-side state

Some time without publish a new release, so here's beta.11! GitHub: https://github.com/damian-pastorini/reldens NPM: https://www.npmjs.com/package/reldens Demo: http://dev.reldens.com/ Installation guide: https://github.com/damian-pastorini/reldens/wiki/New-v4.0.0-beta.x-Installation Discord: https://discord.gg/HuJMxUY What's new on this beta? Made bundler optional and created an await class for the original process. Packages updates. Fixed issues from GitHub #54, #60, #62, #63. Fixed monitor and included authentication. Exported modules @reldens/utils and @reldens/storage. Included SQL script for upgrade from beta.8 to beta.9. PvE, PvP, different attacks short and long distance are fully working, though there still some improvements to be made these are fully operational. Pathfinder was improved and pathfinder layers were included. Here's the last video:

Thanks for your reply! I think this was a networking issue in the end (maybe due to WSL on Windows) -- I changed the server port and now everything's working even without

This won't work in a @colyseus/proxy so it's not really a good solution.

@clementdreptin I got the same error! As I understand it, the problem is that webpack settings do not know how to work with mjs files. I work with nativescript-vue. I found a solution for compiling mjs files for vue, but I don't know how to integrate it into the project: // vue.config.js module.exports = { chainWebpack: config => config.resolve.extensions.prepend('.mjs').prepend('.wasm') }

Hi @endel , @codestitch , side-note, beside the allowReconnection I though some additional will be required to make it work, like express-session or so? https://www.npmjs.com/package/express-session Here is the related topic: https://discuss.colyseus.io/topic/139/persistent-sessions/4 I think https://github.com/endel/colyseus-express-session this is what you need @codestitch

Hi @SpencerWF-0 , my two cents since I've started from scratch and without any experience as well: I would recommend you to keep it as simple as possible (mostly considering this would be a first project, right?), like single language would be better, NodeJS and a JS client could be much easier then the mix you've commented. Also, Colyseus is a full Game Server on it's own, it can handle all communications, though you will need to implement you own game logic on it, so I'm not sure how much it can be integrated with Python Flask (which I don't know nothing about). Hope this helps :)

@endel Yes, it is. Haha, Cheers!