I hate visual scripting*

• (Expression 2) Whole ass PvP/Competitive gamemodes like Control Points / Supraball-something / etc
• (Expression 2) "Shader" library that draws fractals, Raymarches stuff or just trace-scans a photo (with water reflections, texture sampling, world-wrap, debanding and supersampling)
• ...
• (Starfall) A couple 2D multiplayer games on a screen, where people can gather around and play them
• (Starfall) A cat png that chases you, flips you off, drops a bunch of metal pipes on top of you and runs away
• ...

"Play" Resonite.

• All nodes exist in 3D space and everyone can see them
• You can collaborate on scripts together, or just help someone understand stuff
• Nodes can be hidden away (into GameObjects)

• You can upload anything from your PC and it just works
  • Models, Images/Textures, Sound Effects, Text Files, etc
• You can control any property you want:
  • Set the model material, change the shader, move stuff around, parent/unparent, etc
    • Yes, that means every avatar is "constructed" in-game, maybe even by multiple people, one person is importing stuff, someone else is configuring materials, and another dood is plucking boogers while making node logic so the avatar farts when it walks
• You have a personal inventory, where you can save any creation (and it has folders)

• Multi-tools
• A 2D plane that's snaps nodes onto itself for ease of scripting (yes, it's a tool made for visual scripting in the same visual scripting engine)
• Working minigames (sudoku/uno/...)
• Equipable Half-Life HUD
• and a fully-working Tardis...

Foundations

Ideas for the Future

• Node Search
• Tooltips for nodes
• In-editor Node3d WorldPanel rendering, if even possible
• SceneTree Explorer (to grab properties of anything, from anywhere)
• Multiplayer support
• A 2D Grid to snap nodes to
• Packing/Unpacking nodes into GameObjects (same as Pack/Unpack in Protoflux)
• Custom panels for some nodes, so that they are more compact (+, -, *, sin, ...)
• VR Support, lol

S&box Reflection or "How To Tear Your Balls Off"

TypeLibrary.GetType<Drive<float>>().TargetType

TypeLibrary.GetType<Drive<float>>().TargetType == typeof(Drive<>) // true
TypeLibrary.GetType<Drive<float>>() == TypeLibrary.GetType(typeof(Drive<>)) // and this is, also, true

TypeLibrary.GetType(typeof(Drive<>)).CreateGeneric<Node>([typeof(float)], ...);

TypeLibrary.GetType<Drive<float>>().GenericArguments

TypeLibrary.GetType<Drive<float>>().GenericArguments // [ typeof(T) ] (name of the generic argument)
typeof(Drive<float>).GetGenericArguments() // [ typeof(System.Single) ] (actual generic argument, from a closed generic type)

public override Type[] Generics => [typeof(T)];

I have yet to see a more disorganized math library

// Awful
public static int Pow(this int x, int exponent) => (int)Math.Pow(x, exponent);

// Awful, Not whitelisted
public static int Pow(this int x, int exponent) => (int)System.Numerics.BigInteger.Pow(x, exponent);

I almost bounced back to hating frontend

Weak-ass IEnumerable<T>

public static IEnumerable<(int Index, T Item)> Enumerate<T>(this IEnumerable<T> ie)
{
    var max = ie.Count();
    return Enumerable.Range(0, max).Zip(ie);
}

public static void ForEach<T>(this IEnumerable<T> ie, Action<T> action)
{
    foreach (T item in ie) action(item);
}

• `Node` Name/Description/etc. implementations
  • The less code you have to write to make a new node type, the better
• Reimplement most nodes with generic type constraints (via "where"), things like Add<T>, Clamp<T>, etc
• Lack of comparison, bitwise and vector nodes, more wiremod feature-parity
• A utility screen panel that shows you that you have some panel focused
  • People get stuck in `Constant<T>` TextEntries, it's hilarious
• And a general API pass, because it's ass