RedM Scripts, RedM Resources, VORP Scripts, RDR2 Mods, Developer Tools & Documentation

BRK Scripting Studios builds RedM scripts, RedM resources, VORP scripts, RDR2 mods, developer tools, documentation, VORP resources, Lua utilities, roleplay systems, world content, and original games.

A lot of BRK started with a simple pattern: I would be building or running something, realize the tool or system I wanted either did not exist or did not work the way I thought it should, and decide to make it.

That has grown into more than a collection of RedM scripts.

BRK now covers RedM scripts, RedM resources, VORP scripts, RDR2 mods, developer tools, documentation, free tools for server owners, configuration help, UI systems, animal and horse gameplay, hunting and wilderness systems, roleplay utilities, maps and world content, server development, and original game projects.

If you found BRK while searching for RedM scripts, RedM resources, VORP scripts, RDR2 mods, Red Dead Redemption 2 roleplay, an RDR2 multiplayer mod, a Lua config checker, RedM developer tools, documentation, serious RP, horse games, western games, or something considerably more specific, there is probably a reason those subjects all meet here.

Framework and integration support varies by resource. See Framework Compatibility for the current overview. Each resource's own documentation is the authority for what it currently requires.

Why I Build Things the Way I Do

I'm Akrania, also known as BlakelyRachelle, the developer and owner behind BRK Scripting Studios.

I am a RedM developer, server owner, gamer, compulsive stuff builder, and the person who will probably turn one missing feature into an entirely new project because I decided the existing solution was not good enough.

BRK is heavily shaped by actually using what I build.

I don't develop scripts only in an empty test environment and assume that means they are ready for somebody's live server. I build around real server problems, real roleplay, actual configuration needs, and interactions between resources.

Customization Should Not Require You to Be a Programmer

One of my strongest development priorities is making BRK resources highly configurable without requiring the person running the server to know Lua.

Server owners should be able to make a resource fit their community without rewriting its code. That means being able to adjust locations, items, jobs, permissions, restrictions, timings, prices, features, integrations, behavior, difficulty, and optional systems through clear, understandable and explained configuration.

If you know how you want your server to work, you should not have to become a programmer just to make reasonable changes. If you are a developer, BRK also provides extensive exports, events, integrations, and compatibility options so you can extend resources and connect them to your own systems.

That flexibility is also why the BRK Config Syntax Checker exists.

A small syntax mistake can stop an otherwise working resource from loading. A missing comma, bracket, quote, or incorrectly placed value can be difficult to find if you do not work with Lua regularly.

The Config Syntax Checker is designed to make those problems easier to understand and fix.

You do not need to know Lua to use it. The tool can inspect configuration files, identify syntax and structure problems, show where an error is located, explain what went wrong, and help correct it. It also includes additional knowledge of BRK configuration structures for improved accuracy with BRK resources while remaining useful for general Lua files from other RedM resources.

I Don't Believe in Releasing Half Working Scripts

BRK's current portfolio is smaller than I ultimately intend it to be, and that is deliberate.

I stress test resources heavily before I am willing to relese them.

I would rather spend longer finding problems before release than build a large catalog by turning customers into the final testing stage.

That means repeatedly testing interactions, configuration combinations, strange player behavior, failure conditions, framework behavior, restarts, resource dependencies, integrations, and the less interesting edge cases that are usually what actually break on a live server.

I don't believe in selling half working scripts.

Highly Configurable. Highly Maintained. Consistent Support.

Highly configurable means the resource should adapt to different server styles instead of requiring every server to adapt itself around the resource.

Highly maintained means release is not the point where I stop caring about it. Bugs get fixed. Compatibility changes get investigated. Systems get refined. Older work gets revisited when something genuinely needs improvement. Free BRK resources are treated with the same level of maintenance as paid ones and that will always be the case.

Consistent support means if something isn't working, I don't want the answer to be silence.

While BRK's dedicated ticket system is still being built, my DMs are intentionally open for support. If you find a problem, are confused about a configuration option, or believe something is not behaving as intended, you can reach out.

That workflow will become more organized when the support bot is finished, but the underlying principle is staying the same: buying or downloading a resource should not leave you stranded with it.

Suggestions Actually Matter Here

Feature requests and suggestions are taken seriously.

Useful suggestions do not get thrown into a channel and forgotten.

A significant amount of BRK development has been shaped by people actually using the resources and saying, "This would work better if..."

So far, I have a very strong track record of taking good feedback and finding a way to implement it, even when the implementation comes later than the original request.

That conversation between development and actual server use is something I intend to keep.

Fair Pricing Matters Too

I do not believe RedM pricing has to become absurd just because a resource is specialized.

BRK resources are priced around the work, scope, polish, documentation, integration, and usefulness behind them.

Some projects are paid.

Most are free.

The goal is not to be the cheapest script store.

The goal is fairly priced, not cheaply made.

Games Should Give People Things to Do, Not Just Things to Click

The same philosophy carries into my game development and roleplay design.

I like systems that overlap.

A profession should connect to the economy. Animals should have more purpose than being scenery. Horses should feel like individuals rather than interchangeable vehicles. Businesses should create interactions between players. Hunting should lead somewhere. Owning something should create decisions. Progression should open possibilities instead of simply making numbers larger.

I like worlds where players can decide what kind of life they want to build.

That is true whether I'm working inside RedM, designing Indestructible RP, building a horse system, experimenting with a tiny merge game, or planning a much larger original life sim/RP world (spoiler alert).

Immersion matters.

So does fun.

Making something slower, harder, or more tedious is not automatically more immersive.

The systems should create stories.

BRK develops RedM resources primarily around the VORP Core ecosystem, with broader compatibility added where it can be properly supported and tested.

RedM servers vary enormously.

A serious roleplay server, economy focused community, supernatural, casual western server, animal heavy ranching server, development environment, and heavily customized private framework can all want completely different behavior from the same basic concept.

BRK resources are designed with that flexibility in mind.

Configuration is not treated as an afterthought. When a system can reasonably be optional, adjustable, restricted, extended, or integrated differently, I generally want the server owner to have that choice.

Current and developing BRK work includes:

• RedM gameplay scripts
• Mainly VORP compatible resources
• animal interaction systems
• horse and stable systems
• hunting and wilderness gameplay
• ranching and livestock systems
• player communication
• chat systems
• jobs and professions
• business systems
• roleplay utilities
• minigames
• UI and menu systems
• notifications
• server administration
• developer utilities
• configuration tools
• shared integration utilities
• world interactions
• maps and environmental content
• framework compatibility
• server owner quality-of-life tools

VORP is the primary fully tested environment for much of BRK's current catalog, but planned development includes broader framework and open-source compatibility options where they make sense and where they can be validated properly.

I would rather label something honestly as experimental or untested than put six framework logos on a release page and hope for the best lol.

Explore

Browse released and developing BRK resources.

Resources built and tested around VORP Core.

Free scripts, utilities, and tools.

Installation, configuration, dependencies, compatibility, exports, troubleshooting, and updates.

Not everything useful needs a price attached to it.

BRK maintains free RedM scripts and utilities alongside premium development.

Current free work includes projects such as BRK Chat, BRK Fish Filet, development tools, browser based BRK Labs utilities, and other public resources.

The point is not to use free releases as crippled demos for paid versions.

When something is released as a functional free BRK resource, it should still be something I am proud to put my name on.

If you're looking for free RedM scripts, free VORP resources, Lua tools, configuration help, or server owner utilities, start with the Free Resources and BRK Labs sections.

BRK Labs is the browser based tools side of the studio.

Some tools are aimed directly at developers.

Others are deliberately built for server owners who do not consider themselves programmers.

The common idea is removing tedious or unnecessarily technical parts of working with RedM resources.

Config Syntax Checker

The BRK Config Syntax Checker is a free browser based Lua configuration checker designed with RedM resource configuration in mind.

It can help identify:

• Lua syntax errors
• broken configuration tables
• missing commas
• mismatched brackets
• misplaced values
• malformed strings
• invalid configuration structure
• errors in config.lua
• common RedM configuration problems
• BRK-specific configuration mistakes

The checker identifies where problems occur and can provide corrections instead of simply returning an unhelpful parser error.

It includes additional awareness of BRK resource configuration structures for improved accuracy with BRK scripts, while still being capable of checking general Lua files from other resources.

You do not need to know Lua to use it.

If you are searching for a RedM config checker, VORP config checker, Lua config syntax checker, RedM config validator, or a way to figure out why a config.lua stopped working after you edited it, this is exactly the problem the tool was created to solve.

Webhook Embed Lab

The BRK Webhook Embed Lab is a visual Discord webhook and embed builder.

It is designed for people configuring RedM resources, server logs, staff systems, transaction logs, notifications, roleplay logs, administration tools, and other systems that send information to Discord.

Instead of repeatedly editing Lua, restarting a resource, firing an event, and checking Discord just to see whether the layout looks right, the tool lets you construct and preview the embed visually.

Use it for:

• RedM Discord webhooks
• Discord embed design
• server log formatting
• webhook colors
• fields and descriptions
• staff logs
• transaction logs
• roleplay logs
• resource notifications

Console Banner Lab

The BRK Console Banner Lab helps create formatted console banners for RedM, FXServer, and script resources.

It can be used for:

• resource startup banners
• FXServer console headers
• RedM console branding
• ASCII-style console text
• formatted status messages
• script startup output

It is meant to remove the trial-and-error involved in manually spacing and rebuilding console text.

More BRK Tools

BRK Labs will continue expanding as I run into problems that are annoying enough to turn into tools.

Future utilities will continue following the same rule: solve an actual development or server-owner problem instead of existing just to fill a tools page.

A lot of RedM server ownership lives in the uncomfortable space between "I am not a developer" and "I still have to edit Lua files."

BRK documentation and tools are designed with that reality in mind.

Common subjects covered across the site include:

• RedM script installation
• VORP resource setup
• Lua configuration
• config.lua
• server configuration
• framework compatibility
• dependencies
• exports
• events
• integrations
• SQL requirements
• webhook configuration
• script troubleshooting
• resource startup errors
• update instructions
• configuration examples

BRK resources aim to expose meaningful options clearly while keeping implementation details out of the way unless somebody actually needs them.

For developers and advanced server owners, deeper integration information such as exports, events, dependencies, compatibility surfaces, and implementation guidance is documented separately.

Animals are one of BRK's largest areas of interest.

Red Dead Redemption 2 already has an unusually rich animal world, and RedM gives server developers room to make those animals matter far more to actual gameplay and roleplay.

BRK's current and planned animal-focused work spans:

• horse systems
• stable systems
• animal care
• livestock
• ranching
• hunting
• wilderness gameplay
• pets
• playable animals
• breeding
• animal behavior
• animal ownership
• veterinary-style gameplay
• ranch professions
• wildlife interaction
• animal transport
• working animals

BRK Critter Care

Released

BRK Critter Care expands animal and livestock interaction for RedM.

Gameplay includes systems such as milking, shearing, brushing, washing, animal tools, livestock interactions, minigames, configurable job access, durability, and compatibility behavior.

It is designed for ranching, farming, animal-care professions, homesteads, wilderness communities, and servers that simply want animals to be more interactive.

BRK Resourceful Ranger

Released

BRK Resourceful Ranger expands hunting and wilderness resource gameplay.

It is intended for hunters, wilderness characters, traders, survival-oriented gameplay, professions, and server economies where hunting should involve more than the default interaction loop.

BRK Stables

In Development

BRK Stables is being developed as a much larger horse ownership and stable system.

Planned areas include horse ownership, tack, equipment storage, custom coats, stats, behavior, wellbeing, training, bonding, aging, injury and care systems, horse deeds, theft and impound options, breeding, foals, ranch integration, working horses, wagons, and other systems intended to make horses a long-term part of a character's life.

The goal is not simply "another stable menu."

The goal is a deeper horse system where ownership, equipment, care, training, behavior, and player decisions matter.

Pets, Ranching & Additional Animal Systems

Planned / In Development

The longer BRK animal roadmap includes dedicated pets, ranching systems, animal rehabilitation, persistent livestock, breeding traits, herding, shelter and care, and other ways for animals to become part of server life rather than decorative NPCs.

Additional experimental concepts include playable animals and working-animal systems.

These systems will be released when they are ready, not because a roadmap says they have to ship on a particular date.

BRK also develops systems around the wilderness side of RedM.

That includes hunting, harvesting, animals, tools, professions, outdoor activities, resource gathering, and systems that can connect frontier gameplay back into a server economy or roleplay structure.

The goal is to create reasons to spend time outside of towns that go beyond grinding a repetitive route.

Wilderness gameplay can support:

• hunters
• trappers
• ranchers
• guides
• traders
• survival-oriented characters
• resource professions
• animal-focused jobs
• remote homesteads
• wilderness roleplay

Roleplay economies work better when jobs create interactions between players instead of existing only as isolated money loops.

BRK's current and planned work includes systems for:

• jobs
• professions
• businesses
• business management
• player-owned services
• dispatch and calls
• advertisements
• business hours
• auctions
• player stores
• economic interactions
• crafting and production
• specialization
• profession benefits

Planned systems such as BRK Business Bureau are intended to connect businesses, professions, communication, public information, and server administration in ways that give players more reasons to interact with one another.

BRK's larger server-development direction also includes custom store systems and other framework replacements designed around clearer configuration and more flexible location-based behavior.

Not every important system is a giant gameplay resource.

BRK also builds the pieces players interact with constantly.

That includes:

• RedM chat
• roleplay communication
• notifications
• menus
• minigames
• RP dice
• player prompts
• messaging systems
• administration interfaces
• interaction systems
• UI utilities

BRK Chat

BRK Chat is a free RedM chat system built for roleplay and server communication.

Development around BRK Chat includes configurable presentation, opacity, roleplay use, server communication, moderation support, direct messaging, logging, and integration with other BRK systems.

BRK Menu

BRK Menu provides a reusable Red Dead-style menu foundation used across BRK resources.

BRK Notify

BRK Notify provides shared player-facing notification behavior for BRK resources.

BRK RP Dice & Minigames

BRK also develops shared roleplay and minigame systems that can be reused by larger resources rather than rebuilding the same interaction every time.

BRK's server tooling extends beyond gameplay.

Projects include administration systems, development utilities, resource testing tools, compatibility helpers, shared infrastructure, configuration utilities, and tools intended to make running or developing a RedM server less frustrating.

BRK Admin

In Development

BRK Admin is planned as a free administration layer with VORP support and integration with other BRK systems.

Development includes public roster functionality, permissions, administrative tools, audit/logging concepts, and future web-based administration.

BRK Dev Tool

BRK's internal and developer-facing tooling includes resource restart management, testing utilities, entity and animation testing, placement tools, and systems intended to speed up RedM development.

BRK Launcher & Framework Development

BRK is also exploring deeper server-development tooling, including launcher work, server infrastructure, shared framework components, and longer-term ways to reduce unnecessary dependence on inherited systems where custom architecture makes more sense.

Public compatibility will remain broad where practical, while experimental or internal systems will be labeled honestly rather than marketed as finished products.

BRK development is not limited to Lua.

The studio has also released and worked on RedM world content including maps, YMAPs, location edits, and environmental additions.

Past and current world work includes locations around Strawberry, Emerald Ranch, Blackwater, McFarlane's Ranch, and other additions.

Longer-term asset work is expanding toward more custom props, furniture, food items, building pieces, structures, and other objects that can fit naturally into the Red Dead world.

The same standard applies here as with scripts: world content should feel like it belongs in the environment instead of looking obviously pasted on top of it.

If you arrived here searching for RDR2 mods, there is an important distinction.

BRK primarily develops for RedM, the multiplayer server platform used to create custom Red Dead Redemption 2 experiences.

Traditional RDR2 mods generally modify the single-player game.

RedM resources instead become part of custom multiplayer servers and can add or replace systems such as:

• roleplay
• jobs
• businesses
• custom economies
• animals
• horses
• ranching
• hunting
• user interfaces
• chat
• administration
• interactions
• maps
• server utilities
• custom gameplay

If you're looking for custom RDR2 multiplayer, Red Dead roleplay, western RP, or heavily modified Red Dead server gameplay, what you're looking for may actually be RedM.

If you're looking to play instead of build, continue to Indestructible RP.

If you're building a server, explore BRK's RedM resources and development tools.

A Serious RedM Roleplay Server Being Built for the Long Haul

Indestructible RP is an 18+ serious-roleplay RedM server currently under heavy development.

It is not being treated as a quick server launch, a temporary side project, or a collection of scripts thrown together until something feels playable. IRP is being built as a long-term roleplay world with its own identity, economy, systems, standards, community, and development direction.

A large amount of the server is still actively being designed, rebuilt, tested, and expanded. Some ideas will change. Some systems will grow into things that were not originally planned. Others may be simplified, replaced, or dropped entirely if they stop serving the world well.

That is intentional.

The priority is building something worth maintaining for years, not promising a giant feature checklist before the systems have earned their place.

Roleplay Comes Before the Grind

The core philosophy behind IRP is that gameplay systems should create roleplay opportunities, not replace roleplay with chores.

Jobs, businesses, professions, animals, hunting, law, crime, trade, travel, property, and the wider economy should give characters reasons to need one another, make decisions, build reputations, create conflict, and form relationships.

A mechanic is not automatically immersive just because it takes longer.

IRP takes serious roleplay seriously, but that does not mean every basic action needs to become a grind. Players should be able to participate in the world without spending hours doing repetitive tasks just to afford the right to roleplay.

Long-term goals should still matter. Wealth, businesses, property, status, specialized professions, and major accomplishments should feel earned.

The distinction is between meaningful progression and busywork.

A Player-Driven World

Indestructible RP is being designed around the idea that the most interesting stories should come from the people living in the world.

Staff can provide structure, systems, locations, events, consequences, and opportunities, but the server should not depend on staff manufacturing every important storyline.

Businesses should create relationships between owners, employees, customers, suppliers, competitors, and law.

Professions should make characters useful to one another.

Crime should create consequences and responses.

Law should create responsibility rather than simply authority.

Character decisions should have room to matter.

Two people should be able to spend months in IRP and come away with completely different stories because they chose different lives.

A rancher, horse trainer, doctor, outlaw, hunter, business owner, lawman, craftsman, wilderness character, trader, or ordinary town resident should not all feel like they are running through the same progression path with different labels.

Serious RP Without One Correct Way to Play

IRP is serious roleplay, but it is not meant to be a server where every character has to fit the same mold.

There is room for grounded drama, quiet everyday life, business rivalry, family stories, crime, law, wilderness characters, professions, ranching, animals, travel, conflict, humor, ridiculous situations, and the kind of harmless chaos that naturally happens when people spend enough time together in the same world.

Characters are allowed to joke, be weird, make bad decisions, tease one another, have embarrassing moments, get into petty arguments, or end up in situations that are genuinely funny. Goofing around is completely fine when it still makes sense for the characters and the world around them.

Drama, tension, consequences, emotional stories, and heavier roleplay are very welcome too. The point is not to force one tone.

Characters can succeed, fail, change direction, lose things, rebuild, make enemies, make families, or decide that their life's greatest ambition is owning an unreasonable number of horses.

The important part is treating the shared world, the situation, and the other people involved seriously enough that everyone can build on what happens.

Serious RP is about roleplay having weight and continuity, not about banning fun.

Economy Built Around People, Not Just Numbers

IRP is being developed around a player-driven economy where money matters, but money is not the entire game.

Businesses, jobs, services, production, trade, professions, and ownership should connect to the wider community instead of existing as isolated money loops.

The economy is intended to remain tighter and more grounded than the inflated economies common on many roleplay servers.

Major purchases and long-term goals should feel meaningful.

At the same time, basic participation in roleplay should not be reserved for characters who have spent the most time grinding.

The goal is an economy that creates interaction and progression without turning every character into a full-time wage calculator.

Jobs, Professions & Businesses With a Purpose

IRP is putting a lot of attention into the difference between having a job title and actually having something meaningful to do.

Businesses should need customers.

Professions should create useful services.

Leadership roles should carry responsibility.

Specialization can provide advantages, knowledge, opportunities, or access without arbitrarily preventing everyone else from interacting with the world.

Planned and developing systems cover areas such as player businesses, professions, services, public-facing jobs, crafting, trade, advertisements, business management, and other ways for characters to build a place for themselves in the economy.

Exactly how those systems work will continue evolving during development.

The important part is the direction: roles should generate RP between players instead of existing only to generate money.

Horses, Animals & Frontier Life

Animals are a major part of IRP's identity.

Horses in particular are intended to become more than transportation with different speed statistics.

BRK development around IRP is exploring deeper systems involving horse ownership, care, equipment, behavior, training, ranching, livestock, hunting, working animals, and other forms of animal-focused gameplay.

The same philosophy applies to wildlife and domestic animals: if they exist in the world, there should be room for them to matter.

Grounded animal roleplay is also welcome. Players may roleplay animals where it fits the setting without turning the world into supernatural or fantasy RP.

Specific animal systems are still evolving heavily and should be treated as development direction rather than promised launch features.

Law, Crime & a Different Kind of Mexico

Most of the world is built around serious consequences, law, institutions, character responsibility, and the expectations of a shared roleplay environment.

Mexico is intended to provide a deliberately different kind of space.

The direction is a more lawless region where institutional protection is limited or absent and characters can step into riskier styles of western roleplay.

That does not mean abandoning roleplay standards or treating the region as permission to grief other players.

It means the world itself operates differently there.

The exact systems and structure surrounding Mexico are still being developed and may continue changing as the server grows.

No Pay-to-Win

IRP is not being built around selling gameplay advantages.

Supporter and donation options are intended to remain cosmetic or otherwise non-pay-to-win.

Real-world spending should not determine who has the strongest character, the easiest progression, the best business, or the most powerful equipment.

If a character becomes successful in the world, that success should come from what happened inside the world.

Built Alongside BRK Scripting Studios

Indestructible RP is developed alongside BRK Scripting Studios. A lot of my RedM systems are built and tested with IRP in mind, which gives me somewhere to see how they behave as part of a real server instead of only testing them by themselves.

BRK develops reusable resources, tools, infrastructure, and gameplay systems. IRP is the environment where those ideas can meet one another under actual server conditions.

That matters because systems behave differently once real players begin combining them in ways no isolated test case predicted.

IRP gives BRK development exposure to real roleplay, real economies, real community behavior, real edge cases, and the practical problems that appear when multiple complex systems coexist.

At the same time, IRP benefits from development that is being shaped specifically around the kind of world the server is trying to become. Public resource requirements still live in each resource's own resource documentation and on Framework Compatibility.

The server is also part of a longer-term move toward more BRK-built architecture where replacing inherited framework behavior makes sense, while keeping the world functional throughout that process.

Still Heavily Under Development

Indestructible RP should currently be viewed as a developing world, not a finished product waiting for players to notice it.

There is a large amount still being built.

That includes gameplay systems, economy work, jobs, professions, businesses, administration, documentation, world content, horse and animal systems, framework work, player-facing guides, and the less visible infrastructure required to run a serious server properly.

Some of what is being explored today will look different by release.

That is expected.

I would rather change direction during development than keep a weaker idea simply because it appeared on an old roadmap.

Looking for the Community That Will Help Shape It

IRP is already interested in meeting people who want to become part of the community before everything is finished.

That includes future players who enjoy serious, character-driven western roleplay and are interested in watching the world develop rather than only arriving after launch.

Feedback from people who genuinely understand the kind of server IRP is trying to become is valuable during this stage.

The goal is not to design every detail in isolation and then hand a finished rulebook to a community that had no voice in how the world developed.

Community ideas will not automatically become features, but thoughtful feedback is taken seriously.

Future Staff & Department Leadership

Indestructible RP will also need people who want to help build and maintain the community, not just hold a staff title.

As development progresses, IRP will be looking for future staff, department leadership, and experienced roleplayers interested in helping shape areas such as law, justice, medical roleplay, businesses, professions, community support, and other parts of the server that need knowledgeable people behind them.

Those roles are not being treated as decorative ranks.

The right people should care about the health of the roleplay around their department, help newer players understand it, contribute useful ideas, and be willing to build something that may continue evolving for a long time.

IRP is more interested in finding the right people gradually than filling an org chart as quickly as possible.

Collaborators Welcome

The project is also open to meeting people who may want to contribute in other ways.

That can include developers, artists, map creators, writers, lore-minded roleplayers, testers, content creators, server builders, or people with real experience in subjects that IRP is trying to represent well.

Collaboration does not mean every person needs to become formal staff.

Sometimes the most useful contribution is expertise, testing, feedback, a good idea, or helping solve one specific problem.

IRP is being built as a serious long-term project, and there is room for other people who genuinely care about building that kind of world.

What IRP Is Trying to Become

Indestructible RP is ultimately being built for people who want more than a temporary RedM server to grind on for a few weeks.

It is intended to become a persistent western roleplay world where:

• characters can build long-term lives;
• professions and businesses create relationships;
• the economy gives players reasons to depend on one another;
• horses and animals matter;
• law and crime create stories;
• different lifestyles are genuinely viable;
• player actions help shape the community;
• systems support roleplay instead of competing with it;
• staff exist to support the world rather than become the center of it;
• and development continues responding to what the server actually becomes.

There is a lot left to build.

That is also part of what makes this stage interesting.

BRK is also growing beyond RedM into original game development.

The same interests that show up repeatedly in BRK resources appear here too:

• horses
• animals
• western settings
• roleplay
• simulation
• professions
• businesses
• player choice
• emergent systems
• exploration
• life simulation
• multiplayer
• character-driven worlds

The scale of those projects ranges from small experimental games to much larger long-term worlds.

A Horse-Themed Physics Merge Game

In Development

Pony Merge is one of BRK's smaller original game projects.

It takes the familiar drop-and-merge physics game format and replaces anonymous balls, fruit, or numbers with animated horse characters.

Players drop ponies into the play area, combine matching levels into larger horses, manage the increasingly crowded physics space, and try to keep the chain going without overflowing the board.

The project includes:

• pony and horse characters
• merge progression
• physics-based collisions
• bouncing and reactions
• character animations
• horse-themed visual effects
• casual drop-and-merge gameplay

If you're looking for a horse merge game, pony merge game, horse puzzle game, physics merge game, casual horse game, or a horse-themed take on the Suika/drop-and-merge style of game, Pony Merge is being built around exactly that idea.

A Top-Down Western Life, Roleplay & Simulation Game

In Development

Indestructible County is a larger original top-down game project built around western life, characters, systems, and player freedom.

It brings together many of the subjects I keep coming back to across BRK:

• horses
• ranching
• animals
• professions
• businesses
• hunting
• fishing
• towns
• homesteads
• law and outlaw gameplay
• character interaction
• roleplay
• exploration
• economy
• life simulation
• sandbox systems

The visual direction uses detailed top-down pixel art while keeping the world readable enough for actual play.

If you're interested in western games, cowboy games, horse games, ranching games, top-down RPGs, pixel western games, western life sims, roleplay games, or sandbox simulation games, this is the larger side of BRK's original development.

Horses have ended up becoming a recurring part of both BRK's RedM work and original games for a reason.

I am interested in horse gameplay that goes deeper than selecting a mount with slightly different speed statistics.

That includes ideas around:

• breed identity
• temperament
• training
• learned behavior
• bonding
• care
• equipment
• tack
• health
• aging
• breeding
• foals
• ranching
• working horses
• discipline suitability
• individual variation
• herd behavior
• ownership
• long-term consequences

The same approach extends to other animals.

Animals are more interesting when they participate in the game world instead of functioning as collectible decorations.

That philosophy influences BRK Stables, animal resources, ranching development, Indestructible County, and future life-simulation projects.

BRK's longer-term original game direction includes larger roleplay and life-simulation projects where players can build homes, professions, relationships, settlements, economies, and their own place in the world.

Some projects lean western.

Others explore different settings.

The common thread is systemic gameplay: activities and professions connecting to one another rather than existing as isolated minigames.

Future development will continue exploring combinations of:

• roleplay games
• life simulation
• multiplayer roleplay
• sandbox RPGs
• settlement building
• homesteads
• professions
• businesses
• horses and animals
• exploration
• player-created stories
• character progression
• modding
• authored NPC worlds

Projects will get dedicated pages when they are developed far enough to be useful to follow publicly.

BRK resource documentation is intended to tell server owners what they actually need to know.

Depending on the resource, documentation can include:

• installation instructions
• dependencies
• configuration
• compatibility
• exports
• events
• integration information
• examples
• troubleshooting
• known issues
• changelogs
• previews
• feature explanations
• migration information

Configuration documentation is written for the person trying to run the resource.

Developer/API documentation can go deeper when somebody needs to integrate with it.

Those are different audiences and should not have to dig through the same wall of internal implementation detail.

BRK primarily develops and validates around VORP today, but resources are increasingly designed so framework-specific behavior does not have to own the entire architecture.

Where practical, compatibility can expand to additional frameworks, standalone integrations, optional BRK systems, and open-source alternatives.

Support claims remain tied to actual testing.

If compatibility is experimental, partial, or untested, it should be labeled that way.

That matters more to me than making the compatibility list look impressive.

BRK resources can also integrate with shared studio systems such as menus, notifications, minigames, chat, administration, interaction tools, and utilities where doing so genuinely improves the experience.

BRK resources continue to receive maintenance after release.

Updates may include:

• bug fixes
• compatibility fixes
• configuration improvements
• requested quality-of-life features
• new integrations
• documentation improvements
• additional options
• performance improvements
• feature expansions

Feature requests are welcome.

Bug reports are welcome.

Constructive criticism is welcome.

If something I released does not work the way it should, I want to know about it.

Until BRK's dedicated support/ticket bot is complete, direct messages remain open for support.

Before a paid BRK resource is offered publicly, it goes through substantial testing.

That can include:

• repeated gameplay testing
• stress testing
• configuration variations
• restart behavior
• dependency behavior
• incorrect input
• interaction edge cases
• multiplayer situations
• compatibility testing
• UI behavior
• error handling

This takes longer.

That is fine.

A smaller catalog of resources I actually trust is more valuable to me than a giant storefront filled as quickly as possible.

You do not need to be a developer to use BRK.

Server owners can use resources, configuration tools, documentation, visual builders, and support without needing to understand the implementation underneath them.

Developers can use deeper documentation, shared utilities, exports, events, compatibility information, testing tools, and integration surfaces when they need more control.

Those two audiences should be able to exist on the same site without one being treated as an afterthought.

RedM Scripts

BRK Labs & Developer Tools

Maps & World Content

Documentation

Indestructible RP

Original Games

BRK

BRK Scripting Studios started in RedM, and RedM development remains a major part of what I do.

But BRK is ultimately about building systems, tools, worlds, and games that I actually want to exist.

Sometimes that is a large horse ownership system.

Sometimes it is a free Lua checker because somebody broke a comma.

Sometimes it is a serious roleplay server.

Sometimes it is an animated pony bouncing off another animated pony until they become a larger pony.

The projects can look wildly different from the outside.

The standards behind them are much more consistent:

Make it configurable.

Make it understandable.

Test it properly.

Maintain it.

Listen when people using it have something useful to say.

Don't charge people just because you can.

Don't release something you don't trust yet.

And give players more interesting things to do with it once it's in their hands.