Problems and solution

This should be a growing list on how to solve certain story-coding-problems in Tweego/snowman:

Most of those things are implemented in my test-game.

Working with HTML/CSS

• static styling with CSS
• using images and other media
• stacking multiple images to create a grafical scenery without coding
• using fonts as icons
• create game screen

Working with javascript

• Debugging your story
• development/debug-build
• organizing javascript sources
• Adding js-modules

Adding features by javascript:

• custom event handler
• using canvas for drawing dynamic images
• SVG and javascript
• SVG and javascript#2
• embedding JS in SVG
• reuse and style SVG
• dynamic SVG creation
• Links,Buttons and other interactives
• using plain links in replacement of passage-links
• expand a hidden info-text/image when clicking a link
• show popup on hover or click
• show toast on variable change
• Using CSS animations
• Switching CSS themes
• call passage with parameters
• implementing a Back-mechanic for stacked sub-passages

Game-Save/-Load

• using browser-storage for Game-save
• using local filestorage for Game-save
• creating a modal save dialog similar to sugarcubes Save/Load-screen
• add autosave feature
• restoring game-objects from json
• disable save in a scene

Common game-components

• where to store game-state and game-functions
• Achievements and NewGame+
• creating a daily schedule
• Quest-System
• creating inventory and items management
• outfit and equipment management
• Stats/Attributes- and Effects/States-System
• (very basic) turnbased combat with text output
• dungeon-navigation plus map
• deffered events/passages that are not immediatly shown
• bodymorphs
• player transformation over time
• rendering text: I/you/he/she