mnml/WORKLOG.md
2019-06-01 20:27:32 +10:00

158 lines
3.1 KiB
Markdown
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Mechanics
* 10d chaos maths, not rock paper scissors
* phys is faster and chaotic
* spells are slow and reliable
* defensives are implicit
* red_life is restored, not gained
* players can feel aggressive
- build archtypes
fast blue
slow blue
red + aggro green
blue + defensive green
- purify
- 1 effect from all constructs at level 2
- removes all effects from all constructs at l3
- invert
- fx for buffs when applied to enemies
- invert + haste -> doubles all cooldowns
- haste
- additional attack with red skills if affected
- deal % dmg based on speed difference between source and target?
- l2 maybe reduce cooldowns or something
- heal
- buff %
# WORK WORK
## NOW
*CLIENT*
targeting arrows back?
*SERVER*
* std game mode
* time control
* eth adapter
* pay for rerolls
## SOON
* push events
* iconography
* icons change with %
* find new icons for colours / life
* vbox drops chances
* 50% spec, 25% colour etc
* skills
* private fields for opponents
* matchmaking
* elo
* password on MM game to prevent direct joins
* flavour text
* chat wheel trash talk
* KO animations and trash talk
* the *real* authentication endpoint
hit /auth with un/pw or token
invalidate previous token
generate new token and return
attach token to websocket
ez
## LATER
* redis for game events
* store instances / games in redis?
* not sure hwo to get sets of player games
* set joined_games_$account [game_id]
* move player -> player
* chat
* notifications
* elo + leaderboards
* constants
* change to ownership pattern
$$$
* Items
* Colour scheme
* number of constructs
* Highlight (dota) colour
* fx colours + styles
# Db maintenance
# Art Styles
* illusions
* Aztec
* youkai
* Pixel
* Industrial
# notables
* prince of peace
* bonus healing / no damage
* fuck magic
* empower on ko
# Mechanic Ideas
players
1v1 2v2 3v3
gem td style attr combinations
stoney + spikey = jagged
plants
animals
viruses
fungus
artificial
elementals
techno artists for the soundtrack
slimey
ghostly
# Principles
* Experience something
* Express something
* Prove something
* 1: Fighting against human nature is a losing game
* 2: Aesthetics matter
* 3: Resonance is important
* 4: Make use of piggybacking
* 5: Don't confuse "interesting" with "fun"
* 6: Understand what emotion your game is trying to evoke
* 7: Allow the players the skill to make the game personal
* 8: The details are where the players fall in love with your game
* 9: Allow your players to have a sense of ownership
* 10: Leave room for the player to explore
* 11: If everyone likes your game, but no one loves it, it will fail
* 12: Don't design to prove you can do something
* 13: Make the fun part also the correct strategy to win
* 14: Don't be afraid to be blunt
* 15: Design the component for its intended audience
* 16: Be more afraid of boring your players than challenging them
* 17: You don't have to change much to change everything
* 18: Restrictions breed creativity
* 19: Your audience is good at recognizing problems and bad at solving them
* 20: All the lessons connect