I'm going to hang this U.S inspired Miku flag I made outside my house. Will update you all in like 10 days Feel free to download it if you want (Using @majin_kz's miku model)

This song made my day, thank you

LOVE THE SWORD, I CAN WHACK PEOPLE WITH IT

🫡

☝️

☝️

In a perfect world, VRChat would fully support its creator ecosystem with structured, beginner-first tools and systems. Documentation would be visual and contextual, with every SDK and Udon feature explained like the reader has zero coding experience. Every section would include images, GIFs, short videos, and real use cases for every section. Yes, EVERY section. No jargon, no assumptions. New developers would be onboarded through guided learning tracks based on creator type: world, avatar, or programming, external; built directly into the Creator Companion. Currently what you have is *ok*, but needs WAY more information and sections. No more hunting across random Discords, videos, or GitHub gists to learn the basics. External tool and API creators would have a clear, accessible approval pipeline. You could submit your tool, explain what it integrates with, and get an official response: approved, denied, or revise; with a unique tracking ID and public status. Approved tools would be listed somewhere visible, helping others know what’s safe and supported. No more guessing if you're violating the TOS or waiting in fear of takedowns with zero communication. TOS updates would be transparent and human-readable, with changelogs, summaries, and real-world examples showing what’s allowed. Creators need clarity, not legal ambiguity. And finally, there would be a way for asset and tool creators to make money directly on the platform through verified listings, storefronts, or a marketplace integration

As someone who had to work with a team on making VRC assets: - The documentation is severely lacking. It is outdated, poorly structured, missing a lot of context, and has almost no visual flow. It needs to assume the reader has never touched code before and guide them step by step with clear explanations and visual examples. - There is no good onboarding process for new Udon or SDK developers. The learning curve is massive, and I’ve had to create entirely custom documentation just to train my own team. - Creators are afraid to innovate because the terms of service are unclear and can be changed on-a-dime. There is no official way to request pre-approval or track what is and isn’t allowed, and takedowns happen without much examples of what IS allowed. - The knowledge base is fragmented. Information is scattered across Discords, forums, official documentation, unofficial documentation, YouTube videos, and random GitHub repos. There is no central, official, or reliable place to learn. - There is also no way for asset creators to make money directly through the platform. We want to build with and for VRChat, and we want to make money doing it, but right now there’s no support, infrastructure, or path for that to happen in a sustainable way.