Try   HackMD
  • Intro
    1. Game core
    • 2.1. Game loop
    • 2.2. Tiled
    • 2.3. World
      • 2.3.1. Object hierarchy
      • 2.3.2. Player
        • 2.3.2.1. State machine
        • 2.3.2.2. Cutscene state
        • 2.3.2.3. Win state
        • 2.3.2.4. Animations
        • 2.3.2.5. Tweens
      • 2.3.3. Spring
      • 2.3.4. Special levels
    • 2.4. UI
      • 2.4.1. Main menu
      • 2.4.2. Ingame settings
    1. Juiciness
    • 3.1. Post processing
    • 3.2. Screen reading shaders
    • 3.3. Particles: Water splash
    • 3.4. Camera shake
    • 3.5. Sounds
    1. Platforms
    • 4.1. Itch.io, HTML5
    • 4.2. Steam, PC
    • 4.3. Play store
    • 4.4. App store
    1. Profiling

Intro

A draft of "Fish Fight platformer book" - step by step guide of building competitive platformer game.

Game Core

wip

Game Loop

wip

Tiled

https://not-fl3.github.io/platformer-book/tiled/index.html

World

wip

Last changed by 
 
Erlend Sogge Heggen
0
170

Read more

Weird webpage generator

Product Vision https://blog.erlend.sh/weird-web-pages https://blog.erlend.sh/weird-inc Proof of Concept The primary of our first PoC is a static site export that can easily be pushed to one of the popular free host providers: https://github.com/commune-org/weird-rs/issues/3 The flow goes something like:

May 22, 2023
Open-Source Curriculum (v0.1.1)

(also ideal for viewing) In brief: A curriculum for students of 'open source' as it is practiced by open source spftware developers. Whether you’re a newcomer to open source or you’ve been involved with the practice for some time, this curriculum aims to provide a comprehensive overview of everything open source is, and aspires to be. This document aspires to become a comprehensive reading list for anyone seeking to deeply understand ‘openness’ as an ideology for knowledge work, a distributed movement, a commercial industry and more yet to come. Open Source as a subset of openness https://en.wikipedia.org/wiki/Openness

Jul 23, 2022
Bevy Editor-UI research

Target https://github.com/bevyengine/bevy/issues/254 Before we can start work on the Bevy Editor, we need a solid UI implementation. Bevy UI already has nice "flexbox" layout, and we already have a first stab at buttons and interaction events. But Bevy UI still needs a lot more experimentation if we're going to find the "right" patterns and paradigms. Editor-Ready UI has the following requirements: Embraces the Bevy architecture: Bevy ECS, Bevy Scenes, Bevy Assets, Bevy Events A Canvas-style API for drawing widgets with shapes and anti-aliased curves Define a consistent way to implement widgets A core set of widgets: buttons, inputs, resizable panels, etc Theme-ability

Oct 15, 2021
Low-poly strategy

How we can use low-poly resources as high-res greyboxes for the first 6-12 months of development. I think low-poly is a very natural starting point for a game that wants to be as modding-friendly as possible. If the average asset creator needs to create this kind of HD scene: ..then there’s gonna be a lot of people who tap out right away, because they can tell that it’ll take them too darn long to be making something of that detail. Having to make something like this is much less daunting: The simplicity of low-poly also makes it a more powerful target for novel rendering techniques. There are loads of smart ways to give low-poly a distinct, fresh look at low cost:

Mar 21, 2021
Read more from Erlend Sogge Heggen
Published on HackMD