## Introduction
In this tutorial, we will explore how to create interactive UI widgets that can trigger events in Verse using the Verse fields event type in Unreal Motion Graphics (UMG).

## Getting Started
To begin, open the Variables window in the UMG Designer.

## Adding Verse Fields Events
1. Add fields of the new event type to a User Widget in the UMG Designer.
2. Bind these fields to widget events using View Bindings.

## Reacting to Events in Verse
Events added to the User Widget are reflected in the Verse asset digest, allowing you to wait for an event from Verse code to react accordingly.

## Additional Resources
For more detailed information and examples, refer to the [Using Verse fields event type in a UMG User Widget tutorial](https://dev.epicgames.com/community/learning/tutorials/woOK/fortnite-using-verse-fields-event-type-in-a-umg-user-widget).




Create Interactive UI: Verse Fields Events Now Available in UMG

## Evolution of Epic MegaJam
The Epic MegaJam has been a staple in the gaming community, showcasing the creativity and talent of developers worldwide. Since its inception, the jam has grown exponentially each year, attracting more participants and innovative game submissions.

## Journey from 2022 to 2025
Reflecting on the previous Epic MegaJam in 2022, we can see how far the community has come in terms of game design, storytelling, and technical capabilities. The quality and diversity of games submitted have continued to impress both participants and judges alike.

## The Partnership with Showrunner
For the upcoming Epic MegaJam 2025, an exciting partnership has been forged with Showrunner, a leading developer in interactive storytelling. Together, they are set to create a captivating point-and-click adventure set in the City of Brains universe.

## Dive into the 90s
This year's Epic MegaJam submission will transport players back to the 90s, offering a unique prequel experience to the zombie outbreak in the City of Brains. Players will step into the shoes of a reporter navigating the bustling city streets, uncovering mysteries and secrets that will shape the future of the universe.

```python
# Sample Code Snippet

def investigate_location(location):
    clues = gather_clues(location)
    return process_clues(clues)
```


Evolution of Epic MegaJam: A Journey from 2022 to 2025

# 🐘 ELJ Arena: Battle of the Tusks

> *A prequel to City of Brains. A spectacle for the masses. A meat grinder for the unlucky.*

## 🎪 Welcome to the Greatest Show Before the End![alt text](elj_arena_cityofbrains_BETA_access_2025.07.30-21.13.39.png)

Months before the outbreak, the region’s biggest attraction wasn’t a concert—it was carnage on four tusks. ELJ Arena, built in the chemical-drenched shadows of the mountains, offered “family-friendly” entertainment with just a hint of irreversible trauma.

Now, you can ride the line between glory and processing in *Battle of the Tusks*—a 3v3v3 elephant-mounted multiplayer battleground where each team is a trio of specialists riding a single elephant into chaos.

## ⚔ Pick Your Role. Ride or Die.

Players form three-person teams atop war elephants, each member taking on a distinct role: the fearless Mahout (driver), the agile Howdah Warrior (combat specialist), and the all-seeing Luminary (tactical commander). Victory means fame, fortune, and maybe a hot meal. Defeat? Don’t ask what’s in the concession stand...

Every team needs a:

### 🐘 Mahout (The Driver)

Steers the elephant, controls charges and dashes, and can go anywhere on the map—immune to ground damage.

### 🏹 Howdah Warrior (The Fighter)

Grabs victory points, boards enemy elephants, and fights with a mix of ranged and melee weapons. Vulnerable on the ground—agility is survival.

### 🧠 Luminary (The Commander)

Sees from above with a top-down view, commands team strategies, drops AOE attacks, and keeps the squad alive with buffs and heals.

Each role plays totally different. Each has a voice, a view, and a reason to panic.

---
![Take a break from the city](elj_arena_cityofbrains_BETA_access_2025.07.30-21.02.43.png)

## 💀 This Isn’t Just a Game. It’s a Grinder.

On the surface, it’s all neon lights and animal-themed merch.

Look closer.

- Meat trucks leave every night.
- Grandma Liu’s kebabs never quite taste the same.
- The stables echo with elephant cries that sound... off.

There’s something glowing in the waste barrels, and it’s not love.

![More than meats the eye](elj_arena_cityofbrains_BETA_access_2025.07.30-21.13.40.png)
---

## A Spectacle Built on Secrets

The arena's dazzling glow masks something darker. Street vendors sling mystery meat with suspicious enthusiasm. Old champions hobble past on crutches, muttering about “retirement.” The green glow in the elephants' eyes? Totally normal.

![WafflesWafflesEverywhere](elj_arena_cityofbrains_BETA_access_2025.07.30-21.03.40.png)

Explore the concourse between matches: grab tactical waffles from WWE (Waffles Waffles Everywhere), test illegal sonic weapons disguised as guitars, or chat with nervous janitors who know *way* too much about what's under the arena. Victory points earn glory. Coconuts revive your team. Everything else... gets recycled.

### Teaser Quotes from the Arena:

**Jumbo Jack, DealMart Vendor**
![JumboJacks DealMart](elj_arena_cityofbrains_BETA_access_2025.07.30-21.01.13.png)

> Step right up, future champion! Jumbo Juice or escape map—your choice! Just don’t ask what’s glowing in the stables. 😅

**Grandma Liu, Kiwk Kebab Matron**

> Today's meat is REAL goat. Yesterday's losers? That’s someone else’s problem. 🤫

**The Ringmaster, Arena Overseer**

> Our retirement program is industry-leading. Competitors go out on top... or at least in one piece. 😏

## Gameplay at a Glance

- ⚔ **Three Roles, One Elephant:** Every team needs a Mahout to steer, a Howdah to fight, and a Luminary to command.
- 🎯 **Victory Points Decide the Match:** Grab objectives, survive, and outwit rival teams across dynamic 3v3v3 arenas.
- 🐘 **Coconuts Revive Elephants:** Use them wisely... or turn them in for more firepower.
![Arena Grandstands](elj_arena_cityofbrains_BETA_access_2025.07.30-20.58.10.png)
- 🔥 **Arena Zones Include:**
  - Flex Appeal Gym (training + addiction!)
  - MegaSports Gift Shop (rigged odds, rigged merch)
  - VIP Lounge (rewards for winners… and subtle foreshadowing)
  - Food Court Buff Zones (consume with caution)

## 🎮 How to Win (Or At Least Not Get Processed)

You don’t need the most kills to win a match. Victory is earned in multiple ways:

- 🏆 **Victory Point Collectibles**: Spawn around the map—some only visible to Luminaries.
- 📦 **Cargo Raids**: Destroy enemy elephant cargo to weaken their team’s standing.
- 🧠 **Survival Bonus**: Stay alive longer than the others, and the crowd loves you more.
- 🎯 **Objective Control**: Seize control points in unique battle zones (The Ruins, Jungle Circuit, Desert Fortress).

Killing’s great, sure. But the best teams out-strategize, not just out-slaughter.

---

## 🧃 Coconuts, Contracts, and Consequences

You start each match with a **coconut**—it’s your team’s one shot at reviving your elephant. Use it wisely... or trade it for firepower.

And don’t get too attached to that shiny new weapon you just bought from HuntingZone.
![RetroVibes at HuntingZone](elj_arena_cityofbrains_BETA_access_2025.07.30-20.55.04.png)

> If you die, you drop everything.
> If another team loots your stuff? It’s theirs now.
> 💼 **Inventory is persistent**—until it’s stolen.

---

## 🛠️ Built for the Hardcore. Balanced for the Insane.

ELJ Arena was built from the circuit board up in **UEFN**, with a custom-designed inventory and currency system. Every item you purchase, every buff you apply, and every victory you earn is tracked.

> Lose a match? You lose the loot.
> Win a round? Your base gets new gear.
> Trade your coconut for a bonus slot? Hope you don't need it later.

Want the full breakdown? Check out our [Dev Deep Dive](#) for tech-heads and modders.

---

## 👀Join the Prequel Before the Plague

Want to be part of the madness before it all goes... *brain-dead*? We’re accepting **early access playtesters now** through our [Discord]([https://discord.gg/fWHBt5kyjj](https://discord.gg/fWHBt5kyjj)) for a limited time. Compete, explore, and maybe uncover the truth behind the arena’s twisted "retirement plan."

If you survive, you'll have bragging rights—and a head start—when *City of Brains* drops.

### 💥 ELJ Arena Opens Labor Day 2025 💥

See you in the stables… while you still have a choice.

🎟️ **Join here:** [https://discord.gg/fWHBt5kyjj](https://discord.gg/fWHBt5kyjj)

---

*ELJ Arena: Battle of the Tusks* – Where strategy, showmanship, and subtextual meat processing collide.

### 🧠 A City of Brains Prequel

🔪 From the creators of *BrainDeadRP*, *Double Dip Sauce*, and the worst vacation of your life.
# ELJ Arena - Elephant Jousting | Battle of the Tusks starts Labor day 9-1-2025
![Ticket Office Opens Labor Day 2025](elj_arena_cityofbrains_BETA_access_2025.07.30-20.56.21.png)

ELJ Arena – Battle of the Tusks


## 🎬 Welcome to the End of the World (As We Kinda Know It)

You’re a teenager from a quiet town with one goal: get to the city concert before the eclipse ends. Instead, you’ll uncover a secret sauce-fueled apocalypse, sneak through faction turf wars, and maybe find your missing dog.

![Nothing to worry about](cityofbrains_alpha_HighresScreenshot_2024.10.21-07.47.34.png)

Welcome to **City of Brains – The Outbreak Begins**, a stylized multiplayer survival adventure where 90s nostalgia meets neon horror. What starts as a quirky coming-of-age story turns into a full-blown outbreak — and you're at the heart of it.


---

## 🏡 Chapter 0 – Prologue: Suburbia Isn’t Safe

The game begins in your small hometown — seemingly untouched by chaos. Pools glow slightly green, payphones buzz with strange static, and your parents are just... gone.

Your goal? Do a few odd jobs, save up some Gold, and catch the **last bus to the concert** downtown. You can go solo, or link up with friends. The path to Central Nervous Park is open — if you survive the tunnel.

---

## 🎪 Chapter 1 – TotalDarkness at Central Nervous Park

The concert kicks off. Lights, fireworks, footlongs — and a rare lunar eclipse. Unfortunately, those “Joust Dogs” sold by vendors? They're made from processed ELJ Arena losers. Mix that with **Double Dip Dog Sauce**, and you've got a recipe for disaster.

As the blood moon rises, the crowd turns green, groans... and goes for your brain.

![City of Brains Waiting to be explored](cityofbrains_alpha_ScreenShot00037.png)
---

## 🧠 Chapter 2 – There’s Something in the Dip

You wake up trapped in the city. Roads are blocked, corpses don’t stay down, and rumors swirl about factions forming on the fringes. It’s time to find allies, fortify a safe zone, and figure out just how bad this outbreak’s going to get.

This is where **true survival begins**.

---

## 👥 Play How You Want

City of Brains supports multiple styles of play:

- 🤝 **Co-Op** – Team up with friends (best in groups of 3, like ELJ, but no hard cap)
- 🧟‍♂️ **PvE** – Explore at your own pace, face NPC zombies and city events
- 💀 **PvP** – Fight other survivors for loot, zones, or just because

You can travel together to the concert, split off to search for Sparky, or go full lone wolf.

---

## 🧭 Chapter-Based Release Timeline (Alpha)

- ✅ **Prologue** – Suburban jobs + bus to city
- ✅ **Chapter 1** – The outbreak begins at the concert
- 🛠️ **Chapter 2** – Survival systems, factions, and loot loops
- 🔒 **Future Chapters** – Full map unlocks, faction wars, endgame chaos

Everything you do carries over. Dead civilians stay dead. Zombies remember.

---

## 🏙 Factions of the Apocalypse

Each city district is controlled by one major faction — pick one, or navigate the chaos alone:

- **🐻 Team Bear – Northside Tech Bros**  
  Crypto-pilled drone operators with flamethrowers.

- **🐙 The Krakens – Westside Trailer Parks**  
  Outlaw engineers and swamp bombers with hot tempers.

- **🐉 The Dragons – Eastside Influencers**  
  Weaponized glam and weaponized gossip.

- **🦩 The Flamingos – Southside Factories**  
  Fashion-forward, factory-tough — they know the streets.

Joining one grants storage access, perks, and safe passage. Betraying one? Good luck.

---

## 💾 Save Smart, Or Die Trying

- 🔐 Save manually at beds, tents, or faction shelters
- 💸 Bank Gold at **BrainBank ATMs**
- 🧳 Store gear in team caches or personal stashes
- 💀 Die with valuables = they’re lootable by others
![This Underpass looks like a great place to save and sleep](cityofbrains_alpha_savepoint_2025.04.14-14.25.55.png)
---

## 🐕 Sparky: Good Boy. Great Companion.

Complete the flyer side quest to reunite with your dog, **Sparky**:

- Sniffs out buried loot  
- Alerts you to infected threats  
- Unlocks hidden events and side missions  
- Can bark, distract, or even fight if leveled up

He might just save your life. Or help you uncover the truth.

---

## 🎮 Core Gameplay Loop

- Explore abandoned rooftops, arcades, parking garages
- Level up your real-world skills: Plumber, Electrician, Mechanic
- Rebuild vehicles, generators, or blocked paths
- Interact with NPCs who remember your choices
- Escape via the Battle Bus... if it still runs

---

## 🌕 What Comes After the Show?

This isn’t just zombie waves. It’s:

- Environmental storytelling  
- Reactive factions  
- Persistent decisions  
- A corrupted system trying to clean itself… violently

And it all began with a hot dog.

---

## 🧪 ELJ Arena – The Prequel Drops First

Before the concert, there were elephants.  
**ELJ Arena** (launching next month) reveals how the “Joust Dogs” were made — and who didn’t make it out of the ring.  
Spoiler: processed meat plays a role.
![ELJ Arena - Opens Labor Day 2025](elj_arena_prequel_2025.03.25-web.png)

---

## 🎃 What’s Coming

- 🐘 August 2025 – ELJ Arena Prequel launches
- 🧟‍♀️ October 2025 – City of Brains Chapters 1 & 2 release for **Fortnitemares**
- 🚧 Winter 2025 – Additional zones and faction wars

---

## *City of Brains – Where Horror Meats Humor*

Team up or turn on each other.  
Ride the bus or walk the tunnel.  
Save Sparky… or become someone else’s undead sidekick.

The world’s ending, but you’ve got options.  
Let’s see how you handle the sauce.

![City Of Brains - The outbreak starts Fall 2025](cityofbrains_outbreak_header.png)

City of Brains – The Outbreak Begins

# UEFN 34.0 Update: Your Complete Guide to New APIs and Features

*Ever felt like your Fortnite creator toolkit needed a power-up? Well, grab your favorite energy drink because UEFN 34.0 just dropped a loot crate full of new features!*

The latest UEFN update brings a massive overhaul to how we handle everything from HUD elements to AI behaviors. Whether you're crafting the next battle royale sensation or building an immersive adventure, these new tools will level up your creative arsenal.

## What's New in 34.0? (For Those Just Dropping In)

Think of this update as adding a whole new inventory of tools to your creative toolbelt. We've got a shiny new UI Feature Template (say goodbye to UI headaches!), multiplayer testing with AI players (no more begging friends to help test), and some seriously cool new devices that would make even a master thief jealous. Plus, for all you math nerds out there, we've got some coordinate system updates that would make Pythagoras do a double-take.

## The Power-Ups (Major Feature Additions)

### 1. UI Feature Template: Your New Design Best Friend

Tired of building UIs from scratch? The new User Interface Feature Template has your back:

```verse
# Example of using the new UI template components
using { /Game/UI/Templates/CustomHUD }

customHUD := class(creative_device):
    # Import pre-built components
    QuestIndicator : quest_indicator_widget = quest_indicator_widget{}
  
    # Set up your custom UI
    OnBegin<override>():void=
        # Use the template's built-in functionality
        QuestIndicator.SetupDisplay(
            IconType := quest_type.Collection,
            Description := "Collect 10 coins!"
        )
```

The template comes packed with:

- Ready-to-use widget examples
- Custom materials and textures
- Comprehensive setup guides
- Export-ready assets for your projects

### 1. HUD Management 2.0: The Clean-UI Update

Remember wrestling with multiple UI methods? Those days are gone! The new `fort_hud_controller` brings everything under one roof:

```verse
# The new way to manage HUD elements
hudController := Playspace.GetHUDController()

# Hide those pesky elements
hudController.HideElements([hudElement1, hudElement2])

# Show them when needed
hudController.ShowElements([hudElement3, hudElement4])

# Reset when you want a fresh start
hudController.ResetElementVisibility([hudElement1, hudElement2])
```

### 2. Multiplayer Testing: Your Personal QA Team

No more "anyone free to test?" messages! The new Test Player settings let you spawn AI-controlled players for testing:

```verse
# Configure test player settings in your game mode
testSettings := fort_test_settings:
    SpawnOnStart := true
    PlayerCount := 16  # Up to island maximum
  
# You can even customize test player behavior
testBehavior := test_player_behavior:
    OnSpawn(): void =
        # Set up custom test player actions
        MoveToLocation(targetPoint)
        SimulateInteraction(nearestDevice)
```

*Note: While test players are great for basic testing, they're not yet Ready Player One levels of AI - they have some limitations, like not being able to use certain devices.

Your NPCs just got smarter with these new AI features:

```verse
# Create an intelligent guard
guardActions := Character.GetFortGuardActions()

# Make them actually guard stuff!
guardActions.Attack(targetInfo) => result
if (result = ai_action_result.Success) {
    # Your guard is doing their job!
}

# Keep them in check with leash controls
leash := Character.GetFortLeashable()
leash.SetLeashAgent(agent, innerRadius, outerRadius)
```

### 3. New Devices: Bank Vaults and Rift Points

Want to add some Ocean's Eleven vibes to your island? The new Bank Vault and Rift Point devices have you covered:

```verse
# Setting up a bank vault heist
bankVault := fort_bank_vault_device:
    # Configure vault settings
    WeakPointCount := 3
    BreakInTime := 30.0
  
    # Handle vault events
    OnVaultBreakInStarted(): void =
        # Trigger alarms, spawn guards, etc
        SpawnGuards(vault_location)
        TriggerAlarmSequence()
```

You also get the new Rift Point system for bomb-defusal gameplay:

- Plant and defuse mechanics
- Customizable timers
- Team-based interactions

### 4. SpatialMath: Your New Best Friend (Now with FRU!)

The new SpatialMath module is like having a graphing calculator built right into UEFN:

```verse
# Smooth moves with linear interpolation
let start := vector3{Forward:=0.0, Right:=0.0, Up:=0.0}
let end := vector3{Forward:=1.0, Right:=1.0, Up:=1.0}
let smooth := Lerp(start, end, 0.5)

# Almost equal? Let's check!
IsAlmostEqual(vector1, vector2, 0.001)
```

## Understanding the Changes (Or: "Why Your Old Code Might Need a Medkit")

If you're seeing some warnings in your old code, here's what's changed:

1. **HUD Methods**: Old `player_ui` methods are now deprecated

   - *Old*: `ShowHUDElements()`
   - *New*: `fort_hud_controller.ShowElements()`
2. **Character Controls**: New interfaces for better NPC management

   - *Old*: Direct character manipulation
   - *New*: Specialized interfaces like `fort_guard_actions`
3. **Math Operations**: Enhanced vector and rotation calculations

   - *Old*: Basic vector math
   - *New*: Comprehensive SpatialMath module

## Tips for Upgrading (Without Breaking Everything)

1. **Start with HUD Updates**

   - Convert your UI code first
   - Test each element individually
   - Keep a backup of your old code
2. **Gradually Enhance AI**

   - Update one NPC type at a time
   - Test behaviors in isolation
   - Use the new alert levels system
3. **Embrace SpatialMath**

   - Replace old math calculations
   - Take advantage of new vector operations
   - Use the new string representations for debugging

## Real-World Applications

Here's how these updates make common tasks easier:

### Creating Smart Guard NPCs

```verse
# Define guard behavior
npcBehavior := npc_behavior {
    OnBegin := function() {
        # Initialize guard state
        guardActions := Character.GetFortGuardActions()
        guardPerception := Character.GetFortGuardPerception()
    
        # Set up patrol route
        guardActions.Patrol(patrolPoints)
    }
  
    OnAlert := function(level: fort_guard_alert_level) {
        if (level = fort_guard_alert_level.Suspicious) {
            # Investigate the area
            guardActions.InvestigateLocation(lastSeenPosition)
        }
    }
}
```

### Dynamic HUD Management

```verse
# Create a context-aware HUD manager
hudManager := fort_hud_controller {
    UpdateCombatHUD := function(inCombat: logic) {
        if (inCombat) {
            ShowElements([
                CombatElements.HealthBar,
                CombatElements.AmmoCount,
                CombatElements.WeaponSlots
            ])
        } else {
            HideElements([
                CombatElements.HealthBar,
                CombatElements.AmmoCount,
                CombatElements.WeaponSlots
            ])
        }
    }
}
```

## Conclusion

UEFN 34.0 is more than just an update – it's a complete overhaul of how we create and manage game elements. With these new tools, you're better equipped than ever to create amazing experiences.

Remember, you don't have to rebuild everything at once. Start small, test thoroughly, and gradually incorporate these new features into your existing projects. Your future self (and your players) will thank you!

---

*Note: This article was written while chugging energy drinks and debugging NPCs that kept walking into walls. No NPCs were harmed in the making of this guide.*


BizaNator

UEFN 34.0 Update Hud, UI, AI, oh my!

# Disallowed Object Type - Material Nanite Override: Fixing Validation Woes

*Running into validation errors is like encountering a final boss in a game, but fear not, we've got your back! Let's tackle the disallowed object type issue and get you back on track in your UEFN development journey.*

## What is the Disallowed Object Type Material Nanite Override? (For Those Who Love Smooth Sailing)

Picture this: you're cruising through your UEFN project, and suddenly, you hit a roadblock ÃƒÂ¢Ã¢â€šÂ¬Ã¢â‚¬Å“ the dreaded disallowed object type material nanite override error. It's like getting stuck in a game level because you're carrying an item you're not supposed to have. Annoying, right?

## The Problem (Or: "Frustrations You Can Relate To")

If you're seeing these red flags in your console logs:
![uefn console log](disallowed-object-fix-1.png)

- Symptom 1: Errors popping up like mushrooms in a rainy forest after a thunderstorm
- Symptom 2: Feeling like you're trying to wield a broken sword in a boss battle

## The Solution (In Order of "Swift Resolution")

### 1. Nanite Override Maneuver (With a Hint of Tech Magic)

Let's perform a simple hack to override this issue:

1. Locate the problematic material in your content drawer.
2. Click on it like you're selecting a superpower in a game menu.
3. Watch the magic unfold as you fix the disallowed object type error.

### 2. Material Validation Dance (With a Touch of Developer Swagger)

Now, let's dive deeper into the technical realm:

```yaml
material:
  disallowed: false
  naniteOverride: true
  validationStatus: "cleared"
```

- Understand what each setting does like deciphering a spellbook.
- Realize why it matters, just like understanding the weakness of a boss monster.

## Understanding Material Nanite Overrides (Or: "Making Tech Jargon Less Scary")

Let's simplify this technical concept with a relatable analogy:

- Nanite Override: Think of it as equipping an item that nullifies the effects of another item.
- Dive deeper into the nanite world and see how it parallels to choosing your gaming loadout.

## Conclusion: Level Up Your UEFN Skills!

You've conquered the disallowed object type material nanite override challenge! Keep pushing forward in your UEFN adventures, knowing that you can tackle any validation obstacle that comes your way.

---

*Note: Remember, even in the tech world, a little humor and creativity can go a long way in solving problems and keeping the journey fun and engaging.*

Understanding Dissallowed Object Type Material Nanite Override: A Technical Deep Dive

# Say "No More" to OBS's Party-Pooper Pop-Up 🚫🎉

Alright, fellow brain-munchers and keyboard warriors, let's talk about that triple-headed Hydra gaming rig we've all drooled over! 🐉💻 Imagine hooking up all three HDMI inputs plus a cheeky fourth for that all-seeing eye (aka your camera). You're all set for co-op gaming glory, reviews, and those laugh-until-you-cry moments. But then, just like a zombie at a carnival, OBS decides to crash the party with its annoying "unclean shutdown" nag every time you reboot. Like, hello? Who invited you, Mr. Buzzkill?

Since OBS update XX.X (yeah, they're updating faster than you can say "revive me!"), every reboot greets you with that clingy pop-up asking, "Did you forget about me? Want to run in safe mode or normal?" It's like that one friend who can't take a hint when the party's over. 🙄 And there you are, trudging over to manually click "OK" before the real fun can start. Talk about a mood killer.

But fear not, my fellow survivors of the digital apocalypse! A simple command line charm is all it takes to exorcise this ghost. Who's got time to summon the command prompt and chant `obs64.exe --disable-shutdown-check` every time? Not us! We've got zombies to slay and victories to royale. So, let's conjure up a shortcut instead!

## Crafting the Magic Shortcut 🧙‍♂️✨

1. First, embark on a quest to the mystical land where OBS resides (aka navigate to where you installed or extracted OBS). If you're a nomad like me and run it in portable mode, I salute you.

   ![Summoning the Shortcut](obs-shortcut-guide-1.png)

   Find the sacred obs64.exe, right-click, and drag it into the realm of "Create shortcuts here." Like finding an epic loot drop in the middle of a heated Fortnite match.
2. Behold, you've spawned an entity known as "obs64 - shortcut." Right-click this mystical being and select "properties."

   ![Accessing the Arcane Properties](shortcut-properties-tabs-1.png)
3. Click the "Shortcut" tab and with the precision of a sniper, paste the following incantation:

   ```plaintext
   C:\OBS\bizanator\OBSStudio\bin\64bit\obs64.exe --disable-shutdown-check
   ```

   ![Casting the Spell](shortcut-command-field-1.png)

   Remember, fellow spellcasters, no quotation marks "" , no `` – just the spell as it is. Otherwise, you'll summon...

   ![A Wild Error Appears!](windows-advanced-properties-obs-launch-1.png)
4. With the grace of a default dance, click "OK." Congrats! You've now got a magic portal that launches OBS without the nagging spirit of shutdown checks. Pin it to your start menu, clone it to your desktop, tattoo it on your arm – whatever floats your boat.

And there you have it, my gaming ghouls and tech witches! Happy streaming and may your frames be high and your latency low. Welcome to a world where OBS behaves more like a trusty sidekick and less like an unwanted party crasher. 🎮👻


Obs did not shutdown properly?!

# Test Post

Welcome to the mystical realm of technical content creation, where we present to you:

# The Ultimate Guide to Crafting Tech Articles with Claude, the Content Wizard

## Overview
Prepare to be dazzled by a treasure trove of templates and guidelines that will elevate your technical articles to superhero levels of awesomeness. Dive into the world of fancy frontmatter, snazzy SVG graphics, and content that shines brighter than a superhero's cape.

## 1. Frontmatter Template
```yaml
---
id: "{article-slug}"
title: "{Main Title: Subtitle Format}"
date: "YYYY-MM-DD"
category: "tutorials"
images:
  thumbnail: "{article-slug}-thumbnail.svg"
  header: "/images/{article-slug}-header.svg"
creator: "BizaNator"
excerpt: "Embark on a wild, {tone}-infused adventure through the world of {main topic}, armed with {special feature} and practical solutions to conquer any tech challenge."
featured: false
tags: ["tag1", "tag2", "tag3", "tag4", "tag5", "tag6", "tag7"]
status: "published"
---
```

## 2. SVG Header Specifications

### Header SVG Template
```svg
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 800 400">
  

  
  <defs>
    <pattern id="grid" width="40" height="40" patternUnits="userSpaceOnUse">
      <path d="M 40 0 L 0 0 0 40" fill="none" stroke="#2de2e6" stroke-width="0.5" opacity="0.3"/>
    </pattern>
    <linearGradient id="bg-gradient" x1="0%" y1="0%" x2="100%" y2="100%">
      <stop offset="0%" style="stop-color:#2b0a3d"/>
      <stop offset="100%" style="stop-color:#571089"/>
    </linearGradient>
  </defs>

  
  <rect width="800" height="400" fill="url(#bg-gradient)"/>
  <rect width="800" height="400" fill="url(#grid)"/>

  
  <g transform="translate(400,200)">
    
  </g>

  
  <g transform="translate(400,320)">
    <text text-anchor="middle" 
          font-family="Arial Black" 
          font-size="48px" 
          fill="#primary-color"
          style="filter: drop-shadow(0px 0px 10px #primary-color);">
      MAIN TITLE
    </text>
    <text text-anchor="middle" 
          font-family="Arial" 
          font-size="24px" 
          fill="#secondary-color" 
          y="35"
          style="filter: drop-shadow(0px 0px 5px #secondary-color);">
      SUBTITLE
    </text>
  </g>

  
  <path d="M 0 0 L 50 0 L 50 10 L 10 10 L 10 50 L 0 50 Z" fill="#accent-color"/>
  
</svg>
```

### Key Header Design Principles:
1. Viewbox size: 800x400
2. Use gradient backgrounds with grid patterns like a tech wizard
3. Add a sprinkle of animations for that extra flair
4. Center your main visual elements like the hero of a story
5. Spice it up with consistent corner decorations
6. Include both title and subtitle text for that perfect blend
7. Keep the brand colors alive while adding a touch of uniqueness.

## 3. Thumbnail Specifications

### Thumbnail SVG Template
```svg
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 400 400">
  

  
  <defs>
    <linearGradient id="thumbTechGlow" x1="0%" y1="0%" x2="100%" y2="0%">
      <stop offset="0%" style="stop-color:#primary-color"/>
      <stop offset="100%" style="stop-color:#secondary-color"/>
    </linearGradient>
    <style>
      @keyframes pulse {
        0%, 100% { opacity: 0.4; }
        50% { opacity: 1; }
      }
      .animated-element { animation: pulse 2s infinite; }
    </style>
  </defs>

  
  <rect width="400" height="400" fill="#background-color"/>

  
  <g stroke="url(#thumbTechGlow)" stroke-width="1" fill="none" opacity="0.2">
    
  </g>

  
  <g transform="translate(200,200)">
    
    <path d="M-120,-80 L120,-80 L150,0 L120,80 L-120,80 L-150,0 Z" 
          fill="#0f1b2d" stroke="url(#thumbTechGlow)" stroke-width="3"/>
    
    
  </g>

  
  
</svg>
```

### Key Thumbnail Design Principles:
1. Viewbox size: 400x400
2. Keep it simpler than the header but maintain that same tasty style
3. Focus on the central dish like a master chef
4. Add just a pinch of animations for that hint of excitement
5. Don't forget the garnish - consistent corner decorations
6. Let it represent your article's essence like a culinary masterpiece

## 4. Article Structure Template
```markdown
# Main Title: Subtitle

*Start your journey with a clever opening line that sets the tone*

Prepare for the adventure as we introduce the problem and hook you in with our captivating storytelling.

## What is [Topic]? (Explained in Layman's Terms)
An easy-to-digest explanation using relatable analogies.

## The Problem (Or: "The Struggle is Real")

If you're seeing any of these signs:
- Symptom 1 (with a dash of humor)
- Symptom 2 (with a sprinkle of wit)
- [Keep the list going]

## The Solutions (Ranked by "Casual Coolness")

### 1. First Solution Name (With a Side of Pun)
Step-by-step instructions:
1. The first step
2. The second step
[Keep on rocking those steps]

### 2. Second Solution Name (With a Dash of Humor)
A technical breakdown with casual comparisons:
```code block with settings```
- What each setting does
- Why it's important

[Keep those solutions coming]

## Understanding [Topic] (Or: "The Lightbulb Moment")
Break down those technical jargons with analogies you can relate to:
- Tech term: Everyday comparison
- [Keep enlightening us]

## Conclusion

Wrap it up with a final paragraph that's part inspiration, part chuckles.

---
*Note: A parting joke about the magical creation process of this article*
```

## 5. Style Guidelines

### Tone and Voice:
- Casual with a hint of tech-savviness
- Sprinkle some humor for fun
- Use analogies from gaming or pop culture like a pro
- Keep those tech explanations as clear as a gaming strategy guide
- Spice up your headings with catchy subtitles

### Formatting:
- Use markdown for that sleek look
- Serve technical settings in code blocks
- Keep your headings consistent like a pro gamer's strategy
- Bullet points are your best friend
- Add some flair with italicized notes

### Visual Elements:
- Start with a delicious header image
- Keep your color scheme consistent throughout
- Add tech diagrams for that extra oomph
- Sprinkle some animations where it fits
- Don't forget the cherry on top - corner decorations on your graphics

## 6. Process Steps

1. Begin with the frontmatter template
2. Whip up that header SVG like a tech masterchef
3. Serve a scrumptious thumbnail SVG
4. Craft your article following the structured template
5. Add those tags and metadata like a seasoned pro
6. Ensure all your file names match the article slug for that perfect harmony
7. Keep that style consistent throughout like a top-tier gamer aiming for

Unleashing the Power of Test Article: A Comprehensive Guide

## 🎮 Leveling Up Your Samsung Odyssey Neo G9 Setup: FancyZones for Fortnite UEFN Developers 🎥

### 🌟 A Big Screen, A Bigger Workflow 🌟

Welcome to the ultra-wide dreamland of the  **Samsung Odyssey Neo G9** , the 57-inch pixel-pumping powerhouse that's here to make your Fortnite UEFN projects and programming life as smooth as a victory royale. But let’s be real: if you’re not optimizing this beast of a screen, you’re about as efficient as a bot trying to crank 90s. That’s where **FancyZones** swoops in like a glider into Tilted Towers—ready to take your productivity to pro levels. 💻✨

FancyZones, a magical tool from PowerToys, lets you carve up your screen real estate faster than a sweaty squad claiming high ground. And for your G9? It’s the perfect partner in crime. Let’s dive in and show you why this setup is your ticket to creative domination. 🎨🛠️

---

### 🔍 Why FancyZones? (AKA "Why Should You Care?")

Here’s the deal: without FancyZones, you’re wasting the glorious potential of your ultra-wide setup. By splitting your screen into functional zones:

* 🎥  **Screen Recording Nirvana** : Tools like **OBS** or **Camtasia** can perfectly capture your central 4K zone, ensuring your YouTube tutorials look crispy and not weirdly stretched. Your viewers will thank you.
* 💬  **Multitasking Magic** : Keep Discord, Spotify, and browser tabs neatly in their own lanes while Unreal Engine takes center stage.
* 🍕  **Couch Potato Proof** : Nobody can complain about unreadable text when you pair this setup with  **PowerToys ZoomIt** . Seriously, zoom in on fields, highlight elements, and make sure even the guy shoveling pizza on his couch can follow along. Check out our guide on ZoomIt for the ultimate how-to-video arsenal. 😉

---

### 🛠 Installing FancyZones (Because We All Need a Power Move)

Here’s how to get started:

1. **Install PowerToys** :

* Using `winget`: Open PowerShell and type `winget install --id Microsoft.PowerToys -e`.
* Or download directly from [PowerToys GitHub](https://github.com/microsoft/PowerToys/releases).

1. **Launch PowerToys** and select FancyZones from the sidebar.
2. **Enable FancyZones** : Toggle the switch and you’re good to go. 🎉

---

### 🎨 Setting the Stage: Your Ultimate FancyZones Layout 🎨

Picture this: a sleek, ultra-wide **7860x2160** canvas divided into a perfectly optimized layout. Here's the setup that will make your Odyssey Neo G9 shine:

1. **The "Main Event" Zone** : Smack dab in the center is a glorious  **4K zone (3840x2160)** . Use this for UEFN, Unreal Engine, or your primary IDE. Perfectly sized for screen recording to upload 4K tutorials on your YouTube channel, or just to flex on your fellow devs. 🖥️
2. **Double Trouble Stacks on the Left** : Two vertically stacked **1920x1080 zones** on the left side. Ideal for Discord chats, documentation, or just leaving your Spotify playlist open to get those retro Vaporwave vibes flowing. 🎶
3. **Right Zone: The Leftovers** : The remaining **2100x2160 pixels** form a tall, single column on the right—a cozy home for your file manager, browser, or that random JSON parser you keep needing every five minutes. 📂

Below is a diagram showcasing this layout for better visualization:

![FancyZones Layout for Samsung G9](ultrawide_4k_layout_diagram.png)

---

### ⚙️ FancyZones: The Power Move Setup ⚙️

Here’s how to make this layout a reality:

1. **Open FancyZones Editor** : Hit `Win + Shift + ‘` to launch the editor. (Don’t panic, the ‘ key is the one you never use - next to the 1.)
2. **Create a Custom Grid** :

* Divide your screen into three sections.
* Make the left section two vertically stacked zones of  **1920x1080** .""
* Set the center to **3840x2160** for your 4K zone.
* The right gets the leftover **2100x2160** column.
  ![FancyZones Custom Layout](fancy-zones-custom-layout.png)

1. **Hotkeys Setup** :

* Assign hotkeys for quick layout switches in the FancyZones Editor under "Custom Layouts."
* Use `Win + Ctrl + Alt + [Number]` to quickly snap to your custom grid.
* ![FancyZones Hotkey](fancy-zones-hotkey.png)

1. **Zone Behavior Settings** :
   ![FancyZones Settings](fancy-zones-settings.png)

* Enable **"Hold Shift Key to Activate Zones While Dragging."** (Or as we call it, the "grab and drag" power-up.) 🕹️
* Turn on **"Use Middle-Click to Toggle Multiple Zones Spanning."** (For when you want to go full multitask mode.) 👾
* Check **"Keep Windows in Their Zones When the Screen Resolution Changes."** (Because pop-ups in random places are *so* Chapter 1.) 💡
* Activate **"Allow Child Windows Snapping"** for apps like Task Manager. Yes, child windows deserve some love too. 🍼

1. **Apply the Layout** : Drag and snap windows to their new homes. Marvel at your own genius. 🌟

---

### 💡 A Day in the Life of a BrainDead Dev 💡

Imagine this: you’re working on the next chapter of **"City of Brains,"** tweaking the lighting in your Flamingo nightclub. The center 4K zone displays your UEFN viewport in glorious detail. Discord’s blowing up on the left, where you’ve stacked chats and documentation. On the right, you’ve got a browser open, googling "Why is Verse being weird again?" Life’s good. You’re in the zone—literally. 😎

---

### 🌴 Styling with Braindead.tv Colors 🌴

> We’re all about that retro beach-chic vibe, so why not carry it into your workspace? Set your FancyZones colors to match Braindead.tv’s aesthetic—neon pinks, cool blues, and the occasional hint of mint green.![fancy-zones-appearance](fancy-zones-appearance.png) Because even your pixels should party like it’s the 80s. 🌈

To truly bring it home, here’s a styled image inspired by Braindead.tv:

![Braindead FancyZones Styled](a_trendy_and_stylish_illustration_of_a_samsung_g9.webp)

---

### 🎬 Lights, Camera, Action 🎬

Ready to make your Samsung Odyssey Neo G9 the ultimate Fortnite UEFN workstation? FancyZones and this setup make creating tutorials, managing workflows, and being the coolest dev around a piece of cake. Don’t forget to pair this with **PowerToys ZoomIt** to highlight those hard-to-read fields while recording. Because the guy on the couch shoveling snacks deserves to see your genius too. 🍕🎮

Remember: in "City of Brains," nobody’s judging your zones—but IRL? Yeah, they are. So make them awesome. 💪

---


🎮 Leveling Up Your Samsung Odyssey Neo G9 Setup: FancyZones for Fortnite UEFN Developers 🎥


# Verse Function Renaming: The Art of Clean Code Through Smart Aliases

*Ever felt like your function names are longer than a loading screen tooltip?*

When developing games, we often start with descriptive but verbose function names that make perfect sense... until we have to type them for the hundredth time. Today, we'll explore a real-world example of simplifying function names while maintaining backward compatibility, using a technique that's smoother than a perfectly timed emote.

## What is Function Renaming? (For Those Who Type GetPlayerDataForPlayerForPlayerSession)

Function renaming is like giving your character a nickname – it's shorter, easier to remember, but still refers to the same entity. In our case, we're looking at transforming `GetPlayerDataForPlayer` into the more concise `GetPlayerData`. Think of it as upgrading from a lengthy gamertag to something you can actually type without getting thumb cramps.

## The Problem (Or: "Why Are We Still Typing ForPlayer When We Know It's For a Player?")

Here's what we're dealing with:

```verse
# Original verbose function
GetPlayerDataForPlayer<public>(Agent:agent)<transacts><decides>:player_data =
    GameSessionData := GetOrCreateSessionData(GetSession())
    Player := CheckPlayerDataForPlayer[Agent]
    PlayerData := GameSessionData.PlayerData[Player]
    return PlayerData
```

If you're experiencing any of these symptoms:
- Your function names are longer than your actual implementation
- You keep misspelling "ForPlayer" as "ForPLayer" at 2 AM
- Your autocomplete is getting RSI from suggesting the full name
- Your code reviews include more horizontal scrolling than a side-scroller game

## The Solution (In Order of "Why Didn't We Do This Sooner?")

### 1. The Clean Rename (Operation: Shorter Name, Same Game)

First, let's create our new, streamlined function:

```verse
# Get the player's data with a cleaner name
GetPlayerData<public>(Agent:agent)<transacts><decides>:player_data =
    # Get the session data
    GameSessionData := GetOrCreateSessionData(GetSession())
    # Check if the player has data, if not, create one
    Player := CheckPlayerDataForPlayer[Agent]
    # Get the player session data
    PlayerData := GameSessionData.PlayerData[Player]
    return PlayerData
```

### 2. The Backward Compatibility Trick (Or: How to Not Break Everything)

Here's where we pull out our secret weapon – the alias:

```verse
# Alias for backward compatibility
GetPlayerDataForPlayer<public>(Agent:agent)<transacts><decides>:player_data = GetPlayerData[Agent]
```

This is like setting up a redirect from your old gamertag to your new one – all the old references still work, but new code can use the shorter name.

## Understanding the Approach (Or: "Why This Won't Break Your Build")

Let's break down why this solution works perfectly:

1. **Clear Context**: The function is already in a player-focused context, so "ForPlayer" is as redundant as a double shield potion at full shields.

2. **Type Safety**: The `Agent` parameter type makes it crystal clear what we're dealing with – like having a clearly marked pickup in game.

3. **Return Clarity**: The `player_data` return type tells us exactly what we're getting back – no mystery loot boxes here.

4. **Verse Style**: Verse favors concise but clear names, like a well-designed UI that shows exactly what you need.

## Why This Works (The Technical Deep Dive)

Let's visualize the relationship between our old and new functions:

```mermaid
graph TD
    A[Client Code] --> B{GetPlayerDataForPlayer}
    B -->|Alias| C[GetPlayerData]
    C --> D[Session Data]
    D --> E[Player Data]
    style B fill:#ff2a6d,stroke:#fff,stroke-width:2px
    style C fill:#05d9e8,stroke:#fff,stroke-width:2px
```

The alias acts as a bridge, ensuring that:
- Old code continues to work flawlessly
- New code can use the cleaner name
- No functionality is changed
- We can gradually update references

## Conclusion

Renaming `GetPlayerDataForPlayer` to `GetPlayerData` is like upgrading your loadout – it's more efficient, cleaner, and just feels right. With our backward compatibility alias in place, we've achieved the perfect balance between improving our codebase and maintaining stability.

Remember: Good function names are like good emotes – short, memorable, and they get the job done with style.

---
*Note: No functions were harmed in the making of this article. The original function name is now living happily in retirement as an alias.*


Verse Function Renaming: The Art of Clean Code Through Smart Aliases


# So Your Fancy 10GbE Network Adapter Keeps Ghosting You: A Survival Guide

*Because getting disconnected in Fortnite is scarier than facing a horde of carnival zombies with nothing but a common pistol and a dream*

Listen, we get it. You spent good money on that shiny new motherboard with its promised blazing-fast 10GbE networking, only to find yourself in an on-again-off-again relationship with your internet connection. Like a Fortnite player who just lost their legendary loot to a disconnect, you're probably feeling pretty salty right now. Don't worry – you're not alone in this digital heartbreak. Let's fix that temperamental Marvell AQtion adapter faster than a Zero Build sweat can crank 90s.

## What Even Is 10GbE? (For Those Who Just Bought What Looked Expensive)
Think of 10GbE like finding a Supply Llama filled with networking speed. It's theoretically capable of transferring data at up to 10 gigabits per second – that's fast enough to move your entire Fortnite installation folder in the time it takes to drink a mini shield potion. When it works, it's amazing. When it doesn't... well, that's why you're here.

## The Symptoms (Or: "It's Not You, It's Your Network Adapter")

If you're experiencing any of these signs of network adapter rebellion:
- Random disconnections that make you question your life choices (and cost you Victory Royales)
- Connection drops during large Steam downloads (because obviously it would happen right as you're downloading the latest Unreal Engine)
- Speeds that make your old dial-up modem look ambitious
- The need to constantly perform the sacred ritual of "disable and re-enable network adapter"
- Ping spikes higher than a Fortnite rocket ride
- Your network adapter disappearing more often than a bush camper

## The Solutions (In Order of "Yeah, This Might Actually Work")

### 1. The Power Management Powerplay
First, let's tell Windows to stop trying to save power like it's hoarding shield potions:

1. Open Device Manager (like opening your inventory, but for your PC)
2. Find your Marvell AQtion adapter
3. Right-click → Properties
4. Go to the "Power Management" tab
5. \*\*Uncheck\*\* "Allow the computer to turn off this device to save power"
   (Because who thought putting your network card to sleep was a good idea anyway?)
6. Click Apply

### 2. The Advanced Tab Adventure
Time to dive into the advanced settings like you're dropping into Tilted Towers. Here's what each setting actually does (we know you're curious):

```
Energy-Efficient Ethernet: Disabled
(Because saving the planet is important, but not as important as your K/D ratio)
- This feature tries to save power during low network activity, but ends up causing more crashes than a bot's first build battle

Interrupt Moderation & Rate: Disabled
(Like turning off input lag for your network card)
- These settings control how often your network card interrupts your CPU
- Disabling them makes your connection more responsive than a pro player's edit speed

Speed & Duplex: 10 Gbps Full Duplex
(Manual > Auto, like choosing your landing spot instead of using auto-drop)
- Forces your connection to run at full speed instead of letting it get lazy
- Full duplex means data flows both ways simultaneously, like building and shooting at the same time

NDIS QoS: Enabled
(Quality of Service - like SBMM but for your network packets)
- Helps prioritize important network traffic
- Makes sure your gaming packets don't get stuck behind someone's Netflix stream
```

### 3. Optional Performance Tweaks (For the Sweats)
For when you want your network to perform like it's in the FNCS finals:

```
Jumbo Packets: 9014 bytes
(Like carrying more mats in one slot)
- Allows larger data packets to be transferred at once
- Only enable if your entire network supports it, or you'll create more problems than a prankster with a boom box

Flow Control: Disabled
(The networking equivalent of "just build, lol")
- Controls the "speed limit" of data transfer
- Some cards perform better with traffic jams than with police
```

### 4. Static IP Setup (Because Sometimes You Need a Home Base)
Why set a static IP? Here's the deal:

- It's like marking your favorite landing spot on the map – your PC will always know where to find its network location
- Perfect for:
  * Running a home media server (for watching those Victory Royale replays)
  * Port forwarding (for hosting creative maps)
  * Network attached storage (for saving all your clutch clips)
  * Making sure your PC doesn't get assigned a new IP address more often than meta changes

Here's how to set it up in Windows 11 (easier than finding a common chest):

1. Settings → Network & Internet → Ethernet
2. Click on your network adapter
3. Click "Edit" under IP assignment
4. Change from DHCP to Manual
5. Toggle on IPv4
6. Enter your desired settings:
   - IP address (like 192.168.1.100) - Your PC's permanent address in the network lobby
   - Subnet mask (typically 255.255.255.0) - Defines your local network's size
   - Gateway (your router's IP, usually 192.168.1.1) - Your connection to the outside world
   - Preferred DNS (8.8.4.4 for Google) - The phonebook that converts website names to IP addresses
   - Alternate DNS (8.8.8.8 for backup) - Backup phonebook when the first one is taking a chug jug

### Understanding Network Settings (Or: "What Are All These Numbers?")
Think of your network settings like your Fortnite loadout:

- \*\*IP Address\*\*: Your locker number in the giant internet gym
- \*\*Subnet Mask\*\*: The zone that defines where your teammates can find you
- \*\*Gateway\*\*: The battle bus that takes your data to the internet
- \*\*DNS\*\*: The map that shows where all the good websites are hiding
- \*\*Jumbo Packets\*\*: Like carrying a whole inventory of items in one slot
- \*\*Flow Control\*\*: Traffic lights for your data (that nobody wants to stop at)

## Conclusion

Remember, you're not alone in this struggle. Thousands of other users are out there, cursing at their network adapters just like you curse at third-party interventions. Until Marvell releases that mythical firmware update we've all been dreaming about (about as likely as Epic removing building), these workarounds are your best bet for maintaining your sanity.

And hey, if all else fails, there's always carrier pigeons. They might be slower than a default skin with a grey pistol, but at least they don't need driver updates. Plus, they're probably more reliable than the Marvell AQtion on a bad day.

---
*Note: This guide was written by sleep-deprived network administrators who have spent way too many hours staring at Device Manager while getting eliminated in Fortnite. No network adapters were harmed in the making of this guide (though we really wanted to yeet them into the storm). If you see us in-game, please don't eliminate us – we're probably troubleshooting our network connection anyway.*


Network Adapter Survival Guide: Taming the Rebellious Marvell AQtion

# Github Copilot Enterprise Setup

Fianlly got access to github copilot enterprise so going through getting it setup and configured.



If you don't already have Github Copilot installed you'll want to add the extensions:

Name: GitHub Copilot Chat
Id: GitHub.copilot-chat
Description: AI chat features powered by Copilot
Version: 0.22.4
Publisher: GitHub
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=GitHub.copilot-chat



Name: GitHub Copilot
Id: GitHub.copilot
Description: Your AI pair programmer
Version: 1.249.0
Publisher: GitHub
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=GitHub.copilot



![image-20241210173205870](github-copilot-outputwindow.png)

### Code completions

GitHub Copilot provides autocomplete-style suggestions from an AI pair programmer as you code. Just start writing your code in the editor and Copilot provides you with relevant suggestions. Need something specific? Add a natural language code comment to give directions to Copilot about what you want.

![Example of Copilot code completions in test.js](js-suggest.png)

### Chat

Sometimes you just want to ask a question. Whether you're troubleshooting a bug or crafting a new feature, GitHub Copilot is here to assist when you encounter challenges – simply ask for guidance via chat.

**[Chat view](https://code.visualstudio.com/docs/editor/github-copilot#_chat-view)**:

Ask Copilot for help with any task or question in the Chat view, bringing in code from your current files. Copilot is not just a search engine. Rather than giving you a generic answer, it can give answers that are relevant for your codebase.

![Chat view in VS Code](copilot-view.png)

**[Inline Chat](https://code.visualstudio.com/docs/editor/github-copilot#_inline-chat)**:

Apply Copilot's AI suggestions directly to your code, staying in the flow. Need help with refactoring a method, adding error handling, or explaining a complex algorithm? Just launch Copilot in the editor!

![Inline chat in VS Code](inline-chat-question-example.png)

**[Quick Chat](https://code.visualstudio.com/docs/editor/github-copilot#_quick-chat)**:

Do you just want to ask a quick question and immediately get back in the action? Open Quick Chat with the **Chat: Open Quick Chat** command , or use the `Ctrl+Shift+I` or `Cmd+Shift+I` keyboard shortcut.

![Quick Chat in VS Code](quick-chat-dropdown.png)

### Participants

Participants are experts in a particular domain, such as coding, the editor, or many other areas. You can tag them in any chat to scope your questions and get better answers.

Below are examples of using participants built into VS Code.

**@workspace** ![Using the workspace chat participant](participants-workspace.gif)

**@terminal** ![Using the terminal chat participant](participants-vscode.gif)

**@vscode** ![Using the VS Code chat participant](participants-terminal.gif)

### Slash commands

Chat participants can also contribute what we call slash commands, which are shortcuts to specific functionality. Slash commands give you access to meticulously crafted prompts for common coding workflows, no prompt engineering required.

Below are examples of using several slash commands.

**/fix** ![Using /fix in VS Code](slash-fix.gif)

**/doc** ![Using /doc in VS Code](slash-doc.png)

**/tests** ![Using /tests in VS Code](slash-tests.gif)

### Variables

Variables enable you to reference specific information in your code, the editor, or information from other extensions. Combine these with participants to easily pass all the necessary context to Copilot.

**#file** ![Using the file variable in VS Code](variables-file.gif)

**#terminalLastCommand** ![Using the terminal last command variable in VS Code](variables-terminalLastCommand.gif)

### Supported languages and frameworks

GitHub Copilot works on any language, including Java, PHP, Python, JavaScript, Ruby, Go, C#, or C++. Because it��s been trained on languages in public repositories, it works for most popular languages, libraries and frameworks.

### Version compatibility

As Copilot Chat releases in lockstep with VS Code due to its deep UI integration, every new version of Copilot Chat is only compatible with the latest and newest release of VS Code. This means that if you are using an older version of VS Code, you will not be able to use the latest Copilot Chat.

Only the latest Copilot Chat versions will use the latest models provided by the Copilot service, as even minor model upgrades require prompt changes and fixes in the extension. An older version of Copilot Chat will still use the latest version of Copilot completions.

## Commands for CoPilot Extension

All of these settings and Commands can be found inside the Extension Settings. 

In order to open and use these you'll need to access the VS Code Parameter menu, hold CTRL + SHIFT + P 

| ID                                         | Title                                     | Keyboard Shortcuts | Menu Contexts                                       |
| :----------------------------------------- | :---------------------------------------- | :----------------- | :-------------------------------------------------- |
| `editor.action.inlineSuggest.trigger`      |                                           | Alt+\              |                                                     |
| `github.copilot.acceptCursorPanelSolution` | Accept panel suggestion at the cursor     | Ctrl+/             | `commandPalette`                                    |
| `github.copilot.collectDiagnostics`        | Collect Diagnostics                       |                    | `commandPalette`                                    |
| `github.copilot.generate`                  | Open Completions Panel                    | Ctrl+Enter         | `commandPalette` `editor/inlineCompletions/actions` |
| `github.copilot.nextPanelSolution`         | Navigate to the next panel suggestion     | Alt+]              | `commandPalette`                                    |
| `github.copilot.openLogs`                  | Open Logs                                 |                    | `commandPalette`                                    |
| `github.copilot.previousPanelSolution`     | Navigate to the previous panel suggestion | Alt+[              | `commandPalette`                                    |
| `github.copilot.sendFeedback`              | Send Feedback                             |                    | `commandPalette`                                    |
| `github.copilot.signIn`                    | Sign In                                   |                    | `commandPalette`                                    |
| `github.copilot.toggleCopilot`             | Enable/Disable Copilot completions        |                    |                                                     |

### Settings

These enable some extra features	

| ID                                            | Description                                                  | Default                                                      |
| :-------------------------------------------- | :----------------------------------------------------------- | :----------------------------------------------------------- |
| `github.copilot.advanced`                     |                                                              | `{} `                                                        |
| `github.copilot.editor.enableAutoCompletions` | Automatically show inline completions                        | `true `                                                      |
| `github.copilot.enable`                       | Enable or disable Copilot completions for specified [languages](vscode-file://vscode-app/c:/Users/Biza/AppData/Local/Programs/Microsoft VS Code/resources/app/out/vs/code/electron-sandbox/workbench/workbench.html) | `{  "*": true,  "plaintext": false,  "markdown": false,  "scminput": false } ` |
| `github.copilot.inlineSuggest.enable`         | Show inline suggestions                                      |                                                              |



## Commands for CoPilot Chat

In order to open and use these you'll need to access the VS Code Parameter menu, hold CTRL + SHIFT + P 

Commands

| ID                                                           | Title                                                       | Keyboard Shortcuts | Menu Contexts                                                |
| :----------------------------------------------------------- | :---------------------------------------------------------- | :----------------- | :----------------------------------------------------------- |
| `github.copilot.buildLocalWorkspaceIndex`                    | Build Local Workspace Index                                 |                    | `commandPalette`                                             |
| `github.copilot.chat.attachFile`                             | Add File to Chat                                            |                    | `commandPalette` `copilot`                                   |
| `github.copilot.chat.attachSelection`                        | Add Selection to Chat                                       |                    | `commandPalette` `copilot`                                   |
| `github.copilot.chat.explain`                                | Explain                                                     |                    | `copilot`                                                    |
| `github.copilot.chat.explain.palette`                        | Explain                                                     |                    | `commandPalette`                                             |
| `github.copilot.chat.fix`                                    | Fix                                                         |                    | `commandPalette` `copilot`                                   |
| `github.copilot.chat.generate`                               | Generate This                                               |                    | `commandPalette`                                             |
| `github.copilot.chat.generateDocs`                           | Generate Docs                                               |                    | `commandPalette` `copilot`                                   |
| `github.copilot.chat.generateTests`                          | Generate Tests                                              |                    | `commandPalette` `copilot`                                   |
| `github.copilot.chat.review`                                 | Review and Comment                                          |                    | `commandPalette` `copilot`                                   |
| `github.copilot.chat.review.apply`                           | Apply                                                       |                    | `commentsView/commentThread/context` `copilot/reviewComment/additionalActions/apply` |
| `github.copilot.chat.review.applyAndNext`                    | Apply and Go to Next                                        |                    | `copilot/reviewComment/additionalActions/apply`              |
| `github.copilot.chat.review.changes`                         | Copilot Code Review - Uncommitted Changes                   |                    | `scm/title`                                                  |
| `github.copilot.chat.review.continueInChat`                  | View in Chat Panel                                          |                    | `comments/commentThread/title`                               |
| `github.copilot.chat.review.continueInInlineChat`            | Discard and Copy to Inline Chat                             |                    | `copilot/reviewComment/additionalActions/discard`            |
| `github.copilot.chat.review.discard`                         | Discard                                                     |                    | `commentsView/commentThread/context` `copilot/reviewComment/additionalActions/discard` |
| `github.copilot.chat.review.discardAll`                      | Discard All                                                 |                    | `comments/commentThread/title` `commentsView/commentThread/context` |
| `github.copilot.chat.review.discardAndNext`                  | Discard and Go to Next                                      |                    | `copilot/reviewComment/additionalActions/discard`            |
| `github.copilot.chat.review.markHelpful`                     | Helpful                                                     |                    | `comments/comment/title`                                     |
| `github.copilot.chat.review.markUnhelpful`                   | Unhelpful                                                   |                    | `comments/comment/title`                                     |
| `github.copilot.chat.review.next`                            | Next Suggestion                                             |                    | `comments/commentThread/title`                               |
| `github.copilot.chat.review.previous`                        | Previous Suggestion                                         |                    | `comments/commentThread/title`                               |
| `github.copilot.chat.review.stagedChanges`                   | Copilot Code Review - Staged Changes                        |                    | `scm/resourceGroup/context`                                  |
| `github.copilot.chat.review.unstagedChanges`                 | Copilot Code Review - Unstaged Changes                      |                    | `scm/resourceGroup/context`                                  |
| `github.copilot.debug.collectDiagnostics`                    | GitHub Copilot Chat Diagnostics                             |                    | `commandPalette`                                             |
| `github.copilot.debug.generateConfiguration`                 | $(sparkle) Generate Debug Configuration with GitHub Copilot |                    | `commandPalette` `debug/createConfiguration`                 |
| `github.copilot.debug.generateInlineEditTests`               | Generate Inline Edit Tests                                  |                    | `commandPalette` `editor/title`                              |
| `github.copilot.debug.generateSTest`                         | Generate STest From Last Chat Request                       |                    | `commandPalette`                                             |
| `github.copilot.debug.workbenchState`                        | Log Workbench State                                         |                    | `commandPalette`                                             |
| `github.copilot.devcontainer.generateDevContainerConfig`     | Generate Dev Container Configuration with Copilot           |                    |                                                              |
| `github.copilot.git.generateCommitMessage`                   | Generate Commit Message with Copilot                        |                    | `scm/inputBox`                                               |
| `github.copilot.interactiveSession.feedback`                 | Send Chat Feedback                                          |                    | `commandPalette` `view/title`                                |
| `github.copilot.open.walkthrough`                            | Open Walkthrough                                            |                    | `commandPalette`                                             |
| `github.copilot.terminal.explainTerminalLastCommand`         | Explain Last Command (Terminal)                             |                    | `commandPalette`                                             |
| `github.copilot.terminal.explainTerminalSelection`           | Explain This (Terminal)                                     |                    | `commandPalette`                                             |
| `github.copilot.terminal.explainTerminalSelectionContextMenu` | Explain This                                                |                    | `terminal/copilot`                                           |
| `github.copilot.tests.fixTestFailure`                        | Fix Test Failure                                            |                    | `testing/message/context`                                    |
| `github.copilot.tests.fixTestFailure.fromInline`             | Fix Test Failure                                            |                    | `testing/item/context` `testing/item/result`                 |
| `github.copilotChat.signIn`                                  | Sign in to GitHub.com                                       |                    | `commandPalette`                                             |
| `github.copilotChat.signInChoose`                            | Sign in to...                                               |                    | `commandPalette`                                             |
| `github.copilotChat.signInGHE`                               | Sign in to GHE.com                                          |                    | `commandPalette`                                             |
| `inlineChat.start`                                           |                                                             |                    | `copilot`                                                    |
| `inlineChat.startWithCurrentLine`                            |                                                             | Windows+I          |                                                              |
| `workbench.action.terminal.chat.start`                       |                                                             |                    |                                                              |

Github Copilot Enterprise Setup


# "Help! My VSCode/Cursor Lost Its Verse-atility: A Guide to Fixing Verse Linting"

*Is your VSCode/Cursor acting like it's never heard of Verse? Are those comforting red squiggles missing in action? Let's get your development environment back to being as judgy as a Fortnite lobby.*

**![image-20241210101300673](vscode-problems-window-not-working.png)*

## The Symptoms

If you're staring at pristine, squiggle-free code that you KNOW has more issues than a default dancing Jonesy, you're probably experiencing the dreaded Verse linting outage. The key indicators are:

- Empty Problems window (as lonely as Retail Row at 3am)
- No syntax highlighting
- Code that looks perfect (we all know that's suspicious)

## The Diagnosis

The issue usually stems from our Verse Language Server Protocol (verse-lsp) taking an unexpected vacation. Here's how to investigate:

1. **Check the Output Tab** Open VSCode's Output panel (View > Output) and select "VerseExt" from the dropdown. You should see verse-lsp-latest.exe in the logs. If it's missing, it's like trying to build without materials - ain't gonna work.![image-20241210100949284](vscode-output-verseext.png)
2. **Task Manager Reconnaissance** Open Task Manager and look for verse-lsp-latest.exe. If you're using both VSCode AND Cursor (you overachiever, you), you might see multiple instances. That's normal - they're like squadmates, each doing their own thing.

![taskmgr-verse-lsp](taskmgr-verse-lsp.png)

workspace - ![image-20241210102208853](vscode-open-workspace-settings-verse.png)  

## The Cure

Time to hit this bug like a well-placed pickaxe swing. Here's your step-by-step healing potion:

1. ​	**Open Workspace Settings** Press `Ctrl+Shift+P` (or `Cmd+Shift+P` for Mac users) and type "Open Workspace Settings (JSON)". Select it faster than you'd grab a gold SCAR.

![image-20241210100813119](vscode-open-workspace-settings-verse.png)

2. ​	**Configure Your Settings** Your workspace settings should look something like this:

```json
{
  "launch": {
    "configurations": [
      {
        "name": "Verse Debug",
        "type": "verse",
        "request": "attach",
        "debugServer": 1961
      }
    ],
    "version": "0.2.0"
  }
}
```

![image-20241210101130105](vscode-verse-linting-workspace-config.png)

The `debugServer` port (1961) should match your current UEFN version. Think of it like making sure you're on the right game server - you wouldn't want to load into Save the World when you're trying to play Battle Royale!

## The Prevention

To keep your environment healthy and your code properly criticized:

1. Always open your UEFN project through the Epic Games Launcher
2. Make sure you're running the latest version of VSCode/Cursor
3. Keep your Verse extension updated
4. Don't mess with the verse-lsp process (it's more sensitive than a sweat in zero-build mode)

Now you should have proper errors in your code and under your problems Window 

![image-20241210101419870](vscode-problems-window-now-working.png)

## The Plot Thickens: Special Cases & Common Pitfalls

### The OneDrive Dilemma

*If your project folders are living in OneDrive, they're about as useful as a grey pistol in the final circle.*

Since UEFN version 31.20, there's actually a warning about this, but here's the deal: OneDrive and UEFN go together like Peely and a banana slicer. The remote storage access is about 10x slower than your local SSD, which can cause our verse-lsp to throw in the towel.

**Correct Project Paths by OS:**

- Windows 11:
  - ❌ `C:\Users\YourName\OneDrive\Documents\UnrealEngine` (Will break faster than a zero-build sweaty's building habits)
  - ✅ `C:\Users\YourName\Documents\UnrealEngine` (This is the way)
- Windows 10:
  - ✅ `C:\Users\YourName\source\repos\UnrealEngine`

### The Fresh Start Approach

Sometimes your VSCode project needs a reset like a fresh match. If you've created your .verse files outside of UEFN (you rebel, you), the verse server might be giving you the cold shoulder. Here's the proper way:

1. Launch UEFN first (yes, order matters, like landing before looting)
2. Create your new project through UEFN
3. Add your verse files through UEFN's interface
4. Use the "Verse" button in UEFN to launch VSCode

This ensures the verse server initializes properly, like making sure your drop zone has actual loot.

### The Extension Checkup

If you're still not seeing those beautiful red squiggles:

1. Check your Verse extension version (currently at `1.0.30426467` or newer)
2. Verify the extension folder exists: `%userprofile%.vscode\extensions\epicgames.verse-1.0.xxxxx`
3. If things look sus, try this nuclear option:
   - Delete the entire extension folder
   - Reinstall using the `.vsix` file
   - Restart VSCode (and maybe do a little dance)

### The Pipeline Problem

Sometimes the communication pipeline between UEFN and VSCode breaks down worse than team communication in Fill matches. If this happens:

1. Check the Output tab for "VerseExt" messages
2. Verify verse-lsp.exe is running in Task Manager
3. If either is missing, try the old reliable:
   - Close VSCode
   - Close UEFN
   - Reopen UEFN
   - Launch VSCode through UEFN's Verse button
   - Cross your fingers (optional but recommended)

Remember, just like knowing the perfect time to pop a shield, timing matters when launching these applications. UEFN first, VSCode second - this is the way.

## Still Having Issues?

If your linting is still ghosting you harder than your random duos partner:

1. Restart VSCode/Cursor
2. Check for any conflicting extensions
3. Verify your UEFN installation
4. Consider a clean reinstall (the programming equivalent of "have you tried turning it off and on again?")

Remember, a properly configured development environment is like a well-organized loadout - it makes everything easier and more effective. Now get back out there and make something amazing! Just don't forget to thank your linter for keeping your code cleaner than a Creative island on day one.

*P.S. If all else fails, you can always blame it on lag. Works every time, 60% of the time.*

VSCode lost it's Verse-atility - Fixing Verse Linting

## The Setup: What Happens in Git, Stays in Git... Or Does It?

You know that feeling when you wake up after spring break, check your phone's photo gallery, and find 1,372 nearly identical selfies from that one party? Yeah, that's basically what happened to our Git repository, except instead of embarrassing photos, we had thousands of automated commits partying in our git log like it was 1999.

Picture this: You're casually reviewing your repo one morning, coffee in hand, when suddenly you discover your automated sync script has been on a commit binge. Every single file sync created its own commit, each one shouting "Sync from Vercel: bizanator.md" like that one friend who keeps telling the same story at different volumes as the night goes on.

That's exactly what happened to us while building BrainDeadTV. Our script wasn't just doing its job - it was living its best life, creating commits like they were going out of style. It was less "continuous integration" and more "continuous intoxication" of our git history.

## The Problem: The Morning After

Our Git history went from this responsible, professional-looking log:

```
* feat: add cool new feature
* fix: resolve edge case
* feat: implement user feedback
```

To looking like a frat party guest list:

```
* Sync from Vercel: bizanator.md
* Sync from Vercel: bizanator.md #YOLO
* Sync from Vercel: bizanator.md #PartyTime
* Sync from Vercel: bizanator.md #OneMoreWontHurt
* Sync from Vercel: bizanator.md #NoRegrets
* (... and 995 more commits that we totally regret)
```

Time for some Git rehab.

## The Solution: Operation Git Detox

### Attempt 1: The "Hair of the Dog" Approach

First, we tried the classic Git rebase command, like trying to cure a hangover with more drinks:

```bash
git rebase -i HEAD~2100
```

Git's response? `fatal: invalid upstream 'HEAD~2100'` - basically, "Nah bro, that's way too many. Maybe drink some water instead?"

### Attempt 2: The "Let VS Code Handle It" Intervention

We thought VS Code might be our designated driver in this situation:

```bash
git config --global core.editor "code --wait"
```

But then reality hit - manually editing 2,100 lines in a rebase file? That's like trying to count how many drinks you had last night. Not happening.

### The Winning Solution: The Git Reset Cleanse

Here's our tried-and-true Git detox program:

1. Create a backup branch (like taking a screenshot of your Snapchat story before deleting it):

```bash
git checkout -b backup-branch
```

2. Soft reset to before things got out of hand:

```bash
git reset --soft 72a1c80  # The last commit we remember clearly
```

3. Create one clean commit (the "I'll never drink again" promise):

```bash
git commit -m "Squash automated sync commits into single commit"
```

4. Force push (responsibly, like texting your ex but with a friend checking your message first):

```bash
git push origin main --force-with-lease
```

## The Plot Twist: Merge Conflicts (AKA The Unexpected After-Party)

Just when we thought we were in the clear, merge conflicts showed up like uninvited guests. After attempting to handle them through GitHub's web interface (which felt like trying to eat soup with a fork), we went back to our trusty command line:

```bash
# The "Get Your Life Together" sequence
git checkout backup-branch
git pull origin backup-branch
git checkout main
git merge -X theirs backup-branch
```

But wait! The merge created a new commit - like that friend who shows up with more drinks when you're trying to leave the party. One final push to sobriety:

```bash
git checkout main
git reset --hard backup-branch
git push origin main --force-with-lease
git branch -d backup-branch
git push origin --delete backup-branch
```

## The Happy Ending: Git Rehab Success Story

Our Git history is now clean and sober, our sync script has been to commitment counseling (it now batches its commits), and our repository is back to being a productive member of society.

## Lessons Learned: Git Responsibility 101

1. Always have a backup branch (like a designated driver)
2. `git reset --soft` is your best friend (better than that "friend" who keeps buying shots)
3. `--force-with-lease` is safer than `--force` (like having a breathalyzer on your car)
4. When in doubt, hard reset to the last thing you remember clearly
5. Batch your commits (practice safe committing!)

Remember, friends don't let friends commit thousands of automated changes without batching. Happy coding! 🚀

---

## Handy Command Reference

Here are some useful Git commands that helped us through this adventure:

```bash
# View commit history with hashes (one line per commit)
git log --oneline

# View more detailed commit history with dates and authors
git log --pretty=format:"%h - %an, %ar : %s"

# Find commits by message content (great for finding automated commits)
git log --grep="Sync from Vercel"

# View history for a specific file
git log --follow -p -- path/to/file

# Show changes in a specific commit
git show <commit-hash>

# Count total commits
git rev-list --count HEAD
```

## Preventing Future Problems: Batch Commit Example

Here's a simple Node.js example of how to batch your automated commits instead of creating one per file:

```javascript
// batchCommit.js
const { execSync } = require('child_process');
const path = require('path');

async function batchCommitChanges(changedFiles, commitMessage) {
  try {
    // Stage all changed files
    for (const file of changedFiles) {
      execSync(`git add "${file}"`, { stdio: 'inherit' });
    }

    // Create a single commit with all changes
    const timestamp = new Date().toISOString();
    const message = `${commitMessage} [${timestamp}]\n\nFiles changed:\n${changedFiles.join('\n')}`;
    execSync(`git commit -m "${message}"`, { stdio: 'inherit' });

    // Push changes
    execSync('git push origin main', { stdio: 'inherit' });

    console.log(`Successfully batch committed ${changedFiles.length} files`);
  } catch (error) {
    console.error('Error during batch commit:', error);
    throw error;
  }
}

// Example usage in your sync script:
async function syncContent() {
  const changedFiles = [];
  
  // Your existing sync logic here
  // Instead of committing each file, add them to changedFiles array
  for (const file of filesToSync) {
    try {
      await downloadAndSaveFile(file);
      changedFiles.push(file.path);
    } catch (error) {
      console.error(`Failed to sync ${file.path}:`, error);
    }
  }

  // If we have any changes, batch commit them
  if (changedFiles.length > 0) {
    await batchCommitChanges(
      changedFiles,
      `Sync: Batch update of ${changedFiles.length} files`
    );
  }
}
```

With this approach, instead of creating hundreds of individual commits, you'll get a single, well-documented commit that looks like this:

```
Sync: Batch update of 25 files [2024-11-26T12:00:00.000Z]

Files changed:
content/bizanator.md
content/chones-only.md
content/city-of-brains-01.svg
...
```

## About the Author

This post was written by a Git survivor who learned that what happens in the command line doesn't always stay in the command line. They now run a small support group for repositories affected by automated commit addiction.

## Support Resources

- StackOverflow Anonymous
- Git Reset Rehab Center
- Commits Anonymous (CA) - "One commit at a time"

## Updates

- 2024-11-26: Added command reference and batch commit example code (now that we're thinking clearly)
- Original Post: 2024-11-26 (The Morning After)


Git Gone Wild: The Hangover - 1000 Commits Edition

# How to Organize OBS Recordings Using Filename Formatting Variables

Creating a well-organized content library is essential for any creator. This guide shows how to use OBS Studio, the Source Recorder plugin, and the Branch Output plugin to set up variable paths and filenames. By automatically sorting recordings into folders by month and year and naming files with detailed timestamps, you can streamline your workflow and simplify editing for platforms like YouTube.

---

## Why Organization Matters

- **Save Time**: Quickly locate specific recordings without hunting through cluttered directories.
- **Stay Consistent**: Maintain a standardized file naming and folder structure for all projects.
- **Streamline Editing**: Easily identify files by resolution, frame rate, and time for post-production.

---
![Obs Settings](obs-recording-organization-guide-content.jpg)
## Setting Up Your Recording Path and Folder

### 1. Define the Recording Path
1. Open OBS Studio.
2. Navigate to **Settings** > **Output** > **Recording**.
3. Set your **Recording Path** to a main folder (e.g., `C:\Recordings\OBS\`).

This folder will serve as the root directory for your recordings.

---

## Configuring Filename Formatting Variables

OBS Studio supports variables to automatically generate filenames. For instance, `%CCYY` for the year or `%ORES` for the output resolution. Use these to create a structured naming system.

### 3. Create Folder Names by Date
Set the first part of the **Filename Formatting** to:

```%CCYY_%MM_%B```




This creates folders like `2024_11_November`.

### 2. Customize File Names
Navigate to **Settings** > **Advanced** > **Recording** and set **Filename Formatting** to:


`%d_%A-%I_%mm_%p_%ORES_%FPSfps_%B%Y`


This will create filenames like:
23_Saturday-11_39_AM_1920x1080_30fps_November2024.mp4

### 4. Combine Folder and Filename
In order to use the folder name and filename together you can use the simply join them together with a backslash like this:

```%CCYY_%MM_%B\%d_%A-%I_%mm_%p_%ORES_%FPSfps_%B%Y```

Now you will have a structure like this:

C:\Recordings\OBS\2024_11_November\23_Saturday-11_39_AM_1920x1080_30fps_November2024.mp4


---
# Save Individual Recordings of each source
Take this one step further by using the Source Recorder or Branch Output plugins to save individual recordings of each source. This will allow you to have a recording for each source in the same folder structure, for example a separate recording for your camera and your screen. In multiple camera setups this will allow you to keep the recordings organized by date and time and camera name for easier editing.

## Why Use Source Recorder or Branch Output?

Both plugins enhance the default recording capabilities of OBS Studio:

- **Source Recorder**: Ideal for recording individual sources, such as specific cameras or screen captures.
- **Branch Output**: Offers advanced capabilities, including support for multiple sources, custom variables, and improved filename formatting.

Both tools help you automatically organize recordings with folders and filenames based on detailed metadata.

---

## Setting Up Source Recorder

### 1. Install Source Recorder
1. Download the **Source Recorder** plugin from the [OBS Forum](https://obsproject.com/forum/resources/source-record.1285/).
2. Extract the files and place them in your OBS Studio installation directory.
3. Restart OBS Studio.

### 2. Configure Source Recorder
1. Open OBS Studio.
2. Right-click a source (e.g., your camera feed) in the **Sources** list and select **Filters**.
3. Click the **+** button and add the **Source Record** filter.
4. Configure the **Recording Path** to:

 - C:\Recordings\OBS\

5. Set the **Filename Formatting** to:

`CCYY_%MM_%B%d_%A-%I_%mm_%p_%ORES_%FPSfps_%SOURCE_NAME`


### 3. Save Source-Specific Recordings
The plugin creates individual recordings for each source with descriptive filenames, such as:

2024_11_November\23_Saturday-11_39_AM_1920x1080_30fps_Camera1.mp4


---

## Setting Up Branch Output

### 1. Install Branch Output
1. Download the **Branch Output** plugin from [GitHub](https://github.com/OPENSPHERE-Inc/branch-output).
2. Follow the installation instructions to add the plugin to OBS Studio.

### 2. Configure Branch Output
1. Open OBS Studio.
2. Navigate to **Settings** > **Output** > **Recording**.
3. Under **Branch Output**, configure the **Recording Path** to:

C:\Recordings\OBS\
4. Set the **Filename Formatting** to:

%CCYY_%MM_%B%d_%A-%I_%mm_%p_%ORES_%FPSfps_%SOURCE_NAME

Branch Output organizes files similarly to Source Recorder but offers enhanced features for multi-source setups.

---

## Full List of Variables

Here is the complete list of variables you can use for filename formatting:

### Date and Time Variables
- `%CCYY`: Year (4 digits, e.g., 2024)
- `%YY`: Year (last two digits, e.g., 24)
- `%MM`: Month (01–12)
- `%DD`: Day of the month (01–31)
- `%hh`: Hour (24-hour format, 00–23)
- `%mm`: Minute (00–59)
- `%ss`: Second (00–59)
- `%a`: Abbreviated weekday name (e.g., Mon)
- `%A`: Full weekday name (e.g., Monday)
- `%b`: Abbreviated month name (e.g., Jan)
- `%B`: Full month name (e.g., January)
- `%I`: Hour (12-hour format, 01–12)
- `%p`: AM/PM designation

### OBS Metadata Variables
- `%ORES`: Output resolution (e.g., 1920x1080)
- `%FPS`: Frames per second (e.g., 30fps)
- `%CRES`: Base (canvas) resolution (e.g., 3840x2160)
- `%VF`: Video format (e.g., mp4)
- `%SOURCE_NAME`: Source name for the recording
- `%SCENE_NAME`: Active scene name during recording

### Advanced Variables
- `%RAND`: Random number
- `%UUID`: Universally unique identifier
- `%INDEX`: Auto-incremented number for recordings
- `%TICK`: Time in milliseconds since UNIX epoch
- `%TZ`: Timezone offset from UTC

---

## Example Workflow

### Folder Structure
With the above configuration, your recordings will automatically be organized like this:


C:\\Recordings\\OBS\\2024\_11\_November  
├── 23\_Saturday-11\_39\_AM\_1920x1080\_30fps\_Camera1.mp4 ├── 23\_Saturday-11\_45\_AM\_1280x720\_60fps\_ScreenCapture.mp4


### Multi-Camera Setup
1. Apply the Source Recorder filter to each camera source.
2. Assign unique filenames with `%SOURCE_NAME` for differentiation.
3. Files are saved as:
   - `23_Saturday-11_39_AM_1920x1080_30fps_Camera1.mp4`
   - `23_Saturday-11_39_AM_1920x1080_30fps_Camera2.mp4`

---


## Benefits of Organized Recordings

- **Efficiency**: Quickly locate files with consistent folder and filename structures.
- **Editing Simplicity**: Instantly identify recordings by resolution and source.
- **Scalability**: Handle large volumes of content effortlessly.
- **Professionalism**: Maintain a polished workflow ready for editors or collaborators.

---

## Video Tutorial

Learn more by watching this video guide:

<iframe width="560" height="315" src="https://www.youtube.com/embed/youtube-video-id" title="YouTube video player" frameborder="0" allowfullscreen></iframe>

---
## Advanced Tips

1. **Custom Variables**: Use `%UUID` for unique file identifiers in collaborative projects.
2. **Integration with Editors**: Combine `%ORES` and `%FPS` to quickly find files with specific resolutions and frame rates.
3. **Source-Based Recording**: Separate files by input source, ideal for multi-camera setups.


**Take your content creation to the next level with organized recordings.** Try out Source Recorder or Branch Output today and enjoy a streamlined workflow!






Organize OBS Recordings with Filename Variables

How to Organize OBS Recordings Using Filename Formatting Variables


# Your Post Title

Write your post content here using markdown.

## Sections

Use markdown formatting for your content:
- Lists
- **Bold text**
- *Italic text*
- [Links](https://example.com)
- Images: ![Alt text](/path/to/image.jpg)

## Code Blocks 

Sunoai Content Title

YouTube Video Title

Creator Name

SPider Powers

# Welcome to the BrainDead Gaming Community

Are you passionate about gaming, streaming, or game development? Looking for a community that combines all three? Welcome to BrainDead.Games, where we're building more than just games – we're crafting experiences that bring people together.

## Who We Are

We're a community of gamers, streamers, and developers who believe in the power of collaborative gaming experiences. Under the Biloxi Studios banner, we're pushing the boundaries of what's possible in multiplayer gaming, with a special focus on creating content that's as fun to watch as it is to play.

## What We Offer

### Custom Gaming Experiences

- **UEFN Creations**: Dive into our specially crafted Fortnite experiences designed for maximum community engagement
- **Custom Game Servers**: Join our variety of gaming servers, including our immersive GTA RP server
- **Streamer-Focused Content**: Experience games built with content creators in mind

### Development Community

- **Behind-the-Scenes Access**: Get involved in the development of City Of Brains and other exciting projects
- **Learn Game Development**: Access our Patreon for exclusive Verse programming tutorials and UEFN development insights
- **Collaborative Environment**: Connect with other UEFN creators and game developers

### Community Features

- **Active Discord Community**: Join discussions, find gaming partners, and participate in community events
- **Stream Integration**: Special features designed for streamers and their audiences
- **Regular Events**: Participate in community game nights, development workshops, and more

## Why Join Us?

Whether you're a:

- **Streamer** looking for unique content to share with your audience
- **Developer** wanting to learn UEFN and connect with other creators
- **Gamer** seeking new multiplayer experiences and a friendly community
- **Creator** interested in contributing to exciting gaming projects

There's a place for you in the BrainDead community.

## Current Projects

### City Of Brains

Get an exclusive look at our development process and contribute your ideas to this evolving project. Be part of the creative journey from concept to completion.

### Custom Server Experiences

Jump into our various game servers, each offering unique experiences:

- GTA RP Server for immersive roleplay
- Specialized multiplayer environments for content creators
- Community-driven gaming events

## Join Our Community

Ready to be part of something special? Here's how to join:

1. Join our Discord community
2. Connect with fellow creators and gamers
3. Access our custom servers and experiences
4. Get involved in ongoing projects
5. Start learning and creating

Whether you're here to Learn, Stream, Watch, or Play – there's always something exciting happening in the BrainDead community.

Join us today and be part of a community that's reshaping the future of multiplayer gaming and content creation!

[Discord Invite Link]
[Patreon Link for Developers]
[Social Media Links]

---

*BrainDead.Games - A Biloxi Studios Production*


Welcome to BrainDead Gaming Community

Join the BrainDead Gaming Community: Where Streamers, Gamers, and Creators Unite

# Mass vs. Jass: Lethal Lips

Step into the fiery showdown of words where wit is sharper than any blade! In Mass vs. Jass: Lethal Lips, two fierce Japanese warrior women trade verbal jabs in a battle of sass, style, and searing roasts. Armed with sharp tongues and scandalous style, they’ll fight to see who truly reigns supreme. Are you ready to join the ultimate clash of words? Let the roast battles begin!

## How to Play

Currently, this game doesn't have any player controls. The roast battle simulation runs automatically without user input. The characters take turns roasting each other based on AI-generated responses.

## Credits

List any assets, libraries, or other resources you used:
Sound effects from [AI Roast Battle Template v2]
Art by [RinEllaSky]
Built with [framework/engine : Rosebud AI Development]

## Development Notes

Share any interesting technical details or challenges you encountered while building the game.
Learned how to use bitmap font , in this case 'Monocrat' used in game. The font has character mappings, glyph dimensions, and references a png file, to render custom text in game with custom pixel perfect font. Particularly interesting because Bitmap fonts are specially formatted fonts that optimize well in these type of games!This ensures that text appears crisp and consistent across different devices and resolutions.
Did you know? Using a bitmap font can improve text rendering performance and maintain a consistent pixel art style throughout the game.

## Technical Requirements

### JavaScript Bundle

- Your game.js should be a self-contained bundle
- Must work when loaded as a script tag
- Should create and manage its own canvas element
- Must respect the container size provided
- Should handle window resize events appropriately

### Asset Loading

- All assets should be loaded relative to your GitHub repository
- Use absolute URLs to your raw GitHub content
- Example: `https://raw.githubusercontent.com/username/repo/branch/path/to/asset`

### Game Container

Your game will be loaded into a container with the following properties:

- Class: `game-canvas-container`
- Aspect ratio: 16:9
- Responsive width
- Dark background

### Performance

- Bundle size should be reasonable (under 5MB recommended)
- Game should maintain 60 FPS on modern browsers
- Include loading states for assets

## Testing Locally

1. Create your markdown file in the `posts` directory
2. Name it `your-game-name.md`
3. Ensure all required frontmatter fields are filled
4. Test your game loads and runs properly
5. Verify responsive behavior

## Submission Process

1. Host your game repository on GitHub
2. Make sure it's public and the main branch is stable
3. Create your markdown file following the template above
4. Submit a pull request to our repository with your markdown file
5. We'll review and provide feedback if needed

## Example Repository

Here's a minimal example repository showing the required structure:
[Example Minigame Repository](https://github.com/example/minigame-template)

## Common Issues

### Game Doesn't Load

- Check your repository path and branch name
- Verify the entryPoint path is correct
- Ensure all URLs are using raw.githubusercontent.com

### Asset Loading Fails

- Use absolute URLs from your GitHub repository
- Check file permissions and paths
- Verify assets are committed and pushed

### Performance Issues

- Optimize your bundle size
- Implement proper cleanup when game is unmounted
- Handle window resize events efficiently

## Support

If you need help or have questions:

1. Open an issue on our repository
2. Join our Discord server
3. Contact us at support@cityofbrains.com

## Testing Your Submission

Before submitting, verify:

- [ ] Game loads and runs
- [ ] Controls work as expected
- [ ] Assets load correctly
- [ ] Responsive design works
- [ ] No console errors
- [ ] Cleanup works when navigating away


Rinellasky

RinEllaSky

Mass Vs Jass: Lethal Lips


# Complete Guide: Building a Tag-Based Number System in Verse

## Introduction

### Why Build a Tag-Based Number System?
In Fortnite Creative, we often need to represent and manipulate numbers in devices and game logic. However, sometimes we need to:
- Store numbers in a way that's easily readable by devices
- Allow for dynamic number changes during gameplay
- Create number-based puzzles or scoring systems
- Handle special cases like zero or negative numbers

Our tag-based system solves these problems by representing numbers through combinations of tags that devices can easily read and modify.

### What We'll Learn
This tutorial covers:
1. Basic Verse programming concepts
2. Object-oriented programming principles
3. Tag system implementation
4. Validation and error handling
5. Practical game integration

### Prerequisites
- UEFN installed
- Basic programming knowledge
- Text editor or UEFN IDE
- Understanding of basic math concepts

## Part 1: Understanding the Basics

### What is a Tag?
In Verse, a tag is a simple marker that can be attached to objects. Think of it like a sticker - you can put multiple stickers on an object to give it different properties or meanings.

```verse
# This is how we define a basic tag
basic_tag := class(tag){}
```

### Our Number System Design
We'll represent numbers using four types of tags:
1. Ones place (0-9)
2. Tens place (00-90)
3. Hundreds place (000-900)
4. Thousands place (0000-9000)

For example, the number 1,234 would be represented as:
- thousands_1 (1000)
- hundreds_2 (200)
- tens_3 (30)
- ones_4 (4)

```mermaid
graph TD
    A[Number 1,234] --> B[thousands_1]
    A --> C[hundreds_2]
    A --> D[tens_3]
    A --> E[ones_4]
    B --> F[1000]
    C --> G[200]
    D --> H[30]
    E --> I[4]
    F & G & H & I --> J[Sum = 1,234]
```

### Initial Code Structure
Let's start by setting up our basic structure:

```verse
using { /Verse.org/Simulation/Tags }

tag_numbers := module:
    # Base tag class for all our number tags
    number_tag<public> := class(tag){}
    
    # Tag class for actual digits
    digit_tag<public> := class(number_tag){}
```

### Why This Structure?
- `module`: Creates a namespace for our code
- `number_tag`: Base class for all number-related tags
- `digit_tag`: Specific class for digit representation

This hierarchy allows us to:
1. Keep our code organized
2. Easily check if a tag is number-related
3. Add more number types later

## Understanding Modules and Namespaces
Think of modules like different folders on your computer. Just as you might have different folders for different types of files, modules help us organize our code into logical groups.

```mermaid
graph LR
    A[tag_numbers module] --> B[number_tag]
    B --> C[digit_tag]
    C --> D[ones_tags]
    C --> E[tens_tags]
    C --> F[hundreds_tags]
    C --> G[thousands_tags]
```

### Why Use Modules?
1. **Organization**: Keep related code together
2. **Encapsulation**: Hide implementation details
3. **Reusability**: Easy to import and use elsewhere
4. **Maintenance**: Easier to update and modify

## Basic Tag Implementation
Let's create our first digit tags:

```verse
# Ones place tags
ones_0 := class(digit_tag){}
ones_1 := class(digit_tag){}
ones_2 := class(digit_tag){}
# ... continue for 3-9

# Why this way?
# 1. Each number is its own class
# 2. Easy to check for specific numbers
# 3. Clear relationship between tags
```

### Practice Exercise 1
Try creating a simple module with a few number tags:

<details>
<summary>Exercise Solution</summary>

```verse
my_numbers := module:
    my_number_tag := class(tag){}
    
    # Create tags for 1, 2, 3
    number_one := class(my_number_tag){}
    number_two := class(my_number_tag){}
    number_three := class(my_number_tag){}
```
</details>


Complete Guide: Building a Tag-Based Number System in Verse


# Building an Advanced Security System in UEFN

Today we'll create a fully functional security system that can detect players, trigger alarms, activate defense turrets, and create security barriers. This tutorial will demonstrate how to combine multiple devices and create clean, modular code in Verse.

## Part 1: Understanding the Components

First, let's break down the devices we'll be using:

- `perception_trigger_device`: Acts as our security camera/motion detector
- `customizable_light_device`: Visual alarm indicator  
- `automated_turret_device`: Security response system
- `audio_player_device`: Alarm sound effects
- `barrier_device`: Security lockdown system

## Part 2: Basic Structure Setup

Let's start by creating our main security system class and setting up our device variables:

```verse
using { /Fortnite.com/Devices }
using { /Verse.org/Simulation }

# Security system that manages detection and response
security_system_device := class(creative_device):
    # Detection device that acts as our motion sensor
    var Detector : perception_trigger_device = perception_trigger_device{}
    
    # Alarm light that activates when system is triggered
    var AlarmLight : customizable_light_device = customizable_light_device{}
    
    # Defense turret that activates on security breach
    var DefenseTurret : automated_turret_device = automated_turret_device{}
    
    # Audio device for alarm sounds
    var AlarmSound : audio_player_device = audio_player_device{}
    
    # Security barrier for lockdown
    var SecurityBarrier : barrier_device = barrier_device{}
    
    # Time in seconds before system auto-resets
    @editable
    var AutoResetTime : float = 30.0
```

## Part 3: Event Setup and System Activation

Now let's implement the core security system logic:

```verse
    # Initialize system when experience starts
    OnBegin<override>()<suspends>:void=
        # Subscribe to detection events
        if(Detector:perception_trigger_device):
            Detector.AgentLooksAtDeviceEvent.Subscribe(OnIntruderDetected)
    
    # Called when an intruder is detected
    OnIntruderDetected(Agent:agent):void=
        # Activate all security measures
        ActivateSecuritySystem()
        # Start auto-reset timer
        spawn{AutoResetSequence()}
    
    # Activates all security components
    ActivateSecuritySystem():void=
        if(AlarmLight:customizable_light_device):
            AlarmLight.TurnOn()
        
        if(AlarmSound:audio_player_device):
            AlarmSound.Play()
            
        if(DefenseTurret:automated_turret_device):
            DefenseTurret.Enable()
            
        if(SecurityBarrier:barrier_device):
            SecurityBarrier.Enable()
```

## Part 4: Auto-Reset Implementation

Let's add the auto-reset functionality:

```verse
    # Handles the automatic reset sequence
    AutoResetSequence()<suspends>:void=
        # Wait for specified time
        Sleep(AutoResetTime)
        # Reset system
        DeactivateSecuritySystem()
    
    # Deactivates all security components
    DeactivateSecuritySystem():void=
        if(AlarmLight:customizable_light_device):
            AlarmLight.TurnOff()
        
        if(AlarmSound:audio_player_device):
            AlarmSound.Stop()
            
        if(DefenseTurret:automated_turret_device):
            DefenseTurret.Disable()
            
        if(SecurityBarrier:barrier_device):
            SecurityBarrier.Disable()
```

## Setting Up in UEFN

1. Create a new UEFN project or open an existing one
2. Place the required devices in your scene:
   - Perception Trigger Device
   - Customizable Light Device
   - Automated Turret Device
   - Audio Player Device
   - Barrier Device
3. Create a new Verse file and paste the complete code
4. Assign your devices to the corresponding variables in the security system device
5. Configure the AutoResetTime as needed

## Testing Your Security System

1. Enter Play mode
2. Approach the perception trigger's detection area
3. The system should activate:
   - Lights will turn on
   - Alarm will sound
   - Turret will activate
   - Barrier will enable
4. After the specified AutoResetTime, the system will automatically deactivate

## Customization Options

- Adjust the AutoResetTime to control how long the system stays active
- Configure the Perception Trigger's detection range and angle
- Customize the alarm sound and light patterns
- Position the barrier and turret for optimal coverage

This security system provides a foundation that you can build upon for your own creative experiences. Try adding additional features like:

- Multiple detection zones
- Different security levels
- Player team exceptions
- Custom reset conditions

Happy coding!

## Complete Code

```verse
using { /Fortnite.com/Devices }
using { /Verse.org/Simulation }

# Security system that manages detection and response
# Can be configured with various security devices and will automatically
# respond to intruders with configurable reset time
security_system_device := class(creative_device):
    # Detection device that acts as our motion sensor
    var Detector : perception_trigger_device = perception_trigger_device{}
    
    # Alarm light that activates when system is triggered
    var AlarmLight : customizable_light_device = customizable_light_device{}
    
    # Defense turret that activates on security breach
    var DefenseTurret : automated_turret_device = automated_turret_device{}
    
    # Audio device for alarm sounds
    var AlarmSound : audio_player_device = audio_player_device{}
    
    # Security barrier for lockdown
    var SecurityBarrier : barrier_device = barrier_device{}
    
    # Time in seconds before system auto-resets
    @editable
    var AutoResetTime : float = 30.0
    
    # Initialize system when experience starts
    OnBegin<override>()<suspends>:void=
        # Subscribe to detection events
        if(Detector:perception_trigger_device):
            Detector.AgentLooksAtDeviceEvent.Subscribe(OnIntruderDetected)
    
    # Called when an intruder is detected
    OnIntruderDetected(Agent:agent):void=
        # Activate all security measures
        ActivateSecuritySystem()
        # Start auto-reset timer
        spawn{AutoResetSequence()}
    
    # Activates all security components
    ActivateSecuritySystem():void=
        if(AlarmLight:customizable_light_device):
            AlarmLight.TurnOn()
        
        if(AlarmSound:audio_player_device):
            AlarmSound.Play()
            
        if(DefenseTurret:automated_turret_device):
            DefenseTurret.Enable()
            
        if(SecurityBarrier:barrier_device):
            SecurityBarrier.Enable()
    
    # Handles the automatic reset sequence
    AutoResetSequence()<suspends>:void=
        # Wait for specified time
        Sleep(AutoResetTime)
        # Reset system
        DeactivateSecuritySystem()
    
    # Deactivates all security components
    DeactivateSecuritySystem():void=
        if(AlarmLight:customizable_light_device):
            AlarmLight.TurnOff()
        
        if(AlarmSound:audio_player_device):
            AlarmSound.Stop()
            
        if(DefenseTurret:automated_turret_device):
            DefenseTurret.Disable()
            
        if(SecurityBarrier:barrier_device):
            SecurityBarrier.Disable()
```

Creating an Advanced Security System in UEFN

## Welcome to the End of the World (As We Know It)

In City of Brains, players step into the sneakers of a teenager whose concert plans go horrifically wrong when the zombie apocalypse crashes the party. Set in a vibrant metropolis where the dead are rising and the living are trying their best to keep their heads (literally), this multiplayer experience combines dark humor with survival horror in a way that will keep players coming back for seconds... and thirds... and brains.



## A Living City (Before it Wasn't)

Our world pulses with life through the voices of countless NPCs, each with their own story to tell before everything goes sideways. From the sassy barista who's seen it all to the street vendor who might just save your life with that hot dog, every character adds depth to our urban apocalypse.

### Sample Character Vignettes:

**Coffee Shop Barista - "Perky's Place"**

> "Hun, I can make your drink so strong it'll wake the dead... Oh wait, too soon?"

**Street Vendor - "Hot Dog Harry"**

> "These wieners are so good, they're to die for! *nervous laugh* I really need to work on my timing..."

**Gym Rat Outside Fitness Center**

> "Bro, I'm telling you, these gains are apocalypse-proof. Zombies can't bite through these guns!"

![A quiet city night](cityofbrains_alpha_HighresScreenshot_2025.04.14-14.06.26.png)

## Background Ambiance & City Chatter

Our city breathes through carefully crafted ambient dialogue that brings the pre-apocalyptic world to life:

- "No, Mom, I won't be late for dinner... unless the world ends or something!"
- "Did you see that guy stumbling around? Must've had a rough night at Toxic Tuesdays..."
- "I swear, these dating apps are full of nothing but braindead... Oh god, they're actually braindead!"

## Key Features

- Dynamic NPC interactions that evolve as the zombie outbreak progresses
- Rich character backstories that unfold through environmental storytelling
- Voice-acted dialogue powered by ElevenLabs AI, delivering emotional performances that range from humorous to horrifying
- Mature themes and clever wordplay that keep the tone playful yet edgy

## The Perfect Storm

City of Brains captures that precious moment when normal life transforms into chaos, when a teenager's biggest worry shifts from "Will I make it to the concert?" to "Will I make it, period?" It's a story about growing up fast when the world goes down slow, told through the eyes of characters who keep their sense of humor even as they lose their sense of security.

![Will prayer save you](cityofbrains_alpha_HighresScreenshot_2024.11.04-18.40.55.png)

## Join the Apocalypse

Ready to experience the end of the world from a fresh perspective? City of Brains awaits, where every NPC has a story, every corner holds a surprise, and every zombie was someone's barista just five minutes ago.

---
*City of Brains - Because surviving the apocalypse is better with friends... and a sense of humor.*




City of Brains - Where Horror Meats Humor


![Chones Only](chones-only.png)

In the neon-drenched streets of City of Brains, not everything is doom and gloom. Enter "Chones Only" - our latest addition to the cityscape where post-apocalyptic dining meets flamboyant service with a dash of roller-skating flair.

## The Concept

Picture this: a beachside restaurant where thicc Latin kings serve up chalupas on roller skates, wearing nothing but chones (underwear) and sass. It's the kind of establishment that could only exist in a world where zombies roam and normalcy took a permanent vacation.

Our mantra? "No skates? No chones? No service!" 

## Testing Suno AI V4

With Suno AI dropping their V4 model today (11/19/2024), we couldn't resist the opportunity to create something special. The new model's improved ability to handle complex arrangements and genre-blending made it perfect for our vision - a Latin Pop Broadway fusion that would make both RuPaul and Gloria Estefan proud.

## Game Integration

Chones Only isn't just a quirky concept - it's a fully realized location in our upcoming UEFN experience, City of Brains. While zombies may roam the streets outside, inside these walls, the only thing infectious is the rhythm and the service.

The restaurant serves as both a safe haven and a reminder that even in the darkest times, there's always room for joy, sass, and perfectly served chalupas.

Art by the talented @BizaNator brings our vision to life, creating a mascot that embodies everything Chones Only stands for - confidence, charm, and unapologetic fabulousness.

Stay tuned for more updates as we continue developing City of Brains. Until then, keep those roller skates polished and those chones fabulous! 🛼✨

<SunoaiPlayer trackId="610405cb-5265-446f-8672-1f8ae1af923e" />

#GameDev #UEFN #SunoAI #CityOfBrains

Chones Only Theme

Chones Only - Where Sass Meets Service

# Club Nuero | Northside, City of Brains
Want to get your dance on? Club Nuero is the place to be. Once you've got the power back on and cleared the dance floor of the undead, you can boogie on down to the sounds of the best DJs in the city.


District Theme

District Tour

Behind the Scenes

The Neural District

# Game Title
A detailed description of your game. This section will appear below the game canvas.

## How to Play
Explain your game's controls and objectives here. For example:
Use WASD or arrow keys to move
Space to jump
Click to interact
etc.
## Credits
List any assets, libraries, or other resources you used:
Sound effects from [source]
Art by [artist]
Built with [framework/engine]
## Development Notes
Share any interesting technical details or challenges you encountered while building the game.


## Technical Requirements

### JavaScript Bundle
- Your game.js should be a self-contained bundle
- Must work when loaded as a script tag
- Should create and manage its own canvas element
- Must respect the container size provided
- Should handle window resize events appropriately

### Asset Loading
- All assets should be loaded relative to your GitHub repository
- Use absolute URLs to your raw GitHub content
- Example: `https://raw.githubusercontent.com/username/repo/branch/path/to/asset`

### Game Container
Your game will be loaded into a container with the following properties:
- Class: `game-canvas-container`
- Aspect ratio: 16:9
- Responsive width
- Dark background

### Performance
- Bundle size should be reasonable (under 5MB recommended)
- Game should maintain 60 FPS on modern browsers
- Include loading states for assets

## Testing Locally

1. Create your markdown file in the `posts` directory
2. Name it `your-game-name.md`
3. Ensure all required frontmatter fields are filled
4. Test your game loads and runs properly
5. Verify responsive behavior

## Submission Process

1. Host your game repository on GitHub
2. Make sure it's public and the main branch is stable
3. Create your markdown file following the template above
4. Submit a pull request to our repository with your markdown file
5. We'll review and provide feedback if needed

## Example Repository

Here's a minimal example repository showing the required structure:
[Example Minigame Repository](https://github.com/example/minigame-template)

## Common Issues

### Game Doesn't Load
- Check your repository path and branch name
- Verify the entryPoint path is correct
- Ensure all URLs are using raw.githubusercontent.com

### Asset Loading Fails
- Use absolute URLs from your GitHub repository
- Check file permissions and paths
- Verify assets are committed and pushed

### Performance Issues
- Optimize your bundle size
- Implement proper cleanup when game is unmounted
- Handle window resize events efficiently

## Support

If you need help or have questions:
1. Open an issue on our repository
2. Join our Discord server
3. Contact us at support@cityofbrains.com

## Testing Your Submission

Before submitting, verify:
- [ ] Game loads and runs
- [ ] Controls work as expected
- [ ] Assets load correctly
- [ ] Responsive design works
- [ ] No console errors
- [ ] Cleanup works when navigating away

Bearback


# Welcome to the BrainDead.TV Community

Our community is the heart of BrainDead.TV. Here, creators and gamers come together to share their passion for gaming, development, and creative content.

## What You'll Find Here

- Community Events & Meetups
- Creator Spotlights
- Community Projects
- Collaboration Opportunities
- Gaming Sessions & Tournaments

Join us in building the most vibrant and supportive gaming community around!


Community Hub


# Dev Blog

Technical updates, development progress, and behind-the-scenes looks at our projects.

## Topics

- Development Updates & Changelogs
- Technical Deep Dives
- Architecture & Design Decisions
- AI & Tooling Experiments
- UEFN, Verse & Fortnite Development

Follow along as we build and iterate on our games and tools.


Dev Blog

# Expeirences and Projects

Building Co-opperative and multiplayer experiences with an emphasis on community engagement and stream worthy moments we make our games with our community in mind.  We're a small team of developers who love to create unique and fun experiences.

## What You'll Find Here

- UEFN / Fortnite Islands
- Unreal Engine Longer Term Project
- Custom Game Servers and Community Platforms

Join us in building the most vibrant and supportive gaming community around!


Brain Dead Games


# Lore

The world of BrainDead is a place where creators and gamers unite.

## Somtime in the future but not quite the past

- To be added

Let's get you started in the world of BrainDead.




World of BrainDead


# Minigames

Explore interactive minigames built by our community creators.

## Featured Experiences

- Community-Built Games
- Playable Demos
- Game Jams & Challenges
- Interactive Experiments

Jump in and play - every game is a new adventure.


Minigames


# Tutorials & Guides

Step-by-step guides to help you master game development, streaming, and creative technology.

## What You'll Learn

- UEFN & Verse Development
- Game Design Fundamentals
- Streaming & Content Creation
- Creative Tools & Workflows
- Debugging & Problem Solving

Whether you're just starting out or looking to level up, our tutorials have you covered.


Tutorials & Guides


# The Pile

Welcome to The Pile - where interesting ideas, random thoughts, and unique content finds a home. This is our catch-all category for posts that don't quite fit into our standard categories but are too good not to share.

## What You'll Find Here

- Experimental content
- Cross-category topics
- Unique perspectives
- Random discoveries
- Interesting ideas that defy categorization

Think of this as our digital junk drawer - except everything in here is actually useful, just hard to categorize. From unexpected tech discoveries to random gaming insights, if it's interesting but doesn't fit elsewhere, you'll find it here.

## Why "The Pile"?

Sometimes the most interesting discoveries come from unexpected places. This category exists to embrace that chaos, giving a home to content that breaks the mold or spans multiple categories.

Feel free to dive in - you never know what gems you might find! 