moves : {
placePiece : (G, ctx, color, x, y) => { ... }
},
turn : {
stages: {
pieceNotPlaced : {
moves : { placePiece }
},
piecePlaced : {
moves : { commit, undo }
}
}
}
npm audit. Now in place where i used to see my game board i see just the "connecting..." string without any errors. Seems that connection socket.io server works well but for some reason board is not rendered. Do you have any idea of what could be the problem?
10 replies
8 replies
33 replies
1 reply
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?
13 replies
13 replies
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.)
1 reply
I think i'm missing something simple. :) I have a game I've just updated from v0.44 - which used to work.
Basically, it's the whole "you can pick up until the next player plays" scenario.
I've implemented it as a stage that the current player goes into just after endTurn() is called... but it's not working any more.
Code looks like so:
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?Should I be doing this some other way now?
1 reply
3 replies
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.
1 reply
Hey folks,
I am currently a bit confused on how multiplayer credentials work.
My setup looks like this:
- I have a react client
- and I have the boardgame.io koa server
- I want to authenticate via JWT
- I have a custom login route, where user POST their username + password
- the server will then issue a JWT and put it into an HttpOnly cookie, which will be used to authenticate all following requests
Now as far as I understand the docs I need three things:
- A generateCredentials function which retrieves some unique key (the username in my case)
- An authenticateCredentials function which checks if the credentials provided are valid
- I need to set the credentials prop on the GameClient-react component
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.
3 replies
"code": 5,
"message": "Unsupported protocol version"
}
1 reply
17 replies
I'm looking for a freelance JS developer to help me finish and maintain my VueJS + BoardGameIO project.
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:
- Order and unify server APIs: Some are on Koa's internal server; others are in a different express server (a consequence of the learning process).
- Test and debug P2P invitation system. It is working but barely tested. Some border cases or unexpected scenarios (network loss) might create a problem. (Implemented, barely tested).
- Test and debug statistics storage (at the end of the game, make some calculations and save to the DDBB (implemented, with bugs).
- Implement a medal system. Based on statistics. (Nos implemented)
- Implement firebase auth with google account, Facebook and Twitter (not implemented, A simple cookie-based method is currently implemented).
- I have an android and iPhone webview app that, when loads the page, uses the native SDK. I want to conserve that.
- Implement logout and account deletion (not implemented).
- Improve API security. (Implement a JWT based solution).
- Create API methods for getting statistics:
- Games actives.
- Games today.
- Games this month.
- etc.
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.