interface SocketIOOpts
socketOpts?
was changed from any
to ioNamespace.SocketOptions
. Unfortunately, this means I can no longer initialize my Client
with multiplayer: SocketIO({ server: server_url, socketOpts: { path: '/sub/socket.io' } })
because path
is no longer accepted. Any ideas?
Hi, its me again 😅
I am currently having a weird issue (I probably had it before, but did not realize it).
Inside my game definition I set a seed for randomization. The seed is being generated by a call to nanoid().
However I noticed that the seed will only be set once for the game, not for each match instance I create.
Therefore each match will have the exact same randomization output.
I noticed this issue from 2018 boardgameio/boardgame.io#233 - however if I interpret it correctly, this has long been resolved.
Now I am wondering what I should be doing differently. I haven't found a way to tell the server to use a new seed when a new match is being created via the lobby API.
What am I missing here? :)
AHHHH nvm. I missunderstood how the seed works. The server already generates a new seed for each match. Overriding the seed is only necessary, if I want to use a specific seed (e.g. for testing etc.)
var activePlayersValue = {};
activePlayersValue[ctx.currentPlayer] = 'pickup'; //store up the current player to put into the pickup stage.
ctx.events.endTurn();
ctx.events.setActivePlayers({ currentPlayer: Stage.NULL, value: activePlayersValue, maxMoves: (6 - cardCount) }); //let them draw back to 6?
multiplayer: Local({
bots: {
0: MCTSBot,
1: MCTSBot,
},
}),
NODE_ENV
environment variable is 'production'
. Maybe double check process.env.NODE_ENV
is set to something else during development.
Hey folks,
I am currently a bit confused on how multiplayer credentials work.
My setup looks like this:
Now as far as I understand the docs I need three things:
I assume that the authenticateCredentials function takes whatever I put into the React-Components credentials prop as its first parameter. Is that correct?
This means I would not be able to use an HttpOnly-cookie because I won't be able to access it via JS from the client, so that I can hand it to the GameClient.
Is there anything I am missing? There does not seem to be a way to access the koa app.ctx inside the authenticateCredentials function, so that I could get the cookie from there.
The second version of my game (www.abak.me) is built on vueJS (3) + boardgame.io + expressJS. I wrote almost entirely the UI and a huge part of the server-side methods. Still, I need a lot of testing, debugging, and implementing some functionalities, messages, and server-side tools to monitor and manage server-side behavior.
Here you can see the production version (#1): https://www.abak.me Here you can see the new version I'm working on (#2): http://54.213.212.155/
The issue is I'm not in the mood to keep programming. I'm an old guy with a job and a family and, to do this, I need heavy inspiration, which I had six months ago (while I was learning to use vue), but I'm laking right now. But I really want to upgrade my game version, so I need help and decided that this might be the best place to look, given the engine I have used, and yet the boardgame.io part is done.
These are the tasks needed to finish it; most of them are server-side:
I think the code is reasonably well arranged and easy to follow. It is not really commented, though, but I can be your wiki.
I would love to work with a talented programmer who likes the game and aligns itself with my objectives. I can pay with Paypal and cryptos. We can define payment for each task, and we should need to have an induction session to explain the components.