Here's the resources I have written:
#pragma multi_compile_instancing
// IFF the scale of the model is the same for all axes (x, y, and z are ALWAYS the same number), put this next line.
// If not, do NOT use this next line. This is an optimization for the instancer, but it requires a uniform scale.
#pragma instancing_options assumeuniformscaling
Making custom tiles in Rain World requires some knowledge about how tiles actually work in the first place.
If you are reading this line of text right here right now, this document is still in the "my personal notes from observation" stage.
That is, it is primarily written by me for me and may contain strange phrasing, be oddly condescending, or otherwise be a bit rough around the edges.
If this is a public document, it means I think it's good enough to release for now, but it may still have inaccuracies or misleading/misinterpreted information (this is based on both what I read in documents + the lingo code for the level editor).
Level image files contain highly specific data that has a range of meanings both to the game during runtime (on the CPU thread) and to the level shader itself. The colors seen in levels can be slightly confusing, so this document relays them all.
0 to 255 like most people are used to, not 0.0 to 1.0 as seen in shaders). This way it's easier for everyone to understand.
This is NOT for modifying existing sounds! To see how to modify existing sounds, visit Rain World Modding Wiki: Modification Files.
Sounds exist in-game abstractly, that is, rather than you the modder dealing with AudioClip/AudioSource instances (belonging to Unity), you will instead use sounds via their abstract SoundID class, which, like all other ExtEnum<T> types, contains a unique string ID of your choosing.
Consider creating a new class in your mod, like so:
public static class Sounds {
This addresses quirks with the lighting engine and how it interacts with custom shaders.
Futile is a bit of a frankenstein's monster when it comes to iteroperability with base Unity systems; while Unity shaders work, the behavior is overshadowed by Futile's layer system. This caused me to spend more hours than I care to admit trying to figure out why an unlit holographic/additive shader I wrote was casting shadows, and I want to prevent that pain for anyone else who may be reading.
This section covers shader information. It is directed towards those that already understand fundamental shader concepts.
ZWrite and ZTest commands (among less common others) are ignored. Futile does not have a depth buffer.1
| // Just throw this macro into keymap.c | |
| // This macro allows declaring colors just like one would declare their keymap. It is ordered identically and allows a 1:1 | |
| // mimic of the keymap macro when declaring your colors. | |
| // | |
| // Here is the default layout (I use this as a frame of reference): https://configure.zsa.io/moonlander/layouts/default/latest/0 | |
| // Button indices start from the top left of the left keyboard half (= on the default layout), going down. Once it hits the bottom, it goes right one space and continues that way. | |
| // | |
| // When it reaches the thumb buttons, it starts at the top most long thumb button (space on the default layout) then continues along the long buttons | |
| // (on the default layout, it is space => backspace => left windows). After these three, it does the red button. |
Within this folder is a prefab for the wisp. It comes with default settings.
It's easy! The object comes as a prefab. Literally just drag n drop into your avatar and that's it. Set it up with a physbone if you wanna, or leave it hanging there.
| LOCALIZATION CORE DUMP :: INIT CYCLE COMPLETE, DUMP FOLLOWS | |
| findKuName.txt | |
| Fallen Friend | |
| findKuKuFallsUpdateDescription.txt | |
| Ku has fallen. Find her and make your way home. | |
| findKuObjective.txt | |
| Find Ku |