Weissblatt Wiki - User contributions [en]

Guide:Map Design

2026-03-30T00:01:49Z

Nyamoru: /* Technical map design */

Map design or ''mapping'', is the process of creating a [[Map]] for Weissblatt. There are many things to consider when creating a Weissblatt map, so each section of this article will try to provide an overview of what's what and encourage further reading elsewhere - mapping is a broad topic.

== Creative map design ==
''Creative map design'' describes building a map in the creative abstract. This can mean either in terms of visuals as well as game design, but a lot of the skills required for this can be applied outside of Weissblatt.

=== Architecture and Aesthetics ===

=== Gameplay and Difficulty ===

== Technical map design ==
''Technical map design'' describes the process of realizing your ideas as a playable map. The tool to do so is [[BlattPlanner]] - Weissblatt's map editor (based on [https://ultimatedoombuilder.github.io/ Ultimate Doom Builder]).

If you've already started mapping and just need a quick reference for how things fit together, the following pages will have you covered:

* [[Map]]
* [[:Category:MOBJ]]
* [[:Category:Linedef type]]

[[Category:Guide]]
[[Category:TODO]]

Guide:Map Design

2026-03-29T23:56:48Z

Nyamoru: Created page with "Map design or ''mapping'', is the process of creating a Map for Weissblatt. There are many things to consider when creating a Weissblatt map, so each section of this article will try to provide an overview of what's what and encourage further reading elsewhere - mapping is a broad topic. == Creative map design == ''Creative map design'' describes building a map in the creative abstract. This can mean either in terms of visuals as well as game design, but a lot of th..."

Map

2026-03-29T23:42:46Z

Nyamoru:

Game levels in Weissblatt are commonly called '''Maps''' while the act of creating a map is called '''Mapping'''. Like with many multiplayer PC games, this terminology is inherited from [[wikipedia:Doom_(1993_video_game)|Doom]].

This article describes the technical aspect of Weissblatt's map format. If you're looking to get started building maps, visit [[Guide:Map Design]].

== Map format Basics ==
Weissblatt supports two different map formats:
# ''Legacy maps'' (sometimes called ''binary maps'') - This format is inherited from Sonic Robo Blast 2 and is generally advised against when mapping. Weissblatt will no longer develop it an thus a lot of features will be unavailable when using it.
# ''[https://doomwiki.org/wiki/UDMF UDMF] maps'', upon which Weissblatt is built. UDMF stands for '''U'''niversal '''D'''oom '''M'''ap '''F'''ormat - a text-based map description format developed by the Doom source port community.
To fully understand Weissblatt's map formats, you should understand the concepts of how (modern) Doom engines construct their maps in the abstract:

=== Sectors, Walls and Linedefs ===
In short, Doom maps are essentially two-dimensional top-down vertex structures with added properties for height and other gameplay mechanics.

''Walls'' are lines between two or more vertices on a map. Each wall can either be solid with a single texture assigned to it or it can be a two-sided ''Linedef'' seperating two sectors. Depending on the two sectors' floor and ceiling heights, each Linedef may be assigned a top, middle or bottom texture per-side. Linedefs can also be equipped a ''Type'' which can trigger various effects at runtime.

Walls can also have multiple ''flags'', which can have effects on movement and rendering such as <code>Peg Midtexture</code> or <code>Impassable</code>.

''Sectors'' are polygons made up of multiple walls through which the player can move. Sectors can be assigned

* Top and Bottom [[Flat]] [ceiling/floor texture]
* Floor and ceiling height
* Light level
* Colored lighting (depending on the map format)
* A numeric ''Tag'' (multiple for UDMF maps)
* Various unique effects, such as damage upon touch

==== Tagging ====
''Further Reading: [[:Category:Linedef Type]]''

Walls, sectors, and Things within a map can be ''tagged'' using an integer number. Depending on the sector effect and Linedef type, Sectors and Linedefs with matching tags may trigger one another, given trigger-dependent conditions, such as one or all players entering a sector or (not) having collected all [[Chakra Shards]] when doing so. Matching tags can also be used for triggers relating to Things.

==== Binary Space partitioning ====
Simply put, Doom maps are heavily preprocessed using a so-called ''node builder'' before being included in the game. A modern node builder with UDMF support is [https://doomwiki.org/wiki/ZDBSP ZDBSP] from the ZDoom source port.

Node builders implement an algorithm called ''Binary Space Partitioning'' or BSP. Through BSP, all map sectors are subdivided into convex shapes and assembled into a binary tree. The game engine can then per-frame traverse the leaves of any given branch of that tree to determine all potentially visible walls.

<more TBA>

==== Floor-over-Floor (FOF) ====
''Floor-over-Floor sectors'' or FOFs are an extension upon the original Doom format which allows for multi-floor sectors like hovering bridges. To achieve this, a separate ''control sector'' is created outside of the play area to which other host sectors are tagged. Triggered through an [[FOF Linedef Type]], the engine then uniformly applies a subdivision in between the host sector's space based on the control sector's assigned textures and flats.

==== Polyobjects ====
''Polyobjects'' are an extension to use pieces of predefined map geometry as if they were map objects. This allows for many more gameplay mechanics such as spinning geometry, sideways crushers or swinging doors.

=== Things and MOBJs ===
''Further reading: [[:Category:Thing]] | [[:Category:MOBJ]]''

''Things'' are static spawners for game objects placed within sectors. Upon map load, things are initialized and spawn their respective MOBJs. Things can also be given ''parameters'' and ''flags'', which may modify the Thing's behavior. Since Things are only initialized upon map load, this requires some gameplay design considerations when placing enemies such as [https://doomwiki.org/wiki/Monster_closet monster closets].

MOBJs are only spawned at runtime and represent game objects, such as enemies, gems or decorative sprites. MOBJs contain their own Object flags, which are distinct from Thing flags.

=== Fracunits ===
''A fracunit'' is the smallest possible distance in a map. At default scale it corresponds to one texel [pixel on a texture]. In general, Weissblatt assumes a scale of 64 Fracunits per one meter.

== UDMF Mapping ==
''[https://doomwiki.org/wiki/UDMF UDMF]'' stands for ''Universal Doom Map Format''. It is a textual map format developed for near-infinite extensibility within modern Doom engine source ports. It is not backwards compatible to older formats.

A UDMF map consists of the following lumps within a WAD or [[PK3]], :

* <code>MAPxx</code> - A simple marker lump denoting the map number. Required.
* <code>TEXTMAP</code> contains information on the map geometry (vertices, linedefs, sectors), SIDEDEFs and Things. Despite UDMF being a text format, it is not intended to be read or edited manually. Instead it should be parsed by dedicated programs such as Ultimate Zone Builder, SLADE or Weissblatt's game engine.
* <code>ZNODES</code> - BSP information generated by [https://doomwiki.org/wiki/ZDBSP ZDBSP] (as it's the only node builder with UDMF support). If missing, many Doom engines expect it to be generated on-the-fly by a ZDBSP instance built into the engine.

* <code>ENDMAP</code> - a simple marker lump. Required

=== TEXTMAP specification ===
Weissblatt supports UDMF <code>TEXTMAP</code>s of namespace <code>weissblatt</code> and <code>srb2</code>.

== Legacy Mapping ==
The Legacy map format was inherited from Sonic Robo Blast 2 and is now considered deprecated. Weissblatt does not develop it any further and merely maintains it for backwards compatibility. As such the format will be missing many features compared to Weissblatt's UDMF implementation.

Like traditional Doom maps, legacy maps are a ''binary map format'', meaning all data is encoded directly into byte structures. This brings some limitations:

# Each Sector/Linedef/Thing can only be assigned one tag
# Texture/Flat/Thing scaling is not supported
# Flat alignment/rotation is not supported
# Only 65536 tags are allowed.
# The total amount of possible walls, Linedefs, Sectors, etc. within a map may be limited.
# <TBA>

Binary maps are made up of the following lumps:

# <code>THINGS</code>
# <code>VERTEXES</code>
# <code>LINEDEFS</code>
# <code>SIDEDEFS</code>
# <code>SECTORS</code>

=== Reserved specialty tags ===
The Legacy map format does not support multitagging and is generally less flexible when it comes to tagging Things. To get around this, some Tag numbers are given special treatment:
{| class="wikitable"
|+
!Tag
!SOC/Lua Constant
!Effect
|-
|649
|<code>LE_AXE</code>
|Triggered when
|-
|650
|<code>LE_KOOPA</code>
|Triggered when <++> is defeated. Raises matching sectors' ceiling to the highest adjacent ceiling
|-
|680
|<code>LE_CAPSULE0</code>
| rowspan="3" |Triggered when a boss is defeated.
|-
|681
|<code>LE_CAPSULE1</code>
|-
|682
|<code>LE_CAPSULE2</code>
|-
|4200
|<code>LE_BRAKPLATFORM</code>
|Triggered after six hits to the alternate form of [[KOTU]].
|-
|32000
|<code>LE_TURRET</code>
|Triggered when a turret is destroyed.
|-
|65530 (-6)
|<code>LE_BRAKVILEATACK</code>
|Triggered when [[KOTU]] starts casting magic.
|-
|65531 (-5)
|<code>LE_BOSS4DROP</code>
|Triggered when <++> drops <++>
|-
|65532 (-4)
|<code>LE_BOSSDEAD</code>
|Triggered when any Boss is defeated
|-
|65533 (-3)
|<code>LE_ALLBOSSDEAD</code>
|Triggered when all Bosses are defeated
|-
|65534 (-2)
|<code>LE_PINCHPHASE</code>
|Triggered when Bosses switch into their pinch phase
|-
|65535 (-1)
|
|Affect every sector in a map
|-
|
|<code>LE_PARAMWIDTH</code>
|
|}

=== Conversion to UDMF ===
Legacy maps can be converted to UDMF maps: Simply launch the game using <code>-textmap</code> and <code>-warp <MAPNUM></code>. After you quit the game, the engine will save a UDMF conversion of your map to the file <code>TEXTMAP</code> within your game directory. You can use SLADE or Ultimate Zone Builder to recompile the newly-generated <code>TEXTMAP</code> into a proper UDMF map.
[[Category:Technology]]

Writing Wiki Pages

2026-03-29T23:29:19Z

Nyamoru:

The Weissblatt Wiki follows a holistic approach to documentation. By reading this wiki, the reader should be naturally guided to acquire a full understanding on how Weissblatt is put together, why it's done the way it is and how they can contribute.

Thus the Weissblatt Wiki serves three purposes:

# A living design document for Weissblatt.
# A teaching tool to onboard potential new contributors.
# Reference documentation for the existing aspects of Weissblatt.

What the Weissblatt Wiki is '''NOT:'''

# A repository for game files or mods.
# A discussion forum. Although MediaWiki supports discussions, off-the-cuff discussions are more suited to chat applications.

== Writing a page ==

=== Semantics ===

* Each section should have at least one paragraph. Don't just break off into pointless subsections.
* Run-on sentences are hard to read and hard to remember.
* Don't make lists with only one element.
* When your list element looks like a paragraph, split it up or don't put it in the list.
* Be strict about which words you use. Synonyms aren't fancy, they're confusing.
** When a term might be unfamiliar to a reader, ''emphasize'' it upon first use and define it early on in the page. '''Don't leave the reader guessing.'''

=== Structure ===
Page titles should capitalize the first letter of each word. "Glue words" such as ''and'' or ''of'' may be lower case.

Use redirections when dealing with aliases and pick the most general, neutral alias to write the actual content. For example, [[Dr. Roy Asura]] should redirect to [[Fishbart Toyfeller]].

Approach subjects from a lore-oriented point of view. For example [[Orbital Crystal Zone]] should be a subsection of [[Delfid]].

Each page should start with one to a couple introductory paragraphs, summarizing the topic.

=== Content guidelines ===
Each page should have a distinct, focused topic and should contain (or reference) as much info as possible within that focus. Do '''not''' make users dart across hundreds of pages just to piece together an obscure piece of lore, for example.

When mentioning a term a reader might not know about ''emphasize'' or link it upon first use in your page. For long pages, doing so upon first mention within the current section is fine too.

Think of your page as a ''reference''. Information should be easy to spot, easy to read and unambiguous.

When writing a [[Writing Wiki Pages#Writing Guides|Guide]], help the reader get stuff done. Be ''simple'', ''unambiguous'' and ''actionable''.

If you can, provide references and context. What was a character design inspired by? Don't leave these kinds of questions unanswered.

When referencing information from other places (e.g. the [https://doomwiki.org/ Doom Wiki]), link your sources clearly to encourage further reading and provide only the information which are relevant to understanding Weissblatt.
[[Category:Guide]]

Kleene Cognara

2026-03-27T12:25:56Z

Nyamoru: /* History */

[[Category:The Asura Incident]]

{{Character
|name=Kleene Cognara
|species=Beaver
|gender=Male
|affiliation=[[Volunteers]]
|color=Sangria
|birthdate=1972 WBC
|image=Kleene-Cognara.png}}

'''Kleene Cognara''' is one of the main playable characters of [[The Asura Incident]]. He's an inventive, yet practically-oriented beaver engineer who can use his self-built jet-boosted clothing to fly for short periods of time.

== Description ==
Kleene is a red beaver with an interest in engineering and a mostly utilitarian mindset. He wears mostly functional clothing, including scrappy self-built machinery with which he can fly around for short periods of time.

Although curious and open about experimenting with technology, he prefers to remain practical. He is easily annoyed by bad design and will quickly throw together scrappy prototypes to test out whatever ideas he can come up with as soon as possible. Occasionally he may ramble or scribble onto his PDA to create more ideas he can't build yet.

== History ==
From a young age Kleene was curious about mechanics and would frequently destroy or disassemble toys to figure out how they work. This fascination led him to pursue mechanical engineering, driven by a dream of one day understanding the unconventional mechanics behind toys built and designed by [[Patsy Toyfeller]]. His studies led him to befriend [[Babel Memto]].

Sexually frustrated at the age of 16, Kleene built [[Elise Cantor]] during a night of black-out-drunk garage hacking. Ever since building Elise, Kleene claims to be unable to replicate her, since he cannot recall how he built her the first time. After Elise helped recover Kleene's mental state and developed her own autonomy, he let her go out of a growing sense of responsibility, although both still keep each other company.

During the Asura Incident, as he was testing an ancient flight machine design on [[Stella Mountain]] alongside Elise and Babel as the three of them were struck down by [[Dr. Roy Asura|Dr. Asura]], whom had just escaped the destruction of [[Delfid]].

== Gallery ==
[[File:Kleene refsheet.png|thumb|Model sheet for Kleene Cognara]]
[[File:Kleene Cognara with cube.png.png|thumb|Four-Panel concept comic showcasing Kleene's character]]
[[File:Elise and Kleene.png|thumb|Elise and Kleene flying together. Used by the character selection option for Elise & Kleene]]

== Trivia ==
Alongside [[Elise Cantor]] and [[Babel Memto]], Kleene was inspired by [[wikipedia:Muses|the three (original) muses from greek mythology]], with Kleene representing the scientific aspect.

Kleene's first name is a reference to [[wikipedia:Stephen_Cole_Kleene|Stephen Cole Kleene]], an american mathematician known for inventing [[wikipedia:Regular_expression|regular expressions]].

Kleene's character was mainly inspired by maker and hacker culture, in particular the [https://medium.com/@bre/the-cult-of-done-manifesto-724ca1c2ff13 Cult of Done manifesto]

Main Page

2026-03-19T20:20:49Z

Nyamoru:

[[File:Weissblatt lettering (800px).png|alt=Weissblatt Logo|center]]
Welcome to the official Wiki for '''Weissblatt - The Asura Incident'''!

== Categories ==
If you don't know where to start reading, check out the categories below:

=== Game-related categories ===
* [[:Category:Character]] - Playable and Lore characters from Weissblatt
* [[:Category:Guide]] - Read these to get started developing Weissblatt (mods)
** [[:Category:Technology]] - References for Weissblatt's engine and other related projects
* [[:Category:Location]] - Locations on planet Weissblatt with an emphasis on lore. [[Map|Game maps]], are contained within each respective location's page.
* [[:Category:The Asura Incident]]
* [[:Category:Worldbuilding]] - Minor lore-related tidbits that don't fit anywhere else.

=== Site-internal categories ===

* [[:Category:Research and Development]] - Technical and/or creative knowledge gathered during development
* [[:Category:TODO]] - Stub pages

Making Music

2026-03-19T20:17:49Z

Nyamoru: Nyamoru moved page Making Music to Guide: Making Music: Misspelled title

#REDIRECT [[Guide: Making Music]]

Guide: Making Music

2026-03-19T20:17:49Z

Nyamoru: Nyamoru moved page Making Music to Guide: Making Music: Misspelled title

[[Category:Guide]]
[[Category:TODO]]

Guide: Making Music

2026-03-19T20:16:21Z

Nyamoru: Created page with "Category:Guide Category:TODO"

[[Category:Guide]]
[[Category:TODO]]

Fracunit

2026-03-19T20:02:15Z

Nyamoru: Redirected page to Map#Fracunits

#REDIRECT [[Map#Fracunits]]
[[Category:Technology]]

Map

2026-03-19T20:00:03Z

Nyamoru:

Game levels in Weissblatt are commonly called '''Maps''' while the act of creating a map is called '''Mapping'''. Like with many multiplayer PC games, this terminology is inherited from [[wikipedia:Doom_(1993_video_game)|Doom]].

Weissblatt supports two different map formats:

# ''Legacy maps'' (sometimes called ''binary maps'') - This format is inherited from Sonic Robo Blast 2 and is generally advised against when mapping.
# ''[https://doomwiki.org/wiki/UDMF UDMF] maps'', upon which Weissblatt is built. UDMF stands for '''U'''niversal '''D'''oom '''M'''ap '''F'''ormat - a text-based map description format developed by the Doom source port community.

== Map format Basics ==
To fully understand mapping, you should understand the concepts of how (modern) Doom engines construct their maps in the abstract:

=== Sectors, Walls and Linedefs ===
In short, Doom maps are essentially two-dimensional top-down vertex structures with added properties for height and other gameplay mechanics.

''Walls'' are lines between two or more vertices on a map. Each wall can either be solid with a single texture assigned to it or it can be a two-sided ''Linedef'' seperating two sectors. Depending on the two sectors' floor and ceiling heights, each Linedef may be assigned a top, middle or bottom texture per-side. Linedefs can also be equipped a ''Type'' which can trigger various effects at runtime.

Walls can also have multiple ''flags'', which can have effects on movement and rendering such as <code>Peg Midtexture</code> or <code>Impassable</code>.

''Sectors'' are polygons made up of multiple walls through which the player can move. Sectors can be assigned

* Top and Bottom [[Flat]] [ceiling/floor texture]
* Floor and ceiling height
* Light level
* Colored lighting (depending on the map format)
* A numeric ''Tag'' (multiple for UDMF maps)
* Various unique effects, such as damage upon touch

==== Tagging ====
''Further Reading: [[:Category:Linedef Type]]''

Walls, sectors, and Things within a map can be ''tagged'' using an integer number. Depending on the sector effect and Linedef type, Sectors and Linedefs with matching tags may trigger one another, given trigger-dependent conditions, such as one or all players entering a sector or (not) having collected all [[Chakra Shards]] when doing so. Matching tags can also be used for triggers relating to Things.

==== Binary Space partitioning ====
Simply put, Doom maps are heavily preprocessed using a so-called ''node builder'' before being included in the game. A modern node builder with UDMF support is [https://doomwiki.org/wiki/ZDBSP ZDBSP] from the ZDoom source port.

Node builders implement an algorithm called ''Binary Space Partitioning'' or BSP. Through BSP, all map sectors are subdivided into convex shapes and assembled into a binary tree. The game engine can then per-frame traverse the leaves of any given branch of that tree to determine all potentially visible walls.

<more TBA>

==== Floor-over-Floor (FOF) ====
''Floor-over-Floor sectors'' or FOFs are an extension upon the original Doom format which allows for multi-floor sectors like hovering bridges. To achieve this, a separate ''control sector'' is created outside of the play area to which other host sectors are tagged. Triggered through an [[FOF Linedef Type]], the engine then uniformly applies a subdivision in between the host sector's space based on the control sector's assigned textures and flats.

==== Polyobjects ====
''Polyobjects'' are an extension to use pieces of predefined map geometry as if they were map objects. This allows for many more gameplay mechanics such as spinning geometry, sideways crushers or swinging doors.

=== Things and MOBJs ===
''Further reading: [[:Category:Thing]] | [[:Category:MOBJ]]''

''Things'' are static spawners for game objects placed within sectors. Upon map load, things are initialized and spawn their respective MOBJs. Things can also be given ''parameters'' and ''flags'', which may modify the Thing's behavior. Since Things are only initialized upon map load, this requires some gameplay design considerations when placing enemies such as [https://doomwiki.org/wiki/Monster_closet monster closets].

MOBJs are only spawned at runtime and represent game objects, such as enemies, gems or decorative sprites. MOBJs contain their own Object flags, which are distinct from Thing flags.

=== Fracunits ===
''A fracunit'' is the smallest possible distance in a map. At default scale it corresponds to one texel [pixel on a texture]. In general, Weissblatt assumes a scale of 64 Fracunits per one meter.

== UDMF Mapping ==
''[https://doomwiki.org/wiki/UDMF UDMF]'' stands for ''Universal Doom Map Format''. It is a textual map format developed for near-infinite extensibility within modern Doom engine source ports. It is not backwards compatible to older formats.

A UDMF map consists of the following lumps within a WAD or [[PK3]], :

* <code>MAPxx</code> - A simple marker lump denoting the map number. Required.
* <code>TEXTMAP</code> contains information on the map geometry (vertices, linedefs, sectors), SIDEDEFs and Things. Despite UDMF being a text format, it is not intended to be read or edited manually. Instead it should be parsed by dedicated programs such as Ultimate Zone Builder, SLADE or Weissblatt's game engine.
* <code>ZNODES</code> - BSP information generated by [https://doomwiki.org/wiki/ZDBSP ZDBSP] (as it's the only node builder with UDMF support). If missing, many Doom engines expect it to be generated on-the-fly by a ZDBSP instance built into the engine.

* <code>ENDMAP</code> - a simple marker lump. Required

=== TEXTMAP specification ===
Weissblatt supports UDMF <code>TEXTMAP</code>s of namespace <code>weissblatt</code> and <code>srb2</code>.

== Legacy Mapping ==
The Legacy map format was inherited from Sonic Robo Blast 2 and is now considered deprecated. Weissblatt does not develop it any further and merely maintains it for backwards compatibility. As such the format will be missing many features compared to Weissblatt's UDMF implementation.

Like traditional Doom maps, legacy maps are a ''binary map format'', meaning all data is encoded directly into byte structures. This brings some limitations:

# Each Sector/Linedef/Thing can only be assigned one tag
# Texture/Flat/Thing scaling is not supported
# Flat alignment/rotation is not supported
# Only 65536 tags are allowed.
# The total amount of possible walls, Linedefs, Sectors, etc. within a map may be limited.
# <TBA>

Binary maps are made up of the following lumps:

# <code>THINGS</code>
# <code>VERTEXES</code>
# <code>LINEDEFS</code>
# <code>SIDEDEFS</code>
# <code>SECTORS</code>

=== Reserved specialty tags ===
The Legacy map format does not support multitagging and is generally less flexible when it comes to tagging Things. To get around this, some Tag numbers are given special treatment:
{| class="wikitable"
|+
!Tag
!SOC/Lua Constant
!Effect
|-
|649
|<code>LE_AXE</code>
|Triggered when
|-
|650
|<code>LE_KOOPA</code>
|Triggered when <++> is defeated. Raises matching sectors' ceiling to the highest adjacent ceiling
|-
|680
|<code>LE_CAPSULE0</code>
| rowspan="3" |Triggered when a boss is defeated.
|-
|681
|<code>LE_CAPSULE1</code>
|-
|682
|<code>LE_CAPSULE2</code>
|-
|4200
|<code>LE_BRAKPLATFORM</code>
|Triggered after six hits to the alternate form of [[KOTU]].
|-
|32000
|<code>LE_TURRET</code>
|Triggered when a turret is destroyed.
|-
|65530 (-6)
|<code>LE_BRAKVILEATACK</code>
|Triggered when [[KOTU]] starts casting magic.
|-
|65531 (-5)
|<code>LE_BOSS4DROP</code>
|Triggered when <++> drops <++>
|-
|65532 (-4)
|<code>LE_BOSSDEAD</code>
|Triggered when any Boss is defeated
|-
|65533 (-3)
|<code>LE_ALLBOSSDEAD</code>
|Triggered when all Bosses are defeated
|-
|65534 (-2)
|<code>LE_PINCHPHASE</code>
|Triggered when Bosses switch into their pinch phase
|-
|65535 (-1)
|
|Affect every sector in a map
|-
|
|<code>LE_PARAMWIDTH</code>
|
|}

=== Conversion to UDMF ===
Legacy maps can be converted to UDMF maps: Simply launch the game using <code>-textmap</code> and <code>-warp <MAPNUM></code>. After you quit the game, the engine will save a UDMF conversion of your map to the file <code>TEXTMAP</code> within your game directory. You can use SLADE or Ultimate Zone Builder to recompile the newly-generated <code>TEXTMAP</code> into a proper UDMF map.
[[Category:Technology]]

PK3

2026-03-19T19:46:31Z

Nyamoru:

''PK3'' is an archive format first used in [[wikipedia:Quake_III_Arena|Quake III Arena]] and later adopted by many Doom source ports[https://doomwiki.org/wiki/PK3]. For Weissblatt, it poses a more modern, more flexible alternative to [https://doomwiki.org/wiki/WAD WAD].

== Building PK3s ==
PK3 files are actually just [[wikipedia:ZIP_(file_format)|ZIP files]], so theoretically any compression program can be used to create PK3 packages. There are however some specialty tools to make building Weissblatt (addon) PK3s easier:

In general, we recommend testing small changes first using SLADE before translating the final result into a PK3Make structure.

=== Automated building using PK3Make ===
[https://github.com/liquidunderground/pk3make PK3Make] is a specialty tool developed for building complex PK3 projects, such as Weissblatt. It can automatically build complex PK3 files with byte-for-byte determinism using a single command:
user@devdir$ pk3make

==== Writing PK3Makefiles ====
PK3Make's build behavior is determined by a configuration file called a <code>PK3Makefile</code>. The exact syntax and options for writing PK3Makefiles may vary by version, but in general PK3Make works in three steps:
Source files --[build]--> Engine-friendly build files --[pack]--> Finished PK3 file
During these steps, PK3Make will attempt to find files within the source/build files and mirror the required file tree structure in the following build step.

For the sake of safe backups, you should try to keep your project's assets as well as it's PK3Makefile under version control, for example using [https://git-scm.com/ Git].

=== Manual test using SLADE ===
[https://slade.mancubus.net/ SLADE] is a tried and time-tested tool for building Doom mods. It's a graphical WAD/PK3 editor that allows manually inspecting, building and debugging add-ons.

'''Note:''' SLADE's internal [[Picture Format|Picture]] converter is not byte-for-byte compatible with that of PK3Make. This is due to unused padding bytes within the Picture format specification being handled differently. Expect different hash values when comparing a PK3 generated by SLADE to one made using PK3Make. This has no effect on engine-behavior regarding Pictures.
== Directory structure ==
=== Directory structure ===
Weissblatt's directory structure is based on the ZDoom PK3 structure. The table below explains each directory expected by Weissblatt's engine, it's purpose and it's typically expected file format:
{| class="wikitable"
|+Weissblatt PK3 structure
!Directory
!Contains
!File Format
|-
|<code>Characters/</code>
|Images
|S_SKIN (Plain Text)
[[Doom Picture|Picture]]
|-
|<code>Fades/</code>
|[[Screen Fade|Screen Fades]]
|Fade ([[Flat#Fade|Flat]])
|-
|<code>Flats/</code>
|Floor textures
|[[Flat|Flats]]
|-
|<code>Lua/</code>
|Lua scripts
|<code>.lua</code> (Plain Text)
|-
|<code>Maps/</code>
|Maps
|WAD
|-
|<code>Models/</code>
|[[3D Model|3D Models]]
|[[3D Model#MD3|MD3]]
PNG (Textures)
|-
|<code>Music/</code>
|Music files
|OGG
WAV
(General) MIDI
MOD
XM
S3M
IT
|-
|<code>Patches/</code>
|Patch graphics
|[[Doom Picture|Picture]]
|-
|<code>SOC/</code>
|Configuration
|SOC (Plain Text)
|-
|<code>Sounds/</code>
|Sounds
|OGG
WAV
|-
|<code>Sprites</code>
|Sprite graphics
|[[Doom Picture|Picture]]
|-
|<code>Textures/</code>
|Wall textures
|[[Doom Picture|Picture]]
|}
There are also additional files which are also expected, but typically stored in the PK3 root directory:
{| class="wikitable"
|+Special lumps
!File
!Type
|-
|<code>ANIMDEFS</code>
|[[ANIMDEFS]]
|-
|<code>COLORMAP</code>
<code>WATERMAP</code>
<code>CLMxxxx</code>
|[[Color Palette#COLORMAP|COLORMAP]]
|-
|<code>PLAYPAL</code>
<code>PALxxxx</code>
|[[Color Palette|Color palette]]
|-
|<code>TEXTURES</code>
|[[TEXTUREDEF]]
|-
|<code>TRANSxx</code>
|[[Color Palette#TINTTAB|TINTTAB]]
|}
[[Category:Guide]]
[[Category:Technology]]

Category:Guide

2026-03-19T18:52:13Z

Nyamoru: /* Making PK3 packages */

Here you can find guides on all sorts of things related to modding and developing Weissblatt. Below you can also find a list of recommended tools to help you get started.

== Development Tools ==
If you're looking for tools to get started working on Weissblatt, here's what we use to make the game. Keep in mind there are many alternatives you can use, although we prefer to keep things accessible by sticking to FLOSS software where possible.

=== Making PK3 packages ===
Full article: [[PK3]]

* [https://github.com/liquidunderground/pk3make PK3Make] to compile PK3 packages for larger projects, such as Weissblatt itself
* [https://slade.mancubus.net/ SLADE] to manually inspect PK3 packages

=== Programming ===
We recommend using a unix-like system to develop on, especially Linux. However, to ease your decision, here's our recommendation for which Linux distribution you may wanna pick:

* [https://www.linuxmint.com/ Linux Mint] for beginners. If you never used Linux before, use this.
* [https://archlinux.org/ Arch Linux] for advanced hackers
* [https://www.debian.org/ Debian GNU/Linux] for experienced greybeards

==== Tools for Linux/macOS/other unix-like platforms ====

* [https://www.vim.org/ Vim] to edit text on
* [https://vscodium.com/ VSCodium] (FLOSS fork of Microsoft Visual Studio Code)
* [https://gcc.gnu.org/ GCC] to compile C code
* [https://cmake.org/ CMake] to manage dependencies and generate build files for your system.

==== Tools for Windows ====

* [https://visualstudio.microsoft.com Microsoft Visual Studio] (full IDE)
* [https://code.visualstudio.com/download Microsoft Visual Studio Code] (text editor)

* [https://notepad-plus-plus.org/downloads/ Notepad++] to edit text
* [https://visualstudio.microsoft.com/en/downloads/ Microsoft MSVC compiler] to compile C code
* [https://cmake.org/ CMake] to manage dependencies and generate build files for your system.

=== Pixel art and animation ===

* [https://www.aseprite.org/ Aseprite] (paid in pre-compiled form)
* [https://libresprite.github.io/#!/ Libresprite]

=== 3D modeling and animation ===

* [https://www.blender.org/ Blender]

=== Audio ===

==== Digital Music ====

* [https://tildearrow.org/furnace/ Furnace]
* [https://openmpt.org/ OpenMPT]
* [https://ardour.org/ Ardour]
* [https://lmms.io/ LMMS]

==== MIDI Music ====

* [https://www.rosegardenmusic.com/ Rosegarden] for sequencing MIDI music
* [https://www.fluidsynth.org/ Fluidsynth] for engine-accurate MIDI playback (seriously - the engine runs on it)

==== Sound Effects, etc. ====

* [https://www.drpetter.se/project_sfxr.html DrPetter's sfxr] (or [https://sfxr.me/ jsfxr]) for making sound effects
* [https://www.audacityteam.org/download/ Audacity] for mixing

Map

2026-03-05T00:38:24Z

Nyamoru: Additional details on Tagging and Things

Game levels in Weissblatt are commonly called '''Maps''' while the act of creating a map is called '''Mapping'''. Like with many multiplayer PC games, this terminology is inherited from [[wikipedia:Doom_(1993_video_game)|Doom]].

Weissblatt supports two different map formats:

# ''Legacy maps'' (sometimes called ''binary maps'') - This format is inherited from Sonic Robo Blast 2 and is generally advised against when mapping.
# ''[https://doomwiki.org/wiki/UDMF UDMF] maps'', upon which Weissblatt is built. UDMF stands for '''U'''niversal '''D'''oom '''M'''ap '''F'''ormat - a text-based map description format developed by the Doom source port community.

== Map format Basics ==
To fully understand mapping, you should understand the concepts of how (modern) Doom engines construct their maps in the abstract:

=== Sectors, Walls and Linedefs ===
In short, Doom maps are essentially two-dimensional top-down vertex structures with added properties for height and other gameplay mechanics.

''Walls'' are lines between two or more vertices on a map. Each wall can either be solid with a single texture assigned to it or it can be a two-sided ''Linedef'' seperating two sectors. Depending on the two sectors' floor and ceiling heights, each Linedef may be assigned a top, middle or bottom texture per-side. Linedefs can also be equipped a ''Type'' which can trigger various effects at runtime.

Walls can also have multiple ''flags'', which can have effects on movement and rendering such as <code>Peg Midtexture</code> or <code>Impassable</code>.

''Sectors'' are polygons made up of multiple walls through which the player can move. Sectors can be assigned

* Top and Bottom [[Flat]] [ceiling/floor texture]
* Floor and ceiling height
* Light level
* Colored lighting (depending on the map format)
* A numeric ''Tag'' (multiple for UDMF maps)
* Various unique effects, such as damage upon touch

==== Tagging ====
''Further Reading: [[:Category:Linedef Type]]''

Walls, sectors, and Things within a map can be ''tagged'' using an integer number. Depending on the sector effect and Linedef type, Sectors and Linedefs with matching tags may trigger one another, given trigger-dependent conditions, such as one or all players entering a sector or (not) having collected all [[Chakra Shards]] when doing so. Matching tags can also be used for triggers relating to Things.

==== Binary Space partitioning ====
Simply put, Doom maps are heavily preprocessed using a so-called ''node builder'' before being included in the game. A modern node builder with UDMF support is [https://doomwiki.org/wiki/ZDBSP ZDBSP] from the ZDoom source port.

Node builders implement an algorithm called ''Binary Space Partitioning'' or BSP. Through BSP, all map sectors are subdivided into convex shapes and assembled into a binary tree. The game engine can then per-frame traverse the leaves of any given branch of that tree to determine all potentially visible walls.

<more TBA>

==== Floor-over-Floor (FOF) ====
''Floor-over-Floor sectors'' or FOFs are an extension upon the original Doom format which allows for multi-floor sectors like hovering bridges. To achieve this, a separate ''control sector'' is created outside of the play area to which other host sectors are tagged. Triggered through an [[FOF Linedef Type]], the engine then uniformly applies a subdivision in between the host sector's space based on the control sector's assigned textures and flats.

==== Polyobjects ====
''Polyobjects'' are an extension to use pieces of predefined map geometry as if they were map objects. This allows for many more gameplay mechanics such as spinning geometry, sideways crushers or swinging doors.

=== Things and MOBJs ===
''Further reading: [[:Category:Thing]] | [[:Category:MOBJ]]''

''Things'' are static spawners for game objects placed within sectors. Upon map load, things are initialized and spawn their respective MOBJs. Things can also be given ''parameters'' and ''flags'', which may modify the Thing's behavior. Since Things are only initialized upon map load, this requires some gameplay design considerations when placing enemies such as [https://doomwiki.org/wiki/Monster_closet monster closets].

MOBJs are only spawned at runtime and represent game objects, such as enemies, gems or decorative sprites. MOBJs contain their own Object flags, which are distinct from Thing flags.

== UDMF Mapping ==
''[https://doomwiki.org/wiki/UDMF UDMF]'' stands for ''Universal Doom Map Format''. It is a textual map format developed for near-infinite extensibility within modern Doom engine source ports. It is not backwards compatible to older formats.

A UDMF map consists of the following lumps within a WAD or [[PK3]], :

* <code>MAPxx</code> - A simple marker lump denoting the map number. Required.
* <code>TEXTMAP</code> contains information on the map geometry (vertices, linedefs, sectors), SIDEDEFs and Things. Despite UDMF being a text format, it is not intended to be read or edited manually. Instead it should be parsed by dedicated programs such as Ultimate Zone Builder, SLADE or Weissblatt's game engine.
* <code>ZNODES</code> - BSP information generated by [https://doomwiki.org/wiki/ZDBSP ZDBSP] (as it's the only node builder with UDMF support). If missing, many Doom engines expect it to be generated on-the-fly by a ZDBSP instance built into the engine.

* <code>ENDMAP</code> - a simple marker lump. Required

=== TEXTMAP specification ===
Weissblatt supports UDMF <code>TEXTMAP</code>s of namespace <code>weissblatt</code> and <code>srb2</code>.

== Legacy Mapping ==
The Legacy map format was inherited from Sonic Robo Blast 2 and is now considered deprecated. Weissblatt does not develop it any further and merely maintains it for backwards compatibility. As such the format will be missing many features compared to Weissblatt's UDMF implementation.

Like traditional Doom maps, legacy maps are a ''binary map format'', meaning all data is encoded directly into byte structures. This brings some limitations:

# Each Sector/Linedef/Thing can only be assigned one tag
# Texture/Flat/Thing scaling is not supported
# Flat alignment/rotation is not supported
# Only 65536 tags are allowed.
# The total amount of possible walls, Linedefs, Sectors, etc. within a map may be limited.
# <TBA>

Binary maps are made up of the following lumps:

# <code>THINGS</code>
# <code>VERTEXES</code>
# <code>LINEDEFS</code>
# <code>SIDEDEFS</code>
# <code>SECTORS</code>

=== Reserved specialty tags ===
The Legacy map format does not support multitagging and is generally less flexible when it comes to tagging Things. To get around this, some Tag numbers are given special treatment:
{| class="wikitable"
|+
!Tag
!SOC/Lua Constant
!Effect
|-
|649
|<code>LE_AXE</code>
|Triggered when
|-
|650
|<code>LE_KOOPA</code>
|Triggered when <++> is defeated. Raises matching sectors' ceiling to the highest adjacent ceiling
|-
|680
|<code>LE_CAPSULE0</code>
| rowspan="3" |Triggered when a boss is defeated.
|-
|681
|<code>LE_CAPSULE1</code>
|-
|682
|<code>LE_CAPSULE2</code>
|-
|4200
|<code>LE_BRAKPLATFORM</code>
|Triggered after six hits to the alternate form of [[KOTU]].
|-
|32000
|<code>LE_TURRET</code>
|Triggered when a turret is destroyed.
|-
|65530 (-6)
|<code>LE_BRAKVILEATACK</code>
|Triggered when [[KOTU]] starts casting magic.
|-
|65531 (-5)
|<code>LE_BOSS4DROP</code>
|Triggered when <++> drops <++>
|-
|65532 (-4)
|<code>LE_BOSSDEAD</code>
|Triggered when any Boss is defeated
|-
|65533 (-3)
|<code>LE_ALLBOSSDEAD</code>
|Triggered when all Bosses are defeated
|-
|65534 (-2)
|<code>LE_PINCHPHASE</code>
|Triggered when Bosses switch into their pinch phase
|-
|65535 (-1)
|
|Affect every sector in a map
|-
|
|<code>LE_PARAMWIDTH</code>
|
|}

=== Conversion to UDMF ===
Legacy maps can be converted to UDMF maps: Simply launch the game using <code>-textmap</code> and <code>-warp <MAPNUM></code>. After you quit the game, the engine will save a UDMF conversion of your map to the file <code>TEXTMAP</code> within your game directory. You can use SLADE or Ultimate Zone Builder to recompile the newly-generated <code>TEXTMAP</code> into a proper UDMF map.
[[Category:Technology]]

Map

2026-03-05T00:33:24Z

Nyamoru: /* Sectors, Walls and Linedefs */

Game levels in Weissblatt are commonly called '''Maps''' while the act of creating a map is called '''Mapping'''. Like with many multiplayer PC games, this terminology is inherited from [[wikipedia:Doom_(1993_video_game)|Doom]].

Weissblatt supports two different map formats:

# ''Legacy maps'' (sometimes called ''binary maps'') - This format is inherited from Sonic Robo Blast 2 and is generally advised against when mapping.
# ''[https://doomwiki.org/wiki/UDMF UDMF] maps'', upon which Weissblatt is built. UDMF stands for '''U'''niversal '''D'''oom '''M'''ap '''F'''ormat - a text-based map description format developed by the Doom source port community.

== Map format Basics ==
To fully understand mapping, you should understand the concepts of how (modern) Doom engines construct their maps in the abstract:

=== Sectors, Walls and Linedefs ===
In short, Doom maps are essentially two-dimensional top-down vertex structures with added properties for height and other gameplay mechanics.

''Walls'' are lines between two or more vertices on a map. Each wall can either be solid with a single texture assigned to it or it can be a two-sided ''Linedef'' seperating two sectors. Depending on the two sectors' floor and ceiling heights, each Linedef may be assigned a top, middle or bottom texture per-side. Linedefs can also be equipped a ''Type'' which can trigger various effects at runtime.

Walls can also have multiple ''flags'', which can have effects on movement and rendering such as <code>Peg Midtexture</code> or <code>Impassable</code>.

''Sectors'' are polygons made up of multiple walls through which the player can move. Sectors can be assigned

* Top and Bottom [[Flat]] [ceiling/floor texture]
* Floor and ceiling height
* Light level
* Colored lighting (depending on the map format)
* A numeric ''Tag'' (multiple for UDMF maps)
* Various unique effects, such as damage upon touch

==== Tagging ====
Walls, sectors, and Things within a map can be ''tagged'' using an integer number. Depending on the sector effect and Linedef type, Sectors and Linedefs with matching tags may trigger one another, given trigger-dependent conditions, such as one or all players entering a sector or (not) having collected all [[Chakra Shards]] when doing so. Matching tags can also be used for triggers relating to Things.

==== Binary Space partitioning ====
Simply put, Doom maps are heavily preprocessed using a so-called ''node builder'' before being included in the game. A modern node builder with UDMF support is [https://doomwiki.org/wiki/ZDBSP ZDBSP] from the ZDoom source port.

Node builders implement an algorithm called ''Binary Space Partitioning'' or BSP. Through BSP, all map sectors are subdivided into convex shapes and assembled into a binary tree. The game engine can then per-frame traverse the leaves of any given branch of that tree to determine all potentially visible walls.

<more TBA>

==== Floor-over-Floor (FOF) ====
''Floor-over-Floor sectors'' or FOFs are an extension upon the original Doom format which allows for multi-floor sectors like hovering bridges. To achieve this, a separate ''control sector'' is created outside of the play area to which other host sectors are tagged. Triggered through an [[FOF Linedef Type]], the engine then uniformly applies a subdivision in between the host sector's space based on the control sector's assigned textures and flats.

==== Polyobjects ====
''Polyobjects'' are an extension to use pieces of predefined map geometry as if they were map objects. This allows for many more gameplay mechanics such as spinning geometry, sideways crushers or swinging doors.

=== Things and MOBJs ===
''Full page: [[:Category:MOBJ]]''

''Things'' are static spawners for game objects placed within sectors. Upon map load, things are initialized and spawn their respective MOBJs. Things can also be given ''parameters'' and ''flags'', which may modify the Thing's behavior. Since Things are only initialized upon map load, this requires some gameplay design considerations when placing enemies such as [https://doomwiki.org/wiki/Monster_closet monster closets].

MOBJs are only spawned at runtime and represent game objects, such as enemies, gems or decorative sprites. MOBJs contain their own Object flags, which are distinct from Thing flags.

== UDMF Mapping ==
''[https://doomwiki.org/wiki/UDMF UDMF]'' stands for ''Universal Doom Map Format''. It is a textual map format developed for near-infinite extensibility within modern Doom engine source ports. It is not backwards compatible to older formats.

A UDMF map consists of the following lumps within a WAD or [[PK3]], :

* <code>MAPxx</code> - A simple marker lump denoting the map number. Required.
* <code>TEXTMAP</code> contains information on the map geometry (vertices, linedefs, sectors), SIDEDEFs and Things. Despite UDMF being a text format, it is not intended to be read or edited manually. Instead it should be parsed by dedicated programs such as Ultimate Zone Builder, SLADE or Weissblatt's game engine.
* <code>ZNODES</code> - BSP information generated by [https://doomwiki.org/wiki/ZDBSP ZDBSP] (as it's the only node builder with UDMF support). If missing, many Doom engines expect it to be generated on-the-fly by a ZDBSP instance built into the engine.

* <code>ENDMAP</code> - a simple marker lump. Required

=== TEXTMAP specification ===
Weissblatt supports UDMF <code>TEXTMAP</code>s of namespace <code>weissblatt</code> and <code>srb2</code>.

== Legacy Mapping ==
The Legacy map format was inherited from Sonic Robo Blast 2 and is now considered deprecated. Weissblatt does not develop it any further and merely maintains it for backwards compatibility. As such the format will be missing many features compared to Weissblatt's UDMF implementation.

Like traditional Doom maps, legacy maps are a ''binary map format'', meaning all data is encoded directly into byte structures. This brings some limitations:

# Each Sector/Linedef/Thing can only be assigned one tag
# Texture/Flat/Thing scaling is not supported
# Flat alignment/rotation is not supported
# Only 65536 tags are allowed.
# The total amount of possible walls, Linedefs, Sectors, etc. within a map may be limited.
# <TBA>

Binary maps are made up of the following lumps:

# <code>THINGS</code>
# <code>VERTEXES</code>
# <code>LINEDEFS</code>
# <code>SIDEDEFS</code>
# <code>SECTORS</code>

=== Reserved specialty tags ===
The Legacy map format does not support multitagging and is generally less flexible when it comes to tagging Things. To get around this, some Tag numbers are given special treatment:
{| class="wikitable"
|+
!Tag
!SOC/Lua Constant
!Effect
|-
|649
|<code>LE_AXE</code>
|Triggered when
|-
|650
|<code>LE_KOOPA</code>
|Triggered when <++> is defeated. Raises matching sectors' ceiling to the highest adjacent ceiling
|-
|680
|<code>LE_CAPSULE0</code>
| rowspan="3" |Triggered when a boss is defeated.
|-
|681
|<code>LE_CAPSULE1</code>
|-
|682
|<code>LE_CAPSULE2</code>
|-
|4200
|<code>LE_BRAKPLATFORM</code>
|Triggered after six hits to the alternate form of [[KOTU]].
|-
|32000
|<code>LE_TURRET</code>
|Triggered when a turret is destroyed.
|-
|65530 (-6)
|<code>LE_BRAKVILEATACK</code>
|Triggered when [[KOTU]] starts casting magic.
|-
|65531 (-5)
|<code>LE_BOSS4DROP</code>
|Triggered when <++> drops <++>
|-
|65532 (-4)
|<code>LE_BOSSDEAD</code>
|Triggered when any Boss is defeated
|-
|65533 (-3)
|<code>LE_ALLBOSSDEAD</code>
|Triggered when all Bosses are defeated
|-
|65534 (-2)
|<code>LE_PINCHPHASE</code>
|Triggered when Bosses switch into their pinch phase
|-
|65535 (-1)
|
|Affect every sector in a map
|-
|
|<code>LE_PARAMWIDTH</code>
|
|}

=== Conversion to UDMF ===
Legacy maps can be converted to UDMF maps: Simply launch the game using <code>-textmap</code> and <code>-warp <MAPNUM></code>. After you quit the game, the engine will save a UDMF conversion of your map to the file <code>TEXTMAP</code> within your game directory. You can use SLADE or Ultimate Zone Builder to recompile the newly-generated <code>TEXTMAP</code> into a proper UDMF map.
[[Category:Technology]]

Map

2026-03-05T00:29:50Z

Nyamoru: UDMF description

Game levels in Weissblatt are commonly called '''Maps''' while the act of creating a map is called '''Mapping'''. Like with many multiplayer PC games, this terminology is inherited from [[wikipedia:Doom_(1993_video_game)|Doom]].

Weissblatt supports two different map formats:

# ''Legacy maps'' (sometimes called ''binary maps'') - This format is inherited from Sonic Robo Blast 2 and is generally advised against when mapping.
# ''[https://doomwiki.org/wiki/UDMF UDMF] maps'', upon which Weissblatt is built. UDMF stands for '''U'''niversal '''D'''oom '''M'''ap '''F'''ormat - a text-based map description format developed by the Doom source port community.

== Map format Basics ==
To fully understand mapping, you should understand the concepts of how (modern) Doom engines construct their maps in the abstract:

=== Sectors, Walls and Linedefs ===
In short, Doom maps are essentially two-dimensional top-down vertex structures with added properties for height and other gameplay mechanics.

''Walls'' are lines between two or more vertices on a map. Each wall can either be solid with a single texture assigned to it or it can be a two-sided ''Linedef'' seperating two sectors. Depending on the two sectors' floor and ceiling heights, each Linedef may be assigned a top, middle or bottom texture per-side. Linedefs can also be equipped a ''Type'' which can trigger various effects at runtime.

Walls can also have multiple ''flags'', which can have effects on movement and rendering such as <code>Peg Midtexture</code> or <code>Impassable</code>.

''Sectors'' are polygons made up of multiple walls through which the player can move. Sectors can be assigned

* Top and Bottom [[Flat]]
* Floor and ceiling height
* Light level
* Colored lighting (depending on the map format)
* One or multiple ''Tags''
* Various unique effects, such as damage upon touch

==== Tagging ====
Walls, sectors, and Things within a map can be ''tagged'' using an integer number. Depending on the sector effect and Linedef type, Sectors and Linedefs with matching tags may trigger one another, given trigger-dependent conditions, such as one or all players entering a sector or (not) having collected all [[Chakra Shards]] when doing so. Matching tags can also be used for triggers relating to Things.

==== Binary Space partitioning ====
Simply put, Doom maps are heavily preprocessed using a so-called ''node builder'' before being included in the game. A modern node builder with UDMF support is [https://doomwiki.org/wiki/ZDBSP ZDBSP] from the ZDoom source port.

Node builders implement an algorithm called ''Binary Space Partitioning'' or BSP. Through BSP, all map sectors are subdivided into convex shapes and assembled into a binary tree. The game engine can then per-frame traverse the leaves of any given branch of that tree to determine all potentially visible walls.

<more TBA>

==== Floor-over-Floor (FOF) ====
''Floor-over-Floor sectors'' or FOFs are an extension upon the original Doom format which allows for multi-floor sectors like hovering bridges. To achieve this, a separate ''control sector'' is created outside of the play area to which other host sectors are tagged. Triggered through an [[FOF Linedef Type]], the engine then uniformly applies a subdivision in between the host sector's space based on the control sector's assigned textures and flats.

==== Polyobjects ====
''Polyobjects'' are an extension to use pieces of predefined map geometry as if they were map objects. This allows for many more gameplay mechanics such as spinning geometry, sideways crushers or swinging doors.

=== Things and MOBJs ===
''Full page: [[:Category:MOBJ]]''

''Things'' are static spawners for game objects placed within sectors. Upon map load, things are initialized and spawn their respective MOBJs. Things can also be given ''parameters'' and ''flags'', which may modify the Thing's behavior. Since Things are only initialized upon map load, this requires some gameplay design considerations when placing enemies such as [https://doomwiki.org/wiki/Monster_closet monster closets].

MOBJs are only spawned at runtime and represent game objects, such as enemies, gems or decorative sprites. MOBJs contain their own Object flags, which are distinct from Thing flags.

== UDMF Mapping ==
''[https://doomwiki.org/wiki/UDMF UDMF]'' stands for ''Universal Doom Map Format''. It is a textual map format developed for near-infinite extensibility within modern Doom engine source ports. It is not backwards compatible to older formats.

A UDMF map consists of the following lumps within a WAD or [[PK3]], :

* <code>MAPxx</code> - A simple marker lump denoting the map number. Required.
* <code>TEXTMAP</code> contains information on the map geometry (vertices, linedefs, sectors), SIDEDEFs and Things. Despite UDMF being a text format, it is not intended to be read or edited manually. Instead it should be parsed by dedicated programs such as Ultimate Zone Builder, SLADE or Weissblatt's game engine.
* <code>ZNODES</code> - BSP information generated by [https://doomwiki.org/wiki/ZDBSP ZDBSP] (as it's the only node builder with UDMF support). If missing, many Doom engines expect it to be generated on-the-fly by a ZDBSP instance built into the engine.

* <code>ENDMAP</code> - a simple marker lump. Required

=== TEXTMAP specification ===
Weissblatt supports UDMF <code>TEXTMAP</code>s of namespace <code>weissblatt</code> and <code>srb2</code>.

== Legacy Mapping ==
The Legacy map format was inherited from Sonic Robo Blast 2 and is now considered deprecated. Weissblatt does not develop it any further and merely maintains it for backwards compatibility. As such the format will be missing many features compared to Weissblatt's UDMF implementation.

Like traditional Doom maps, legacy maps are a ''binary map format'', meaning all data is encoded directly into byte structures. This brings some limitations:

# Each Sector/Linedef/Thing can only be assigned one tag
# Texture/Flat/Thing scaling is not supported
# Flat alignment/rotation is not supported
# Only 65536 tags are allowed.
# The total amount of possible walls, Linedefs, Sectors, etc. within a map may be limited.
# <TBA>

Binary maps are made up of the following lumps:

# <code>THINGS</code>
# <code>VERTEXES</code>
# <code>LINEDEFS</code>
# <code>SIDEDEFS</code>
# <code>SECTORS</code>

=== Reserved specialty tags ===
The Legacy map format does not support multitagging and is generally less flexible when it comes to tagging Things. To get around this, some Tag numbers are given special treatment:
{| class="wikitable"
|+
!Tag
!SOC/Lua Constant
!Effect
|-
|649
|<code>LE_AXE</code>
|Triggered when
|-
|650
|<code>LE_KOOPA</code>
|Triggered when <++> is defeated. Raises matching sectors' ceiling to the highest adjacent ceiling
|-
|680
|<code>LE_CAPSULE0</code>
| rowspan="3" |Triggered when a boss is defeated.
|-
|681
|<code>LE_CAPSULE1</code>
|-
|682
|<code>LE_CAPSULE2</code>
|-
|4200
|<code>LE_BRAKPLATFORM</code>
|Triggered after six hits to the alternate form of [[KOTU]].
|-
|32000
|<code>LE_TURRET</code>
|Triggered when a turret is destroyed.
|-
|65530 (-6)
|<code>LE_BRAKVILEATACK</code>
|Triggered when [[KOTU]] starts casting magic.
|-
|65531 (-5)
|<code>LE_BOSS4DROP</code>
|Triggered when <++> drops <++>
|-
|65532 (-4)
|<code>LE_BOSSDEAD</code>
|Triggered when any Boss is defeated
|-
|65533 (-3)
|<code>LE_ALLBOSSDEAD</code>
|Triggered when all Bosses are defeated
|-
|65534 (-2)
|<code>LE_PINCHPHASE</code>
|Triggered when Bosses switch into their pinch phase
|-
|65535 (-1)
|
|Affect every sector in a map
|-
|
|<code>LE_PARAMWIDTH</code>
|
|}

=== Conversion to UDMF ===
Legacy maps can be converted to UDMF maps: Simply launch the game using <code>-textmap</code> and <code>-warp <MAPNUM></code>. After you quit the game, the engine will save a UDMF conversion of your map to the file <code>TEXTMAP</code> within your game directory. You can use SLADE or Ultimate Zone Builder to recompile the newly-generated <code>TEXTMAP</code> into a proper UDMF map.
[[Category:Technology]]

Enlightenment Crystal

2026-03-03T16:12:07Z

Nyamoru: Chakra Shards - Specify Glenz Reactor

[[Category:The Asura Incident]]
[[Category:Worldbuilding]]

The ''Enlightenment Crystal'' is a building-sized magical crystal that served as the backbone of [[Delfid]] before it's destruction.

= History =
When the intelligence of Dolphins led to the discovery of crystal-based magic, the dolphins gradually adjusted their entire society around them to utilize their newly-gained spiritual powers. This lead to a schism with the [[Bouwder Tribe]], which eventually culminated in the construction of [[Delfid]] - an orbital city built around a massive crystal serving as a beacon to the world and to facilitate magical enlightenment.

== The Asura Incident ==
In 1999 [[Planet Weissblatt#Weissblatt Calendar|WBC]]. [[Fishbart Toyfeller|Dr. Asura]] visits Delfid and attempts to corrupt the Enlightenment Crystal using demonic magic, but is being spotted by [[Alex Felitas]]. In the following encounter, Alex is defeated and the Enlightenment Crystal splinters into seven [[#Chakra Shards|Chakra Shards]], destroying Delfid and spreading the crystal's remains across [[Planet Weissblatt]].

Knowing the dangers of a reassembled Enlightenment Crystal under dark magic, Alex casts a distress signal across the planet, opening portals to the [[Crystal Clockworld]] and pleading [[Volunteers]] to stop Dr. Asura, whom simultaneously orders a squad of Demons to scramble across the planet for the Chakra Shards.

During the 2000 [[Planet Weissblatt#Weissblatt Calendar|WBC]] equinox of the [[Planet Weissblatt#Moons|six moons of Planet Weissblatt]], demons at [[Equinox Gate]] mentioned to assemble the [[Equinox Gate#Zone 2|Glenz Reactor]] from parts of the Enlightenment Crystal in order to open a portal to [[The Underworld]]. After [[Shtayn|MARA]] brought the remaining Chakra Shards on-site through tricking [[Volunteers]], the parts are secured through the portal and a corrupted version of the Enlightenment Crystal is reassembled in the Underworld.

= Chakra Shards =
The ''Chakra Shards'' are the seven catalyst components of the splintered Enlightenment Crystal. During [[The Asura Incident]] they are collected by volunteers under plead from [[Alex Felitas]], as well as demons under order of [[Fishbart Toyfeller]]. Collecting all seven of them allows to reassemble the Enlightenment Crystal yielding unmatched spiritual powers to those who can harness it's magic.

Guide:Character Design

2026-01-17T19:34:09Z

Nyamoru: /* Furry Characters */

So you wanna design your own Weissblatt character? Here's everything you need to know.

== High-level basics of Character design ==
If there is one guiding principle to follow during character design, it's that '''audience perception is key.''' Make sure that your characters are unique and intuitively communicate a clear concept (ideally) from their appearance alone. Some helpful tips may include:

* Black out your character to see if they have a '''unique, recognizable silhouette'''. Try drawing them in different positions to see if they can retain their uniqueness.
* '''Keep it simple''': Can you draw a crude yet recognizable version of your character within 30 seconds? How about after you haven't looked at them for a day?
* Let your '''influences inform your character's design''': Where does your character come from? Do they prefer functional or extravagant clothing? Are they sloppy? There are many ways to convey character visually. If your intuition fails you, research various ideas and aesthetics until you find what you wanted to do all along.

=== Animation, expression and posture ===
Remember that Weissblatt's characters are ''designed to be animated. You're going to need to draw this character many, many times:''

* Get a clear idea for how to break your character down into simple shapes like cubes, cones spheres or tubes and how to maintain consistent proportions.

* Provide guidelines for posture and expressions of your character. Define how they act and not just how they look.

== Types of characters ==

=== Furry Characters ===
''Furry characters'' or ''Furries'' are planet Weissblatt's equivalent to humans - they are (usually) bipedal and act and talk in a human-like manner. The average adult male furry (such as [[Kleene Cognara]] or [[Dr. Roy Asura]]) is 1m tall, although this is an average and not a rule (e.g. [[Babel Memto]] is only 60cm tall due to being a mole). Females are naturally slightly shorter than males (~90 - 95cm, such as [[Elise Cantor]]).

'''Furry characters follow the [[wikipedia:Rubber_hose_animation|rubber hose style]].''' Their torsos are usually constructed from "Disney beans" - bean-like shapes made from two spheres (one for the shoulders and one for the pelvis). An adult furry's height is usually proportioned as three heads tall for illustrations (such as comic books or cutscenes) and two heads tall for toonier depicitions such as in-game sprites and playable 3D models. Children have bigger heads proprotional to the rest of their body, depending on their age/maturity.
[[File:Alex-sketchcompare.png|thumb|Example construction of [[Alex Felitas]]. Notice the two spheres forming a Disney bean underneath Alex' garment.]]
'''There are no (natural) humans on planet Weissblatt.''' Instead each furry is given features of a specific species to communicate their character. When designing a character, ask yourself: ''What does it tell the audience'' when character X is a Fox/Elephant/Lizard/etc.? As the line between human and non-human species can be blurry across fantasy media, we provided a guide as to what species are generally appropriate for furries:
[[File:Anthro-scale.png|thumb|Species guide for Weissblatt, ordered by likeness to humans vs. animals.]]
Cross-species transformations are currently undecided:

* Natural/intuitive transformations (such as a worm character turning into a butterfly upon enlightenment) are fine.
* (TBA)

==== WIP notes ====
- Bipedal rubberhose Characters (ex: Chimera)
-> Species is derived from character (Aesop)
->> ''Intuition is key. Make their themes readable''
-> Body shapes may vary.
''->>Keep your characters unique and interesting''
- Spirits are feral
- Feral animals allowed.

- Character Carnivores allowed*
-> Cross-species characters: Cannibalism
-> Feral animals: Animal cruelty (, phrenology?)
-> Delfid: Soul of deceased must be honored.

=== Feral characters ===
Feral characters are more animal-like - they generally also look and act like animals.

Spirits are (visually speaking) feral characters.

Weissblatt character are

== Drawing sprites ==
Weissblatt - The Asura incident follows a consistent texture scale of 64px == 64 [[Fracunit|Fracunits]] == 1m in-game (although some maps may scale some textures differently for visual effect).
[[Category:Guide]]

Guide:Character Design

2026-01-17T19:25:50Z

Nyamoru:

So you wanna design your own Weissblatt character? Here's everything you need to know.

== High-level basics of Character design ==
If there is one guiding principle to follow during character design, it's that '''audience perception is key.''' Make sure that your characters are unique and intuitively communicate a clear concept (ideally) from their appearance alone. Some helpful tips may include:

* Black out your character to see if they have a '''unique, recognizable silhouette'''. Try drawing them in different positions to see if they can retain their uniqueness.
* '''Keep it simple''': Can you draw a crude yet recognizable version of your character within 30 seconds? How about after you haven't looked at them for a day?
* Let your '''influences inform your character's design''': Where does your character come from? Do they prefer functional or extravagant clothing? Are they sloppy? There are many ways to convey character visually. If your intuition fails you, research various ideas and aesthetics until you find what you wanted to do all along.

=== Animation, expression and posture ===
Remember that Weissblatt's characters are ''designed to be animated. You're going to need to draw this character many, many times:''

* Get a clear idea for how to break your character down into simple shapes like cubes, cones spheres or tubes and how to maintain consistent proportions.

* Provide guidelines for posture and expressions of your character. Define how they act and not just how they look.

== Types of characters ==

=== Furry Characters ===
''Furry characters'' or ''Furries'' are planet Weissblatt's equivalent to humans - they are (usually) bipedal and act and talk in a human-like manner. The average adult male furry (such as [[Kleene Cognara]] or [[Dr. Roy Asura]]) is 1m tall, although this is an average and not a rule (e.g. [[Babel Memto]] is only 60cm tall due to being a mole). Females are naturally slightly shorter than males (~90 - 95cm, such as [[Elise Cantor]]).

'''Furry characters follow the [[wikipedia:Rubber_hose_animation|rubber hose style]].''' Their torsos are usually constructed from "Disney beans" - bean-like shapes made from two spheres (one for the shoulders and one for the pelvis). An adult furry's height is usually proportioned as three heads tall for illustrations (such as comic books or cutscenes) and two heads tall for toonier depicitions such as in-game sprites and playable 3D models.
[[File:Alex-sketchcompare.png|thumb|Example construction of [[Alex Felitas]]. Notice the two spheres forming a Disney bean underneath Alex' garment.]]
'''There are no (natural) humans on planet Weissblatt.''' Instead each furry is given features of a specific species to communicate their character. When designing a character, ask yourself: ''What does it tell the audience'' when character X is a Fox/Elephant/Lizard/etc.? As the line between human and non-human species can be blurry across fantasy media, we provided a guide as to what species are generally appropriate for furries:
[[File:Anthro-scale.png|thumb|Species guide for Weissblatt, ordered by likeness to humans vs. animals.]]
Cross-species transformations are currently undecided:

* Natural/intuitive transformations (such as a worm character turning into a butterfly upon enlightenment) are fine.
* (TBA)

==== WIP notes ====
- Bipedal rubberhose Characters (ex: Chimera)
-> Species is derived from character (Aesop)
->> ''Intuition is key. Make their themes readable''
-> Body shapes may vary.
''->>Keep your characters unique and interesting''
- Spirits are feral
- Feral animals allowed.

- Character Carnivores allowed*
-> Cross-species characters: Cannibalism
-> Feral animals: Animal cruelty (, phrenology?)
-> Delfid: Soul of deceased must be honored.

=== Feral characters ===
Feral characters are more animal-like - they generally also look and act like animals.

Spirits are (visually speaking) feral characters.

Weissblatt character are

== Drawing sprites ==
Weissblatt - The Asura incident follows a consistent texture scale of 64px == 64 [[Fracunit|Fracunits]] == 1m in-game (although some maps may scale some textures differently for visual effect).
[[Category:Guide]]

File:Alex-sketchcompare.png

2026-01-17T19:23:36Z

Nyamoru:

Alex Felitas reference pose in final render vs. sketch

Guide:Character Design

2026-01-17T19:17:36Z

Nyamoru:

So you wanna design your own Weissblatt character? Here's everything you need to know.

== High-level basics of Character design ==
If there is one guiding principle to follow during character design, it's that '''audience perception is key.''' Make sure that your characters are unique and intuitively communicate a clear concept (ideally) from their appearance alone. Some helpful tips may include:

* Black out your character to see if they have a '''unique, recognizable silhouette'''. Try drawing them in different positions to see if they can retain their uniqueness.
* '''Keep it simple''': Can you draw a crude yet recognizable version of your character within 30 seconds? How about after you haven't looked at them for a day?
* Let your '''influences inform your character's design''': Where does your character come from? Do they prefer functional or extravagant clothing? Are they sloppy? There are many ways to convey character visually. If your intuition fails you, research various ideas and aesthetics until you find what you wanted to do all along.

=== Animation, expression and posture ===
Remember that Weissblatt's characters are ''designed to be animated. You're going to need to draw this character many, many times:''

* Get a clear idea for how to break your character down into simple shapes like cubes, cones spheres or tubes and how to maintain consistent proportions.

* Provide guidelines for posture and expressions of your character. Define how they act and not just how they look.

== Types of characters ==

=== Furry Characters ===
''Furry characters'' or ''Furries'' are planet Weissblatt's equivalent to humans - they are (usually) bipedal and act and talk in a human-like manner. The average adult male furry (such as [[Kleene Cognara]] or [[Dr. Roy Asura]]) is 1m tall, although this is an average and not a rule (e.g. [[Babel Memto]] is only 60cm tall due to being a mole). Females are naturally slightly shorter than males (~90 - 95cm, such as [[Elise Cantor]]).

'''Furry characters follow the [[wikipedia:Rubber_hose_animation|rubber hose style]].''' Their torsos are usually constructed from "Disney beans" - bean-like shapes made from two spheres (one for the shoulders and one for the pelvis). An adult furry's height is usually proportioned as three heads tall for illustrations (such as comic books or cutscenes) and two heads tall for toonier depicitions such as in-game sprites and playable 3D models.

'''There are no (natural) humans on planet Weissblatt.''' Instead each furry is given features of a specific species to communicate their character. When designing a character, ask yourself: ''What does it tell the audience'' when character X is a Fox/Elephant/Lizard/etc.? As the line between human and non-human species can be blurry across fantasy media, we provided a guide as to what species are generally appropriate for furries:
[[File:Anthro-scale.png|thumb|Species guide for Weissblatt, ordered by likeness to humans vs. animals.]]
Cross-species transformations are currently undecided:

* Natural/intuitive transformations (such as a worm character turning into a butterfly upon enlightenment) are fine.
* (TBA)

==== WIP notes ====
- Bipedal rubberhose Characters (ex: Chimera)
-> Species is derived from character (Aesop)
->> ''Intuition is key. Make their themes readable''
-> Body shapes may vary.
''->>Keep your characters unique and interesting''
- Spirits are feral
- Feral animals allowed.

- Character Carnivores allowed*
-> Cross-species characters: Cannibalism
-> Feral animals: Animal cruelty (, phrenology?)
-> Delfid: Soul of deceased must be honored.

=== Feral characters ===
Feral characters are more animal-like - they generally also look and act like animals.

Spirits are (visually speaking) feral characters.

Weissblatt character are

== Drawing sprites ==
Weissblatt - The Asura incident follows a consistent texture scale of 64px == 64 [[Fracunit|Fracunits]] == 1m in-game (although some maps may scale some textures differently for visual effect).
[[Category:Guide]]

File:Anthro-scale.png

2026-01-17T19:04:27Z

Nyamoru:

Guiding scale of (non-)humanness for Weissblatt

Guide:Character Design

2026-01-17T14:07:04Z

Nyamoru: Created page with "On this page you can learn some basics for designing characters that feel appropriate to Weissblatt's style. == Basics == If there is one guiding principle to follow during character design, it's that '''audience perception is key.''' Make sure that your characters are unique and intuitively communicate a clear concept (ideally) from their appearance alone. Some helpful tips may include: * Black out your character to see if they have a '''unique, recognizable silhouett..."

On this page you can learn some basics for designing characters that feel appropriate to Weissblatt's style.

== Basics ==
If there is one guiding principle to follow during character design, it's that '''audience perception is key.''' Make sure that your characters are unique and intuitively communicate a clear concept (ideally) from their appearance alone. Some helpful tips may include:

* Black out your character to see if they have a '''unique, recognizable silhouette'''. Try drawing them in different positions to see if they can retain their uniqueness.
* '''Keep it simple''': Can you draw a crude yet recognizable version of your character within 30 seconds? How about after you haven't looked at them for a day?
* Let your '''influences inform your character's design''': Where does your character come from? Do they prefer functional or extravagant clothing? Are they sloppy? There are many ways to convey character visually. If your intuition fails you, research various ideas and aesthetics until you find what you wanted to do all along.

=== Animation, expression and posture ===
Remember that Weissblatt's characters are ''designed to be animated. You're going to need to draw this character many, many times:''

* Get a clear idea for how to break your character down into simple shapes like cubes, cones spheres or tubes and how to maintain consistent proportions.

* Provide guidelines for posture and expressions of your character. Define how they act and not just how they look.

== Types of characters ==

=== Furries ===
Furries are planet Weissblatt's equivalent to humans - they are (usually) bipedal and act and talk in a human-like manner. '''There are no (natural) humans on planet Weissblatt.''' As the line between human and non-human characters can be blurred within fantasy media, we provided a guide as to what species are generally appropriate for furries:

When deciding on a species for your character, follow their personality and background. This doesn't have to be a canonical reason - it may also be to evoke e.g. historical or mythological ideas. But ask yourself: ''What does it tell the audience'' when character X is a Fox/Elephant/Lizard/etc.?

Cross-species transformations are currently undecided:

* Natural/intuitive transformations (such as a worm character turning into a butterfly upon enlightenment) are fine.
* (TBA)

Furry characters follow the [[wikipedia:Rubber_hose_animation|rubber hose style]]. Their torsos are usually constructed from "Disney beans" - bean-like shapes made from two spheres (one for the shoulders and one for the pelvis). An adult furry character's height is usually proportioned as three heads tall for illustrations and two heads tall for toonier depicitions such as in-game sprites and playable 3D models.

==== WIP notes ====
- Bipedal rubberhose Characters (ex: Chimera)
-> Species is derived from character (Aesop)
->> ''Intuition is key. Make their themes readable''
-> Body shapes may vary.
''->>Keep your characters unique and interesting''
- Spirits are feral
- Feral animals allowed.

- Character Carnivores allowed*
-> Cross-species characters: Cannibalism
-> Feral animals: Animal cruelty (, phrenology?)
-> Delfid: Soul of deceased must be honored.

=== Feral characters ===
Feral characters are more animal-like - they generally also look and act like animals.

Spirits are (visually speaking) feral characters.

Weissblatt character are

[[Category:Guide]]

Guide:Animation

2026-01-17T13:11:35Z

Nyamoru: /* Tips and Tricks */

== The Twelve Principles of Animation ==
[[wikipedia:Twelve_basic_principles_of_animation|Twelve basic principles of animation]] is a book written by early Walt Disney animators Frank Thomas and Ollie Johnston. It outlines twelve general principles which are regarded as fundamental among animators.

To save you a lengthy, complicated explanation of each of these, here's a useful educational video by Alan Becker: https://www.youtube.com/watch?v=uDqjIdI4bF4

# '''Squash and Stretch'''
# '''Anticipation'''
# '''Staging'''
# '''Straight-Ahead and Pose-to-Pose'''
# '''Follow-Through and overlapping action'''
# '''Slow-In and Slow-Out'''
# '''Arcs'''
# '''Secondary Action'''
# '''Timing'''
# '''Exaggeration'''
# '''Solid Drawing'''
# '''Appeal'''

== Animating for Weissblatt ==

=== Doom Sprite animation system ===
Weissblatt's sprite animation system works by appending a ''frame'' and an ''angle'' to the name of your sprite's lump name. For example, the animation <code>WALK</code> may consist of the frames <code>WALKA0</code>, <code>WALKB0</code>, <code>WALKC0</code> and <code>WALKD0</code>. The frame is determined by a letter A to Z, while the angle is determined by a number.

Any sprite may be assigned to one or two frame-angle-pairs. When a second frame-angle pair is given, it will be displayed by horizontally flipping the sprite along it's offset. For example a single sprite may be called <code>WALKA3A7</code> to be used as both a left-facing and a right facing sprite.

The following table explains how the angle numbers are assigned:

{| class="wikitable"
|+Sprite angle system
|'''A4'''
(Back-Left diagonal)
|AC
|'''A5'''
(Back)
|AD
|'''A6'''
(Back-Right diagonal)
|-
|AB
| colspan="3" rowspan="3" |'''A0'''
(Billboarding)
|AE
|-
|'''A3/AL'''
(Left)
|'''A7/AR'''
(Right)
|-
|AA
|AF
|-
|'''A2'''
(Front-Left diagonal)
|A9
|'''A1'''
(Front)
|AG
|'''A8'''
(Front-Right diagonal)
|}
Sprites can be defined in multiple modes, depending on which angle is loaded last missing frames will result in an error:

# '''A0 mode''': Only an A0 angle is defined and the sprite is billboarded. This is usually used by decorative objects.
# '''Left-Right mode''': Only the angles AL and AR are defined. The sprite will always be facing either left or right, akin to a 2D game.
# '''Eight-Angle mode''': Angles A1 to A8 are required. This is the mode used by most characters and enemies.
# '''Sixteen-Angle mode''': Angles A1 to AG are required. This is used by the 8 ball.

=== Tips and Tricks ===

# Be sure to animate a good sketch first - it's easier to clean up when stuff goes wrong.
# Stage animations to be ''readable'' and ''express character.'' Viewers won't notice a little cheat to do so.
# Players are more likely to look at individual animations than full turnarounds. Focus on making good-looking animations first and then adjust them to look good from all sides.
# Most of the time there's no space for inbetweens. Focus on good key poses and breakdowns.
# Sometimes, the engine may play animations at different speeds. Consider the amount of frames in an animation as more important than the actual time. (This is contrary to how most film animation works.)

[[Category:Guide]]

Elise Cantor

2026-01-15T23:25:06Z

Nyamoru:

[[Category:The Asura Incident]]

{{Character|name=Elise Cantor|species=Swan-Stork mix,Robot|gender=female-coded|affiliation=[[Volunteers]]|color=Teal|birthdate=1988 WBC (Body), Mental age: 24|image=Elise-Cantor.png}}

'''Elise Cantor''' is an AI swan-stork-mix musician and one of the main playable characters of [[The Asura Incident]].

== Description ==
Elise usually presents as a teal swan-stork mix, with her body being projected out from her helmet. Her helmet is a mixture between an [[wikipedia:Armet|Armet]] and a [[wikipedia:Pickelhaube|Pickelhaube]] with speakers in place of the visor's hinges and a lamp on top of it's prick, giving it the appearance of an antenna. Her holographic body provides just enough solidity to serve as a means of transport and physical expression, such as dancing. Despite her beak, Elise speaks mainly from her helmet's speakers.

When in her enlightened form ''supreme Elise'', her helmet turns golden with both her helmet and her hologram gaining wings. Her bow tie is also replaced with a pearl-based brooch.

Since her helmet lacks persistent storage, she may occasionally lay "Zip Eggs" containing a snapshot of her AI. This process is extremely exhausting to Elise, usually requiring a reboot afterwards using the freshly-laid egg.

== History ==
Elise was built by [[Kleene Cognara]] at the age of 16 during a night of black-out-drunk hardware hacking. Although initially built to alleviate Kleene's loneliness, Elise eventually deduced that her objective to create love had outgrown Kleene and that more people across the world needed her. She discovered a fascination for music and performs as "ELI5E", an idol spcialising in Jazz and electronica, trying to touch as many hearts as she can with her music and stage persona. In private, she still largely sticks by Kleene's side, both for maintenance as well as their relationship.

== Gallery ==
[[File:Elise-and-spirits.png|thumb|Conccept art of Elise Cantor tending a spirit]]
[[File:Elise Cantor refsheet.png|thumb|Model Sheet for Elise]]
[[File:Supreme Elise refsheet.png|thumb|Model Sheet for ''Supreme Elise,'' her enlightened form.]]
[[File:Elise and Kleene.png|thumb|Elise and Kleene flying together. Used by the character selection option for Elise & Kleene]]

== Trivia ==
Alongside [[Kleene Cognara]] and [[Babel Memto]], Elise was inspired by [[wikipedia:Muses|the three (original) muses from greek mythology]], with Elise representing the artistic/musical aspect.

Elise's last name simultaneously means "singer" in Latin. It's also is a reference to [[wikipedia:Georg_Cantor|Georg Cantor]], a german mathematician known his work on mathematical infinity.

Elise's musical preference for electronic music and jazz was inspired by the creatively liberal cultures around [[wikipedia:Vocaloid|Vocaloid]] and jazz music respectively, with her character design being inspired by orchestra conductors, [https://snk.fandom.com/wiki/Charlotte_Christine_de_Colde Charlotte Christine de Colde] and [[wikipedia:Hatsune_Miku|Hatsune Miku]]

File:Elise-and-spirits.png

2026-01-15T23:24:20Z

Nyamoru:

Concept art of Elise Cantor and a spirit

File:Elise-Cantor.png

2026-01-15T23:12:28Z

Nyamoru: Nyamoru uploaded a new version of File:Elise-Cantor.png

== Summary ==
Sample picture of Elise Cantor

Elise Cantor

2026-01-14T13:09:33Z

Nyamoru:

[[Category:The Asura Incident]]

{{Character|name=Elise Cantor|species=Swan-Stork mix,Robot|gender=female-coded|affiliation=[[Volunteers]]|color=Teal|birthdate=1988 WBC (Body), Mental age: 24|image=Elise-Cantor.png}}

'''Elise Cantor''' is an AI swan-stork-mix musician and one of the main playable characters of [[The Asura Incident]].

== Description ==
Elise usually presents as a teal swan-stork mix, with her body being projected out from her helmet. Her helmet is a mixture between an [[wikipedia:Armet|Armet]] and a [[wikipedia:Pickelhaube|Pickelhaube]] with speakers in place of the visor's hinges and a lamp on top of it's prick, giving it the appearance of an antenna. Her holographic body provides just enough solidity to serve as a means of transport and physical expression, such as dancing. Despite her beak, Elise speaks mainly from her helmet's speakers.

When in her enlightened form ''supreme Elise'', her helmet turns golden with both her helmet and her hologram gaining wings. Her bow tie is also replaced with a pearl-based brooch.

Since her helmet lacks persistent storage, she may occasionally lay "Zip Eggs" containing a snapshot of her AI. This process is extremely exhausting to Elise, usually requiring a reboot afterwards using the freshly-laid egg.

== History ==
Elise was built by [[Kleene Cognara]] at the age of 16 during a night of black-out-drunk hardware hacking. Although initially built to alleviate Kleene's loneliness, Elise eventually deduced that her objective to create love had outgrown Kleene and that more people across the world needed her. She discovered a fascination for music and performs as "ELI5E", an idol spcialising in Jazz and electronica, trying to touch as many hearts as she can with her music and stage persona. In private, she still largely sticks by Kleene's side, both for maintenance as well as their relationship.

== Gallery ==
[[File:Elise-Cantor.png|thumb|Concept art of Elise tending some spirits]][[File:Elise Cantor refsheet.png|thumb|Model Sheet for Elise]]
[[File:Supreme Elise refsheet.png|thumb|Model Sheet for ''Supreme Elise,'' her enlightened form.]]
[[File:Elise and Kleene.png|thumb|Elise and Kleene flying together. Used by the character selection option for Elise & Kleene]]

== Trivia ==
Alongside [[Kleene Cognara]] and [[Babel Memto]], Elise was inspired by [[wikipedia:Muses|the three (original) muses from greek mythology]], with Elise representing the artistic/musical aspect.

Elise's last name simultaneously means "singer" in Latin. It's also is a reference to [[wikipedia:Georg_Cantor|Georg Cantor]], a german mathematician known his work on mathematical infinity.

Elise's musical preference for electronic music and jazz was inspired by the creatively liberal cultures around [[wikipedia:Vocaloid|Vocaloid]] and jazz music respectively, with her character design being inspired by orchestra conductors, [https://snk.fandom.com/wiki/Charlotte_Christine_de_Colde Charlotte Christine de Colde] and [[wikipedia:Hatsune_Miku|Hatsune Miku]]

Elise Cantor

2026-01-14T13:08:04Z

Nyamoru:

[[Category:The Asura Incident]]

{{Character|name=Elise Cantor|species=Swan-Stork mix,Robot|gender=female-coded|affiliation=[[Volunteers]]|color=Teal|birthdate=1988 WBC (Body), Mental age: 24|image=Elise-Cantor.png}}

'''Elise Cantor''' is an AI swan-stork-mix musician and one of the main playable characters of [[The Asura Incident]].

== Description ==
Elise usually presents as a teal swan-stork mix, with her body being projected out from her helmet. Her helmet is a mixture between an [[wikipedia:Armet|Armet]] and a [[wikipedia:Pickelhaube|Pickelhaube]] with speakers in place of the visor's hinges and a lamp on top of it's prick, giving it the appearance of an antenna. Her holographic body provides just enough solidity to serve as a means of transport and physical expression, such as dancing. Despite her beak, Elise speaks mainly from her helmet's speakers.

When in her enlightened form ''supreme Elise'', her helmet turns golden with both her helmet and her hologram gaining wings. Her bow tie is also replaced with a pearl-based brooch.

Since her helmet lacks persistent storage, she may occasionally lay "Zip Eggs" containing a snapshot of her AI. This process is extremely exhausting to Elise, usually requiring a reboot afterwards using the freshly-laid egg.

== History ==
Elise was built by [[Kleene Cognara]] at the age of 16 during a night of black-out-drunk hardware hacking. Although initially built to alleviate Kleene's loneliness, Elise eventually deduced that her objective to create love had outgrown Kleene and that more people across the world needed her. She discovered a fascination for music and performs as "ELI5E", an idol spcialising in Jazz and electronica, trying to touch as many hearts as she can with her music and stage persona. In private, she still largely sticks by Kleene's side, both for maintenance as well as their relationship.

== Gallery ==
[[File:Elise Cantor refsheet.png|thumb|Model Sheet for Elise]]
[[File:Supreme Elise refsheet.png|thumb|[[File:Elise-Cantor.png|thumb|Concept art of Elise tending some spirits]]Model Sheet for ''Supreme Elise,'' her enlightened form.]]
[[File:Elise and Kleene.png|thumb|Elise and Kleene flying together. Used by the character selection option for Elise & Kleene]]

== Trivia ==
Alongside [[Kleene Cognara]] and [[Babel Memto]], Elise was inspired by [[wikipedia:Muses|the three (original) muses from greek mythology]], with Elise representing the artistic/musical aspect.

Elise's last name simultaneously means "singer" in Latin. It's also is a reference to [[wikipedia:Georg_Cantor|Georg Cantor]], a german mathematician known his work on mathematical infinity.

Elise's musical preference for electronic music and jazz was inspired by the creatively liberal cultures around [[wikipedia:Vocaloid|Vocaloid]] and jazz music respectively, with her character design being inspired by orchestra conductors, [https://snk.fandom.com/wiki/Charlotte_Christine_de_Colde Charlotte Christine de Colde] and [[wikipedia:Hatsune_Miku|Hatsune Miku]]

Kleene Cognara

2026-01-14T13:06:41Z

Nyamoru:

[[Category:The Asura Incident]]

{{Character
|name=Kleene Cognara
|species=Beaver
|gender=Male
|affiliation=[[Volunteers]]
|color=Sangria
|birthdate=1972 WBC
|image=Kleene-Cognara.png}}

'''Kleene Cognara''' is one of the main playable characters of [[The Asura Incident]]. He's an inventive, yet practically-oriented beaver engineer who can use his self-built jet-boosted clothing to fly for short periods of time.

== Description ==
Kleene is a red beaver with an interest in engineering and a mostly utilitarian mindset. He wears mostly functional clothing, including scrappy self-built machinery with which he can fly around for short periods of time.

Although curious and open about experimenting with technology, he prefers to remain practical. He is easily annoyed by bad design and will quickly throw together scrappy prototypes to test out whatever ideas he can come up with as soon as possible. Occasionally he may ramble or scribble onto his PDA to create more ideas he can't build yet.

== History ==
From a young age Kleene was curious about mechanics and would frequently destroy or disassemble toys to figure out how they work. This fascination led him to pursue mechanical engineering, driven by a dream of one day understanding the unconventional mechanics behind toys built and designed by [[Patsy Toyfeller]]. His studies led him to befriend [[Babel Memto]].

Sexually frustrated at the age of 16, Kleene built [[Elise Cantor]] during a night of black-out-drunk garage hacking. Ever since building Elise, Kleene claims to be unable to replicate her, both due to outdated parts as well as lack of documentation and memory creating her. After Elise helped recover Kleene's mental state and developed autonomy, he let her go out of a growing sense of responsibility.

Years later, as he was on [[Stella Mountain]] alongside Elise and Babel testing an ancient flight machine design by [[Marco Vinci]] the three of them were struck down by [[Dr. Roy Asura|Dr. Asura]], whom had just escaped the destruction of [[Delfid]].

== Gallery ==
[[File:Kleene refsheet.png|thumb|Model sheet for Kleene Cognara]]
[[File:Kleene Cognara with cube.png.png|thumb|Four-Panel concept comic showcasing Kleene's character]]
[[File:Elise and Kleene.png|thumb|Elise and Kleene flying together. Used by the character selection option for Elise & Kleene]]

== Trivia ==
Alongside [[Elise Cantor]] and [[Babel Memto]], Kleene was inspired by [[wikipedia:Muses|the three (original) muses from greek mythology]], with Kleene representing the scientific aspect.

Kleene's first name is a reference to [[wikipedia:Stephen_Cole_Kleene|Stephen Cole Kleene]], an american mathematician known for inventing [[wikipedia:Regular_expression|regular expressions]].

Kleene's character was mainly inspired by maker and hacker culture, in particular the [https://medium.com/@bre/the-cult-of-done-manifesto-724ca1c2ff13 Cult of Done manifesto]

File:Elise and Kleene.png

2026-01-14T13:06:25Z

Nyamoru:

Elise and Kleene flying together. Used by the character selection option for Elise & Kleene

Frozen Record

2025-10-21T21:39:58Z

Nyamoru: /* Concept draft */

''Frozen Record'' is a militarized library located at the polar caps of [[Planet Weissblatt]]. It served as an archive of worldly knowledge - particularly as backup for [[Delfid]]. During [[The Asura Incident]] it is caught in a struggle between volunteers and demons.

== Concept draft ==
<pre>
# Frozen Record Zone

**Author**: Zibon "PixL" Badi
**Mapper**: NONE
**Canon**: Delfid
**Placement**: Phase 1

## Lore

Delfid knew it was not to last, which is why it's citizens sought to preserve it's wisdom and culture on planet Weissblatt. This gigantic library located around the polar caps serves as a record of all but it's most recent discoveries and now that the orbital city is no more, it remains the last. Previously guarded to preserve it's accuracy, the opening of the *Crystal Clockworld* has rendered even the strongest defenses futile against the flood of incoming demons and volunteers. One has to wonder what drives everyone to flock to this library, whether they seek to preserve, to share, to revise or to destroy it's recordings.

## Author's Notes

You can think of FRZ as a hybrid ice/library/military map. Somewhere between the Great Library of Alexandria and Shadow Moses Island. Stealth mechanics, turrets and such are a natural here.

## Themes/Aesthetics

- Arctic
- Militarized
- Library (inside)
- Stealth gameplay

## Elements

- Shield guard w/ fixed paths
- (Lancer guards)
- Turrets
- Elemental shields
- Ice physics
- Snow physics
- Crystal shard hunt

## Ideas

### Act 1

- Act 1 for infiltration, Act 2 for exploration
- Include a frosty cave with ice water sections, requiring elemental shields to pass (Ghostenks)

### Act 2

- Structure the inside of the facility like a tower/silo around a giant rosetta stone-like structure (PixL)
- Labyrinth to expand on the stealth mechanics

## Sequence

### Act 1

1. Player is placed under the open polar-lit sky, stepping through snow
2. Player sees a snow-covered entrance to the base, guarded by a turret behind a fence
3. Player escapes into a nearby cave
4. Player slips on some ice inside the cave and discovers some ice water ponds (+maybe an elemental shield)
5. Player eventually enters a broken canal by breaking some ice -> ice water slowly drains gems
6. Player exits the canal behind the building; covered by some crates
- Player must pass hallway patrolled by shield guards
- Player is attacked by vertical cannons
- Player must squeeze along the narrow outside of the compound
99. Player sneaks through the snow-covered courtyard past the turret and into the inside of the building

### Act 2

1. Player starts inside of an elevator, moving downwards
2. Player encounters a giant rosetta stone-like structure connecting multiple rooms
- Player encounters patrolling guards and tries to avoid them
- Climbs on top of bookshelves to avoid them

</pre>
[[Category:Location]]

Babel Memto

2025-09-22T12:51:36Z

Nyamoru:

[[Category:The Asura Incident]]

{{Infobox character|name=Babel Memto|species=Mole|color=green|gender=male|image=Babel-Memto.png|height=60cm}}

{{Character|image=Babel-Memto.png|species=Mole|gender=Male|color=Island (Green)|affiliation=Volunteer|name=Babel Memto}}

''Babel Memto'' is a playable Character in [[The Asura Incident]]. Alongside [[Elise Cantor]] and [[Kleene Cognara]], he is one of the three main characters of the game.

== Abilities ==
Babel is a mole librarian with an interest in history and old trashy movies, of which he keeps a personal archive which he regularly screens as a hobby. He is able to climb, swim and glide for, which leads him down unconventional paths when moving around the terrain.

== Gallery ==
[[File:Babel Refsheet.png|thumb|Model Sheet for Babel Memto]]
[[Category:Character]]

File:Babel-Memto.png

2025-09-22T12:50:54Z

Nyamoru: Character select picture for Babel Memto

== Summary ==
Character select picture for Babel Memto

Babel Memto

2025-09-22T12:50:08Z

Nyamoru:

[[Category:The Asura Incident]]

{{Infobox character|name=Babel Memto|species=Mole|color=green|gender=male|image=Babel-Memto.png|height=60cm}}

{{Character|image=Babel-Memto.png|species=Mole|gender=Male|color=Island (Green)|affiliation=Volunteer}}

''Babel Memto'' is a playable Character in [[The Asura Incident]]. Alongside [[Elise Cantor]] and [[Kleene Cognara]], he is one of the three main characters of the game.

== Abilities ==
Babel is a mole librarian with an interest in history and old trashy movies, of which he keeps a personal archive which he regularly screens as a hobby. He is able to climb, swim and glide for, which leads him down unconventional paths when moving around the terrain.

== Gallery ==
[[File:Babel Refsheet.png|thumb|Model Sheet for Babel Memto]]
[[Category:Character]]

Babel Memto

2025-09-22T12:47:39Z

Nyamoru:

[[Category:The Asura Incident]]

{{Infobox character|name=Babel Memto|species=Mole|color=green|gender=male|image=Babel-Memto.png|height=60cm}}''Babel Memto'' is a playable Character in [[The Asura Incident]]. Alongside [[Elise Cantor]] and [[Kleene Cognara]], he is one of the three main characters of the game.

== Abilities ==
Babel is a mole librarian with an interest in history and old trashy movies, of which he keeps a personal archive which he regularly screens as a hobby. He is able to climb, swim and glide for, which leads him down unconventional paths when moving around the terrain.

== Gallery ==
[[File:Babel Refsheet.png|thumb|Model Sheet for Babel Memto]]
[[Category:Character]]

The Underworld

2025-09-05T20:05:15Z

Nyamoru: /* Zones */

[[Category:The Asura Incident]]

[[Category:Location]]

'''The Underworld''' is the domain of Demons .
= Zones =
# The Underworld

**Author**: Zibon "PixL" Badi
**Mapper**: NONE
**Canon**: Delfid
**Placement**: Phase 3 (race against MARA & final boss)

## Lore

After being chased and confronted by our heroes, Mara pulls them into the underworld where it is uncovered that Mara has been possessed by none other
than the king of demons himself. These winding, non-euclidean caves being
the home domain of the demons, their absurd, alien structure appears
inherently hostile to any non-demonic visitors.

## Author's Notes

May contain traces of *Crystal Clockworld*, if we end up making that one.

## Themes/Aesthetics/Goals

### Underworld 99

- Abstract shapes
- Optical illusion and disorientation

### Underworld 66

- Roses & Brambles
- Gothic influences
- "Eclipse" from Berserk

## Elements

- Gravflip
- Frequent scenery change (UW99)

## Sequence

### Underworld 99

1. Player starts on a rainbow floor with an abstract, seemingly infinite skybox
1. MARA dances akin to Shiva to mock the player
2. Race against MARA starts
x. Player jumps a couple regular obstacles, such as spikes
x. Player jumps a set of sparsely-placed moving floor sections
x. Player reaches another speed section with timed mechanics, requiring precise jump/roll timing
x. Floor reaches end, but rainbow ceiling appears -> Player jumps to gravflip
x. Player gravflips between more sparsely placed/moving floor/ceiling sections
x. Zoom tube mask a skybox change to UW66, leading the player's rainbow floor towards ending at the UW66 platform
99. Race ends on UW66 platform (END)

### Underworld 66

1. Intro sequence
a. Player starts inside giant rosebud
b. MARA is released from his puppet (jumps up and explodes)
c. Outer rose petals fall away, revealing a wide cave made of soul plants w/ the re-assembled Enlightenment Crystal in the background
d. Inner rosebud opens, revealing KOTU
2. Boss fight against KOTU
3. At pinch phase, some petals of the rosebud drop, leaving less cover to the player
4. After KOTU is defeated, music cuts out and a crystal altar reaches out of the ground
5. Player climbs the altar and a rumble followed by a white flash lead into the ending cutscene

== Underworld 99 ==

In '''Underworld 99''', the player chases [[Shtayn|MARA]] through an interdimensional passage.
== Underworld 66 ==

'''Underworld 66''' pits the player against the campaign's final boss [[Shtayn|KOTU]].
== Infinite Pathway==

'''Infinite Pathway''' is the 8th special stage in [[The Asura Incident]].

The Underworld

2025-09-05T20:03:04Z

Nyamoru: /* Zones */

[[Category:The Asura Incident]]

[[Category:Location]]

'''The Underworld''' is the domain of Demons .
= Zones =
# The Underworld

**Author**: Zibon "PixL" Badi
**Mapper**: NONE
**Canon**: Delfid
**Placement**: Phase 3 (race against MARA & final boss)

## Lore

After being chased and confronted by our heroes, Mara pulls them into the underworld where it is uncovered that Mara has been possessed by none other
than the king of demons himself. These winding, non-euclidean caves being
the home domain of the demons, their absurd, alien structure appears
inherently hostile to any non-demonic visitors.

## Author's Notes

May contain traces of *Crystal Clockworld*, if we end up making that one.

## Themes/Aesthetics/Goals

### Underworld 99

- Abstract shapes
- Optical illusion and disorientation

### Underworld 66

- Roses & Brambles
- Gothic influences
- "Eclipse" from Berserk

## Elements

- Gravflip
- Frequent scenery change (UW99)

## Sequence

### Underworld 99

1. Player starts on a rainbow floor with an abstract, seemingly infinite skybox
1. MARA dances akin to Shiva to mock the player
2. Race against MARA starts
x. Player jumps a couple regular obstacles, such as spikes
x. Player jumps a set of sparsely-placed moving floor sections
x. Player reaches another speed section with timed mechanics, requiring precise jump/roll timing
x. Floor reaches end, but rainbow ceiling appears -> Player jumps to gravflip
x. Player gravflips between more sparsely placed/moving floor/ceiling sections
x. Zoom tube mask a skybox change to UW66, leading the player's rainbow floor towards ending at the UW66 platform
99. Race ends on UW66 platform (END)

### Underworld 66

1. Intro sequence
a. Player starts inside giant rosebud
b. MARA is released from his puppet (jumps up and explodes)
c. Outer rose petals fall away, revealing a wide cave made of soul plants w/ the re-assembled Enlightenment Crystal in the background
d. Inner rosebud opens, revealing KOTU
2. Boss fight against KOTU
3. After KOTU is defeated, music cuts out and a crystal altar reaches out of the ground
4. Player climbs the altar and a rumble followed by a white flash lead into the ending cutscene

== Underworld 99 ==

In '''Underworld 99''', the player chases [[Shtayn|MARA]] through an interdimensional passage.
== Underworld 66 ==

'''Underworld 66''' pits the player against the campaign's final boss [[Shtayn|KOTU]].
== Infinite Pathway==

'''Infinite Pathway''' is the 8th special stage in [[The Asura Incident]].

Equinox Gate

2025-09-05T19:48:06Z

Nyamoru: /* Concept draft */

''Equinox Gate'' is a volcano featuring a launch base built by [[Dr. Asura]]. The name is derived from it's launch base, which requires the Enlightenment Crystal to be placed inside it to function during the ''Equinox''.

== Concept draft ==
<pre>
# Equinox Gate Zone

**Author**: Zibon "PixL" Badi
**Mapper**: \<NONE\>
**Canon**: Delfid
**Placement**: Phase 2

## Lore

Hidden inside a volcano, Dr. Asura prepared a launch base for the *Equinox*,
a rare alignment of Weissblatt's six moons that allows him to utilize the
Chakra Shards' magic for his own purposes.

After the player defeats Patsy Toyfeller during the campaign, MARA steals
the contract to Patsy's soul to lure them into here and use the Chakra
Shards to fuse Weissblatt with the underworld.

## Author's Notes

It's a magic tech launch base inside of a volcano. May contain traces of a
race against MARA, although the difficult parts should be reserved for
*The Underworld*. The second stage of this is intended to be the boss fight
against MARA, with an optional retreat of theirs into the underworld,
should the player have collected all seven Chakra Shards up to this point.

## Themes/Aesthetics

- Volcano
- Launch base/Sci-fi
- Slight dashes of tropical
- Hectic/Hasty gameplay
- Downward spiral/descent into crater

## Elements

- Lasers
- Moving bridges
- Lava
- Pools
- Falls
- 8 balls
- Fans/Wind tunnels

## Ideas

## Sequence

0. <++>
1. Player starts on the outside of the island, spotting MARA running away in the distance
2. Player rushes across some crumbling bridges and encounters a lava river
3. Player crosses the lava river using a nearby 8 ball
outside terrain (crumbling bridges, lava rivers) toward the ridge of the crater
4. Player descends through the crater using nearby safe terrain, passing wind currents from the heat below as well as some cooling units from the side of the walls
- (The sections switch between crater and cave areas, w/ crater areas having an air counter for "heat")
5. Towards the bottom, player is faced with laser defense systems and turrets to avoid (possibly another 8 ball section)
99. Player reaches the arena bottom area of the crater (end)

## Act 2

1. Boss fight against MARA
2a. (If NOT all Chakra Shards)
1. Bridge raises
2. player exit
3. Game end
2b. (If all Chakra Shards)
1. Volcano revealed to be a trap
2. Glenz reactor activates -> Portal to underworld appears
3. Player jumps into portal
</pre>

== In ''The Asura Incident'' ==

=== Zone 1 ===
In zone 1, the player chases [[MARA]] across the volcano, first from the outside then from the inside.

=== Zone 2 ===
[[File:Glenz-reactor-concept.png|thumb|Concept art for Equinox Gate 2 titled "The Glenz reactor"]]
Zone 2 starts where Zone 1 left off and the player is locked inside the capsule to fight MARA.

After MARA is defeated, the entire arena is lifted downwards to reveal a laboratory underneath. Following a tunnel reveals a reactor-like structure featurng a pitch black portal overgrown with brambles, leading the player into [[The Underworld]].
[[Category:Location]]

Equinox Gate

2025-09-05T19:45:00Z

Nyamoru: /* Concept draft */

''Equinox Gate'' is a volcano featuring a launch base built by [[Dr. Asura]]. The name is derived from it's launch base, which requires the Enlightenment Crystal to be placed inside it to function during the ''Equinox''.

== Concept draft ==
<pre>
# Equinox Gate Zone

**Author**: Zibon "PixL" Badi
**Mapper**: \<NONE\>
**Canon**: Delfid
**Placement**: Phase 2

## Lore

Hidden inside a volcano, Dr. Asura prepared a launch base for the *Equinox*,
a rare alignment of Weissblatt's six moons that allows him to utilize the
Chakra Shards' magic for his own purposes.

After the player defeats Patsy Toyfeller during the campaign, MARA steals
the contract to Patsy's soul to lure them into here and use the Chakra
Shards to fuse Weissblatt with the underworld.

## Author's Notes

It's a magic tech launch base inside of a volcano. May contain traces of a
race against MARA, although the difficult parts should be reserved for
*The Underworld*. The second stage of this is intended to be the boss fight
against MARA, with an optional retreat of theirs into the underworld,
should the player have collected all seven Chakra Shards up to this point.

## Themes/Aesthetics

- Volcano
- Launch base/Sci-fi
- Slight dashes of tropical
- Hectic/Hasty gameplay
- Downward spiral/descent into crater

## Elements

- Lasers
- Moving bridges
- Lava
- Pools
- Falls
- 8 balls
- Fans/Wind tunnels

## Ideas

## Sequence

0. <++>
1. Player starts on the outside of the island, spotting MARA running away in the distance
2. Player rushes across some crumbling bridges and encounters a lava river
3. Player crosses the lava river using a nearby 8 ball
outside terrain (crumbling bridges, lava rivers) toward the ridge of the crater
4. Player descends through the crater using nearby safe terrain, passing wind currents from the heat below as well as some cooling units from the side of the walls
5. Towards the bottom, player is faced with laser defense systems and turrets to avoid
99. Player reaches the arena bottom area of the crater (end)

## Act 2

1. Boss fight against MARA
2a. (If NOT all Chakra Shards)
1. Bridge raises
2. player exit
3. Game end
2b. (If all Chakra Shards)
1. Volcano revealed to be a trap
2. Glenz reactor activates -> Portal to underworld appears
3. Player jumps into portal
</pre>

== In ''The Asura Incident'' ==

=== Zone 1 ===
In zone 1, the player chases [[MARA]] across the volcano, first from the outside then from the inside.

=== Zone 2 ===
[[File:Glenz-reactor-concept.png|thumb|Concept art for Equinox Gate 2 titled "The Glenz reactor"]]
Zone 2 starts where Zone 1 left off and the player is locked inside the capsule to fight MARA.

After MARA is defeated, the entire arena is lifted downwards to reveal a laboratory underneath. Following a tunnel reveals a reactor-like structure featurng a pitch black portal overgrown with brambles, leading the player into [[The Underworld]].
[[Category:Location]]

Stella Mountain

2025-09-05T19:37:15Z

Nyamoru: /* Concept */

[[Category:Location]]
[[Category:The Asura Incident]]

'''Stella Mountain''' is a mountain range on [[Planet Weissblatt]].
= History =

At some point during 1000 [[Planet Weissblatt#Weissblatt Calendar|WBC]], [[Shogun Yuko]] set up a secret hideout before the [[Siege on Cleron]].

In 1999 [[Planet Weissblatt#Weissblatt Calendar|WBC]], [[Kleene Cognara]], [[Elise Cantor]] and [[Babel Memto]] were caught in the crossfire of [[Fishbart Toyfeller|Dr. Roy Asura]] crash landing on Stella Mountain shortly after [[The Asura Incident (Scene)]].

== In ''The Asura Incident'' ==

=== Concept ===
# Stella Mountain Zone

**Author**: Zibon "PixL" Badi
**Mapper**: \<NONE\>
**Canon**: Delfid, Yuko (referenced)
**Placement**: Phase 1

## Lore

The Marble empire has spent most of it's history isolated from the rest of planet Weissblatt's continents. This is in no small part due to *Stella Mountain*, the mountain range located at the northern isthmus of the peninsula. Although nowadays navigable and a well-known tourist spot for it's beautiful landscapes, it is said that Stella Mountain reaches so far into the sky that it frequently catches incoming shooting stars. During the Asura incident, it happened to be the chosen vacation spot of Kleene Cognara, Elise Cantor and Babel Memto right as they crash landed alongside Dr. Asura following the destruction of Delfid.

## Author's Notes

This zone has more or less been born out of it's assets. Think of it as a Green Hill archetype with large vertical scale under a starry sky as incoming shooting stars form craters on the ground.

## Elements

- Piggy Tanks
- Breakable walls/floors
- Crumbling floors?
- Hanging Ropes
- Low-gravity sections

## Ideas/Goals

- Act one as simple introduction to the mechanics
- Ascending geometry
- non-punishing
- mountain climb
- Serpentine-like structure
- Hidden cave w/ Equinox mural at the wall
- (Meteorite impact => Craters in the ground)

## Moments/Sequence

### Act 1

1. Player starts on a crystal altar on an open field
2. Player explores the environment and finds <++>
x. Player encounters a plateau with a giant turnip

### Act 2

1. Player climbs a steep rift/tower and sees "a way forward" alongside the wide-open skybox
2. Meteorite impact reveals an underground cave
99. Player ends on a plateau jumping into Dr. Asura's impact crater

### Act 3

1. Boss Fight against Dr. Asura inside his impact crater
2. Boss defeated => Crystal altar reaches out of ground w/ portal teleported on top
3. Portal leads to CCW

=== In ''Sentinels of Yuko'' ===
# Stella Mountain Zone (Yuko)

**Author**: Zibon "PixL" Badi, Victor "NotablyPrettyCrazy"
**Mapper**: <TBD>
**Canon**: Yuko, Delfid (original)
**Placement**: Late campaign

## Lore

The Marble empire has spent most of it's history isolated from the rest of planet Weissblatt's continents. This is in no small part due to Stella Mountain, the mountain range located at the northern isthmus of the peninsula. It is believed by the Marble empire's astrologers that Stella Mountain reaches so far that all shooting stars in the sky eventually end up there.

Although a mystery wanting to be solved, during the times of the Yuko wars this mountain range was still considered insurmountable. A few brave souls have attempted to conquer it, usually to never be heard from again. Shogun Yuko somehow managed to create a secret hideout somewhere on there where the ancient scrolls are probably located.

## Author's Notes

It's concept is based on the Delfid canon's Stella Mountain Zone, although with a few notes regarding the Yuko canon:

There's no civilization on here, so navigating Stella Mountain's unaltered natural landscape is a lot more dangerous -> we can make this version of Stella Mountain a lot harder.

Regardless of whether we're doing so for Delfid, Stella Mountain's stratospheric height justifies some light space elements, such as low gravity sections

## Gameplay Ideas

- Weather-based obstacles
- No civilization yet => Dangerous terrain

## Moments/Sequence

- Fight against Ganbaatar

Stella Mountain

2025-09-05T19:36:25Z

Nyamoru: /* Concept */

[[Category:Location]]
[[Category:The Asura Incident]]

'''Stella Mountain''' is a mountain range on [[Planet Weissblatt]].
= History =

At some point during 1000 [[Planet Weissblatt#Weissblatt Calendar|WBC]], [[Shogun Yuko]] set up a secret hideout before the [[Siege on Cleron]].

In 1999 [[Planet Weissblatt#Weissblatt Calendar|WBC]], [[Kleene Cognara]], [[Elise Cantor]] and [[Babel Memto]] were caught in the crossfire of [[Fishbart Toyfeller|Dr. Roy Asura]] crash landing on Stella Mountain shortly after [[The Asura Incident (Scene)]].

== In ''The Asura Incident'' ==

=== Concept ===
# Stella Mountain Zone

**Author**: Zibon "PixL" Badi
**Mapper**: \<NONE\>
**Canon**: Delfid, Yuko (referenced)
**Placement**: Phase 1

## Lore

The Marble empire has spent most of it's history isolated from the rest of planet Weissblatt's continents. This is in no small part due to *Stella Mountain*, the mountain range located at the northern isthmus of the peninsula. Although nowadays navigable and a well-known tourist spot for it's beautiful landscapes, it is said that Stella Mountain reaches so far into the sky that it frequently catches incoming shooting stars. During the Asura incident, it happened to be the chosen vacation spot of Kleene Cognara, Elise Cantor and Babel Memto right as they crash landed alongside Dr. Asura following the destruction of Delfid.

## Author's Notes

This zone has more or less been born out of it's assets. Think of it as a Green Hill archetype with large vertical scale under a starry sky as incoming shooting stars form craters on the ground.

## Elements

- Piggy Tanks
- Breakable walls
- Hanging Ropes
- Low-gravity sections

## Ideas/Goals

- Act one as simple introduction to the mechanics
- Ascending geometry
- non-punishing
- mountain climb
- Serpentine-like structure
- Hidden cave w/ Equinox mural at the wall
- (Meteorite impact => Craters in the ground)

## Moments/Sequence

### Act 1

1. Player starts on a crystal altar on an open field
2. Player explores the environment and finds <++>
x. Player encounters a plateau with a giant turnip

### Act 2

1. Player climbs a steep rift/tower and sees "a way forward" alongside the wide-open skybox
2. Meteorite impact reveals an underground cave
99. Player ends on a plateau jumping into Dr. Asura's impact crater

### Act 3

1. Boss Fight against Dr. Asura inside his impact crater
2. Boss defeated => Crystal altar reaches out of ground w/ portal teleported on top
3. Portal leads to CCW

=== In ''Sentinels of Yuko'' ===
# Stella Mountain Zone (Yuko)

**Author**: Zibon "PixL" Badi, Victor "NotablyPrettyCrazy"
**Mapper**: <TBD>
**Canon**: Yuko, Delfid (original)
**Placement**: Late campaign

## Lore

The Marble empire has spent most of it's history isolated from the rest of planet Weissblatt's continents. This is in no small part due to Stella Mountain, the mountain range located at the northern isthmus of the peninsula. It is believed by the Marble empire's astrologers that Stella Mountain reaches so far that all shooting stars in the sky eventually end up there.

Although a mystery wanting to be solved, during the times of the Yuko wars this mountain range was still considered insurmountable. A few brave souls have attempted to conquer it, usually to never be heard from again. Shogun Yuko somehow managed to create a secret hideout somewhere on there where the ancient scrolls are probably located.

## Author's Notes

It's concept is based on the Delfid canon's Stella Mountain Zone, although with a few notes regarding the Yuko canon:

There's no civilization on here, so navigating Stella Mountain's unaltered natural landscape is a lot more dangerous -> we can make this version of Stella Mountain a lot harder.

Regardless of whether we're doing so for Delfid, Stella Mountain's stratospheric height justifies some light space elements, such as low gravity sections

## Gameplay Ideas

- Weather-based obstacles
- No civilization yet => Dangerous terrain

## Moments/Sequence

- Fight against Ganbaatar

Equinox Gate

2025-09-05T19:33:04Z

Nyamoru: /* Concept draft */

''Equinox Gate'' is a volcano featuring a launch base built by [[Dr. Asura]]. The name is derived from it's launch base, which requires the Enlightenment Crystal to be placed inside it to function during the ''Equinox''.

== Concept draft ==
<pre>
# Equinox Gate Zone

**Author**: Zibon "PixL" Badi
**Mapper**: \<NONE\>
**Canon**: Delfid
**Placement**: Phase 2

## Lore

Hidden inside a volcano, Dr. Asura prepared a launch base for the *Equinox*,
a rare alignment of Weissblatt's six moons that allows him to utilize the
Chakra Shards' magic for his own purposes.

After the player defeats Patsy Toyfeller during the campaign, MARA steals
the contract to Patsy's soul to lure them into here and use the Chakra
Shards to fuse Weissblatt with the underworld.

## Author's Notes

It's a magic tech launch base inside of a volcano. May contain traces of a
race against MARA, although the difficult parts should be reserved for
*The Underworld*. The second stage of this is intended to be the boss fight
against MARA, with an optional retreat of theirs into the underworld,
should the player have collected all seven Chakra Shards up to this point.

## Themes/Aesthetics

- Volcano
- Launch base/Sci-fi
- Slight dashes of tropical
- Hectic/Hasty gameplay
- Downward spiral/descent into crater

## Elements

- Lasers
- Moving bridges
- Lava
- Pools
- Falls
- Fans/Wind tunnels

## Ideas

## Sequence

0. <++>

## Act 2

1. Boss fight against MARA
2a. (If NOT all Chakra Shards)
1. Bridge raises
2. player exit
3. Game end
2b. (If all Chakra Shards)
1. Volcano revealed to be a trap
2. Glenz reactor activates -> Portal to underworld appears
3. Player jumps into portal
</pre>

== In ''The Asura Incident'' ==

=== Zone 1 ===
In zone 1, the player chases [[MARA]] across the volcano, first from the outside then from the inside.

=== Zone 2 ===
[[File:Glenz-reactor-concept.png|thumb|Concept art for Equinox Gate 2 titled "The Glenz reactor"]]
Zone 2 starts where Zone 1 left off and the player is locked inside the capsule to fight MARA.

After MARA is defeated, the entire arena is lifted downwards to reveal a laboratory underneath. Following a tunnel reveals a reactor-like structure featurng a pitch black portal overgrown with brambles, leading the player into [[The Underworld]].
[[Category:Location]]

The Underworld

2025-08-05T22:23:05Z

Nyamoru: /* Zones */

[[Category:The Asura Incident]]

[[Category:Location]]

'''The Underworld''' is the domain of Demons .
= Zones =
# The Underworld

**Author**: Zibon "PixL" Badi
**Mapper**: NONE
**Canon**: Delfid
**Placement**: Phase 3 (race against MARA & final boss)

## Lore

After being chased and confronted by our heroes, Mara pulls them into the underworld where it is uncovered that Mara has been possessed by none other
than the king of demons himself. These winding, non-euclidean caves being
the home domain of the demons, their absurd, alien structure appears
inherently hostile to any non-demonic visitors.

## Author's Notes

May contain traces of *Crystal Clockworld*, if we end up making that one.

## Themes/Aesthetics/Goals

### Underworld 99

- Abstract shapes
- Optical illusion and disorientation

### Underworld 66

- Roses & Brambles
- Gothic influences
- "Eclipse" from Berserk

## Elements

- Gravflip
- Frequent scenery change (UW99)

## Sequence

### Underworld 99

1. MARA dances akin to Shiva to mock the player
2. Race against MARA starts
x. <++>
99. Race ends on UW66 platform

### Underworld 66

1. Intro sequence
a. Player starts inside giant rosebud
b. MARA is released from his puppet (jumps up and explodes)
c. Outer rose petals fall away, revealing a wide cave made of soul plants w/ the re-assembled Enlightenment Crystal in the background
d. Inner rosebud opens, revealing KOTU
2. Boss fight against KOTU
3. After KOTU is defeated, music cuts out and a crystal altar reaches out of the ground
4. Player climbs the altar and a rumble followed by a white flash lead into the ending cutscene

== Underworld 99 ==

In '''Underworld 99''', the player chases [[Shtayn|MARA]] through an interdimensional passage.
== Underworld 66 ==

'''Underworld 66''' pits the player against the campaign's final boss [[Shtayn|KOTU]].
== Infinite Pathway==

'''Infinite Pathway''' is the 8th special stage in [[The Asura Incident]].

The Underworld

2025-08-05T22:21:08Z

Nyamoru: /* Zones */

[[Category:The Asura Incident]]

[[Category:Location]]

'''The Underworld''' is the domain of Demons .
= Zones =
# The Underworld

**Author**: Zibon "PixL" Badi
**Mapper**: NONE
**Canon**: Delfid
**Placement**: Phase 3 (race against MARA & final boss)

## Lore

After being chased and confronted by our heroes, Mara pulls them into the underworld where it is uncovered that Mara has been possessed by none other
than the king of demons himself. These winding, non-euclidean caves being
the home domain of the demons, their absurd, alien structure appears
inherently hostile to any non-demonic visitors.

## Author's Notes

May contain traces of *Crystal Clockworld*, if we end up making that one.

## Themes/Aesthetics/Goals

### Underworld 99

- Abstract shapes
- Optical illusion and disorientation

### Underworld 66

- Roses & Brambles
- Gothic influences
- "Eclipse" from Berserk

## Elements

- Gravflip
- Frequent scenery change (UW99)

## Sequence

### Underworld 99

1. MARA dances akin to Shiva to mock the player
2. Race against MARA starts
x. <++>
99. Race ends on UW66 platform

### Underworld 66

1. Intro sequence
a. Player starts on top of rosebud
b. MARA is released from his puppet (jumps up and explodes)
c. Outer rose petals fall away, revealing a wide cave made of soul plants
d. Inner rosebud opens, revealing KOTU
2. Boss fight against KOTU
3. After KOTU is defeated, music cuts out and a crystal altar reaches out of the ground
4. Player climbs the altar and a rumble followed by a white flash lead into the ending cutscene

== Underworld 99 ==

In '''Underworld 99''', the player chases [[Shtayn|MARA]] through an interdimensional passage.
== Underworld 66 ==

'''Underworld 66''' pits the player against the campaign's final boss [[Shtayn|KOTU]].
== Infinite Pathway==

'''Infinite Pathway''' is the 8th special stage in [[The Asura Incident]].

Equinox Gate

2025-08-05T22:05:09Z

Nyamoru: /* Concept draft */

''Equinox Gate'' is a volcano featuring a launch base built by [[Dr. Asura]]. The name is derived from it's launch base, which requires the Enlightenment Crystal to be placed inside it to function during the ''Equinox''.

== Concept draft ==
<pre>
# Equinox Gate Zone

**Author**: Zibon "PixL" Badi
**Mapper**: \<NONE\>
**Canon**: Delfid
**Placement**: Phase 2

## Lore

Hidden inside a volcano, Dr. Asura prepared a launch base for the *Equinox*,
a rare alignment of Weissblatt's six moons that allows him to utilize the
Chakra Shards' magic for his own purposes.

After the player defeats Patsy Toyfeller during the campaign, MARA steals
the contract to Patsy's soul to lure them into here and use the Chakra
Shards to fuse Weissblatt with the underworld.

## Author's Notes

It's a magic tech launch base inside of a volcano. May contain traces of a
race against MARA, although the difficult parts should be reserved for
*The Underworld*. The second stage of this is intended to be the boss fight
against MARA, with an optional retreat of theirs into the underworld,
should the player have collected all seven Chakra Shards up to this point.

## Themes/Aesthetics

- Volcano
- Launch base/Sci-fi
- Slight dashes of tropical
- Hectic/Hasty gameplay

## Elements

- Lasers
- Moving bridges
- Lava
- Pools
- Falls
-
- Fans/Wind tunnels

## Ideas

## Sequence

0. <++>

## Act 2

1. Boss fight against MARA
2a. (If NOT all Chakra Shards)
1. Bridge raises
2. player exit
3. Game end
2b. (If all Chakra Shards)
1. Volcano revealed to be a trap
2. Glenz reactor activates -> Portal to underworld appears
3. Player jumps into portal
</pre>

== In ''The Asura Incident'' ==

=== Zone 1 ===
In zone 1, the player chases [[MARA]] across the volcano, first from the outside then from the inside.

=== Zone 2 ===
[[File:Glenz-reactor-concept.png|thumb|Concept art for Equinox Gate 2 titled "The Glenz reactor"]]
Zone 2 starts where Zone 1 left off and the player is locked inside the capsule to fight MARA.

After MARA is defeated, the entire arena is lifted downwards to reveal a laboratory underneath. Following a tunnel reveals a reactor-like structure featurng a pitch black portal overgrown with brambles, leading the player into [[The Underworld]].
[[Category:Location]]

Desert Pit Zone

2025-08-05T22:04:53Z

Nyamoru: /* In The Asura Incident */

[[Category:The Asura Incident]]

{{Infobox fictional location}}

''Desert Pit Zone'' is a playable level in [[The Asura Incident]]. It is set in an unnamed desert filled with circus built by [[Patsy Toyfeller]].

== In The Asura Incident ==
## Themes/Aesthetics

- Desert (Outback?)
- Circus
- Launch base/Sci-fi
- Slight dashes of tropical
- Hectic/Hasty gameplay

## Elements

- Roc birds
- 8 Balls
- Ring swings
- Explosives (TNT)

## Ideas

### Act 1

- *Heat zones* - avoid the sunlight

### Act 2

- Tight ropes
- Trampolines
- Ring swinging

### Act 3

TRAIIINS!

## Sequence

### Act 1

1. Player starts in cave with a partly-shaded path outside
2. Player touches outside ground -> gets hurt -> avoid sunlight
99. Player arrives at circus tent

### Act 2

0. <++>

### Act 3

1. Player fights Patsy
2. MARA attacks beaten-down Patsy and dashes away
3. Level End

=== Act 1 ===
In act one, the player is mostly confronted with the hostility of the desert. Staying in the sun will drain the player's health.

=== Act 2 ===
Act two continues the desert theme, but introduces the player to disjointed elements of a circus.

=== Act 3 ===
Act three consists of the player discovering a deranged Patsy, who engages them in a boss fight on his self-built circus train.

Once Patsy is defeated, he lays down broken and weak while [[MARA]] appears and snatches the contract to Patsy's soul, leading the player towards chasing MARA through [[Equinox Gate]].
[[Category:Location]]

Toyfeller Corp

2025-08-05T21:54:31Z

Nyamoru: /* Toyfeller Park */

[[Category:The Asura Incident]]

''Toyfeller Corp.'' is the largest toy manufacturer on [[Planet Weissblatt]], founded by [[Fishbart Toyfeller|Dr. Fishbart Toyfeller]] and [[Patsy Toyfeller]].

= History =

Freshly after having graduated with a PhD in economics in 1977 WBC, [[Fishbart Toyfeller]] saw the career struggles of his quirky, but inventive brother [[Patsy Toyfeller]] and decided to jointly found Toyfeller Corp as a family business to keep the brothers afloat. After a breakthrough success fueled by Patsy's unique toy designs and a well-adjusted business strategy, Fishbart expanded the business by founding Toyfeller Park, a factory park which allowed Toyfeller Corp to mass-produce new toys on at rapid pace, which Patsy begrudgingly complied with despite creative concerns.

Between 1984 and 1992 WBC, sales of Toyfeller Corp.'s toys steadily declined due to ever-more prominent quality control issues. To address these problems as well as save on labor and operation costs, Fishbart directed Patsy to develop a system by which manufacturing and development of toys could eventually be handled entirely autonomously by the resident toys located at Toyfeller Park. Soon after the project was completed in 1997 WBC, Patsy silently disappeared.

= Toyfeller Park =

''Toyfeller Park'' is a playable level in [[The Asura Incident]], set in the eponymous main factory of Toyfeller Corp.
## Lore

What may look like a theme park wrapped around itself is in fact, the main
factory of the largest toy maker on Weissblatt. Perhaps it's because of
this, that Dr. Asura's demons like to take control of toys, as Toyfeller
discovered a way to make their toys develop and run their plants
autonomously. Due to this however, the park slowly evolved into a
disjointed mess of toy logic and it may not just be demons to beware of
here.

## Author's Notes

This is our industrial/lab zone, with some topsy-turvy toy bizarreness
thrown in for playfulness.

For theming reasons, feel free to use some of the weirder mechanics like
bouncing, goop, gravflip, etc. in more puzzling ways here.

For plot reasons, also feel free to make this one of the harder zones and
sequence it towards the end of the nonlinear act

## Themes/Aesthetics/Goals

- Toy-like silliness
- Industrial machinery
- "Bouncy and zaney" gameplay
- Lots of airborne gameplay
- Unpredictable physics
- Require the player adapt quickly

## Elements

### Toy

- Jelly floors/walls
- Lots and lots of springs
- Rollercoaster
- Gravflip
- Goop fluids
- Stepping on LEGO (it hurts)
- Crazy Stars
- 8 Ball riding

### Industrial

- Crushers (Horizontal & Vertical)
- Pistons (maybe for bouncy jumps)
- Steam vents & Pipes
- Acid pools
- Fans/Wind tunnels
- Conveyors

## Ideas

- Rollercoaster takes player across the map and introduces sections
- Jumping off a jelly pool at different heights
- Diving down a goop pool to different levels
- Show off INFOWAL1
- Red carpet of LEGO

## Sequence

## Act 1

1. Player enters on a rollercoaster taking them across the park
2. Rollercoaster ride ends throwing the player into a goop pool
3. Player finds themself in front of the factory complex, but the door is closed and front is paved with LEGO
4. Player jumps into the goop pool and dives underneath
5. Player encounters a Crazy Star, which likely explodes on a nearby <++>

- Player jumps off a piston to increase a jelly bounce and reach <++>

## Act 2

- gravflip
- passing INFOWAL1

Toyfeller Corp

2025-08-05T21:43:21Z

Nyamoru: /* Toyfeller Park */

[[Category:The Asura Incident]]

''Toyfeller Corp.'' is the largest toy manufacturer on [[Planet Weissblatt]], founded by [[Fishbart Toyfeller|Dr. Fishbart Toyfeller]] and [[Patsy Toyfeller]].

= History =

Freshly after having graduated with a PhD in economics in 1977 WBC, [[Fishbart Toyfeller]] saw the career struggles of his quirky, but inventive brother [[Patsy Toyfeller]] and decided to jointly found Toyfeller Corp as a family business to keep the brothers afloat. After a breakthrough success fueled by Patsy's unique toy designs and a well-adjusted business strategy, Fishbart expanded the business by founding Toyfeller Park, a factory park which allowed Toyfeller Corp to mass-produce new toys on at rapid pace, which Patsy begrudgingly complied with despite creative concerns.

Between 1984 and 1992 WBC, sales of Toyfeller Corp.'s toys steadily declined due to ever-more prominent quality control issues. To address these problems as well as save on labor and operation costs, Fishbart directed Patsy to develop a system by which manufacturing and development of toys could eventually be handled entirely autonomously by the resident toys located at Toyfeller Park. Soon after the project was completed in 1997 WBC, Patsy silently disappeared.

= Toyfeller Park =

''Toyfeller Park'' is a playable level in [[The Asura Incident]], set in the eponymous main factory of Toyfeller Corp.
## Lore

What may look like a theme park wrapped around itself is in fact, the main
factory of the largest toy maker on Weissblatt. Perhaps it's because of
this, that Dr. Asura's demons like to take control of toys, as Toyfeller
discovered a way to make their toys develop and run their plants
autonomously. Due to this however, the park slowly evolved into a
disjointed mess of toy logic and it may not just be demons to beware of
here.

## Author's Notes

This is our industrial/lab zone, with some topsy-turvy toy bizarreness
thrown in for playfulness.

For theming reasons, feel free to use some of the weirder mechanics like
bouncing, goop, gravflip, etc. in more puzzling ways here.

For plot reasons, also feel free to make this one of the harder zones and
sequence it towards the end of the nonlinear act

## Themes/Aesthetics/Goals

- Toy-like silliness
- Industrial machinery
- "Bouncy and zaney" gameplay
- Lots of airborne gameplay
- Unpredictable physics
- Require the player adapt quickly

## Elements

### Toy

- Jelly floors/walls
- Lots and lots of springs
- Rollercoaster
- Gravflip
- Goop fluids
- Stepping on LEGO (it hurts)
- Crazy Stars

### Industrial

- Crushers (Horizontal & Vertical)
- Pistons (maybe for bouncy jumps)
- Steam vents & Pipes
- Acid pools
- Fans/Wind tunnels
- Conveyors

## Ideas

- Rollercoaster takes player across the map and introduces sections
- Jumping off a jelly pool at different heights
- Diving down a goop pool to different levels
- Show off INFOWAL1
- Red carpet of LEGO

## Sequence

## Act 1

1. Player enters on a rollercoaster taking them across the park
2. Rollercoaster ride ends throwing the player into a goop pool
3. Player finds themself in front of the factory complex, but the door is closed and front is paved with LEGO
4. Player jumps into the goop pool and dives underneath
5. Player encounters a Crazy Star, which likely explodes on a nearby <++>

- Player jumps off a piston to increase a jelly bounce and reach <++>

## Act 2

- gravflip
- passing INFOWAL1

Toyfeller Corp

2025-08-05T20:31:47Z

Nyamoru: /* Convert Toyfeller Park concept back to draft form */