To a UnityFreak, the default Editor layout is not acceptable. It’s a starting point. They have four monitors: one for Scene view, one for Game view, one for a custom tools window they built themselves, and one for the Profiler running in real-time (just to feel alive).
Writing Editor Scripts for Fun While other developers write code for their games, UnityFreaks write code for their workflow. They build nested prefab variant managers. They create batch renaming tools with regex support. They script a window that automatically generates level blockout geometry from CSV files exported from Excel. Then they lose interest in the game itself and spend three more days perfecting the tool.
The ultimate status symbol in the UnityFreak community is a completely custom Editor experience: a toolbar that plays a sound every time you hit Play, a Scene view outline that color-codes objects by layer priority, and a custom inspector for every MonoBehaviour that explains, in sarcastic tooltips, why the variable shouldn’t be public.
A UnityFreak does not buy shaders from the Asset Store. They write them in HLSL, hand-optimizing instruction limits. They know that a shader that compiles to 110 ALU instructions is "bloated." They use Shader Graph for prototyping, but for production, they revert to code. They understand that every texture sample costs time and every branch in a fragment shader is a potential stall. unityfreaks
While most players see a game as a finished product, a UnityFreak sees raw potential. "What if I climb that mountain?" "What if I mod this texture into a potato?" "What if I reverse-engineer this physics glitch to launch a tank into orbit?" We don’t just consume content; we interrogate it.
You might read this and wonder: why? Why spend hundreds of hours optimizing a game that will only be played by three people on Itch.io? Why write a custom inspector for a variable that could have just been public? Why embrace the chaos, the broken builds, the asset store debt, and the endless cycles of refactoring?
Because it’s fun. Not the polished, user-friendly fun of a finished game. The raw, jagged, deeply satisfying fun of making something from nothing inside a system that is just barely holding itself together. Unity is an engine of contradictions: it’s powerful yet clunky, intuitive yet arcane, beloved yet despised. To be a UnityFreak is to love it not despite those contradictions, but because of them. To a UnityFreak, the default Editor layout is not acceptable
When a UnityFreak finally builds their game—whether for a game jam, a Steam release, or just a private share to a friend—and they see their shader compile, their jobs system run smooth, and their custom Editor tabs all in place, there is a fleeting moment of perfection. Then they close the build. They open the Profiler. And they find one more thing to optimize.
That’s the freakish beauty of it. The project is never done. The engine is never mastered. But the process—the glorious, broken, obsessive process—is the whole point.
So if you find yourself at 3 AM, staring at a bright orange error log, muttering "one more fix" to an empty room… welcome. You are among the UnityFreaks. A UnityFreak does not buy shaders from the Asset Store
Now go clean up your Prefabs. And for God’s sake, stop calling GameObject.Find in Update().
Could you clarify what you mean by "create feature looking at unityfreaks"? For example:
In the meantime, here’s a short written feature outline assuming UnityFreaks is a game development community or asset provider: