Motivation

History

This project aims to revive Pyoncord's original goals. Before Bunny superseded it, Pyoncord had several key objectives:

• Lazy modules fetching/patching from Metro (the main one)
• First-party focused (plugins)
• Native modules/patching

I started this project (Pyoncord) not to solve a problem, but as a proof-of-concept to tinker with modding. These goals required building the mod from scratch, so I never intended it to compete with other mods or gain users.

The primary goal was implementing lazy modules fetching/patching. Once I discovered a way to achieve this for Vendetta's architecture without creating an entire mod, I integrated it into Bunny and discontinued Pyoncord, as Bunny had served its main purpose.

Around Q3 2024, my family faced a severe crisis that disrupted my normal life. This forced me to pause Bunny's development, though I continued providing maintenance updates as long as I could touch my laptop.

As I adapt with my situation, I wanted to continue work on Bunny. However, its architecture—inherited from Vendetta—proved challenging, especially to work with backwards compatibility. The emergence of newer client mods also dampened my motivation. From its poor UX to codebase full of bandages, Bunny seemed unfixable.

I considered abandoning Bunny and letting other client mods take over. Another option was to drop backwards compatibility and rebuild Bunny's architecture, but this is actually a lot of work that starting a rewrite seemed easier. Yet with other works-in-progress out there, a rewrite felt redundant unless Bunny could offer something unique.

This sparked the idea to revive this project under the codename Wintry. Its first-party focus would set it apart—at least until other mods adopt a similar approach. Inspired by Vencord, Wintry aims to deliver a similar user experience.

You might have heard of “Wintry” before—it was originally proposed as Bunny's rebrand. Though that rebranding was cancelled, the name lives on as this project's codename.

Why first-party plugins?

• Everything is installed out of the box – just toggle it on, and it's ready to use.
• Fully safe and vetted – all plugins are verified, so there’s no need to worry about security risks.
• Always works – since all plugins are first-party, there’s no risk of a developer abandoning their project and avoid the existence of a fork of a fork of a plugin. If something breaks, it can be fixed quickly by anyone.
• Better support – because we control all plugins, we can provide proper support for them.

Despite these advantages, the system has its drawbacks:

• More effort for plugin developers – instead of writing a plugin as a separate project, developers have to clone the entire project and contribute directly.
• Slower external innovation – while anyone can contribute, independent developers can’t create and distribute plugins separately, unlike third-party systems.
• Bloat – including a broad range of plugins in the main project could lead to unnecessary bloat for users who don’t need them.
• Limited variety – since all plugins must go through the main project, users don’t get the same variety that an open third-party marketplace might offer.

If the disadvantages outweigh the benefits for you, you may want to explore other client mods. Wintry isn't meant to replace existing client mods.