Signed-off-by: André Jaenisch <firstname.lastname@example.org>
|1 year ago|
|.husky||1 year ago|
|dist||1 year ago|
|gdd||1 year ago|
|scripts||1 year ago|
|src||1 year ago|
|test||1 year ago|
|.eslintrc.json||1 year ago|
|.gitignore||1 year ago|
|.mocharc.cjs||1 year ago|
|.nycrc.json||1 year ago|
|LICENSE.txt||1 year ago|
|README.md||1 year ago|
|commitlint.config.cjs||1 year ago|
|index.d.ts||1 year ago|
|index.test-d.ts||1 year ago|
|package-lock.json||1 year ago|
|package.json||1 year ago|
|tsconfig.json||1 year ago|
Grow emojis together
I use that jam for exploring some multiplayer ideas I wouldn't be able to implement for js13kgames.
Right now, the game is about growing a plant …
One player can control the weather, the other the plant. They communicate via emojis.
Weather can consist of 🌞or 🌧️ or 🌬️, I guess. It corresponds to 🙂 / 😭 / 😗.
Now, on the other hand, I'd like to see a plant grow.
I have 🌱and 🌳 and 🍃and 🍂.
Link to https://github.com/dev-mastery/comments-api for client directory structure
Link to https://github.com/flowingis/strazz-talk-cityjs2021 for rendering engine
Link to https://github.com/onehungrymind/fem-enterprise-patterns for state management
Respond with „You shall no pass!” to all other requests.
Should user pick a hue and then use hue-rotate filter to personalise emojis?
Use Reducers and action creators for state management
Check actions on 'isFSA` (Flux Standard Action)
These are the core entities in my game. They collect properties in a structure.
The UI first asks for a nickname. It then generates a nanoid and associates it with this person. A person can either have the role host or guest.
A party has a person nanoid as host and a list of people nanoids as guests.
A person can create a party. In this case, that person will become the host. Alternatively, a person can join an existing party as guest. The host has to accept the request to join. Each person can only be in one party at any given time. With closing of the connection, that person will leave its party.
A session has a nanoid, that maps to a party. That is the only information the server will ever hold. The server maintains a list of parties. The remaining communication uses WebRTC DataChannels.
A plant evolves through all four seasons. It starts in spring. To grow, it needs fresh air, rain and sunlight. It needs to exceed a certain treshold to reach the next level.
Models are interacting with each other in a defined way.
Create a party
The user creates a request to the server to create a new session and adds the id of that user as host. The guests are an empty array.