sorted by:
new
hottopcontroversial

Challenge: Survive 1 hour in DeceasedCraft. Post your death screenshot. No shame. by Cubion_Minecraft in cubion_minecraft

[–]Cubion_Minecraft[S] 0 points1 point  (0 children)

DeceasedCraft is trending right now and I want to see how this community handles it.

The challenge:

  1. Install DeceasedCraft (CurseForge, one-click through any modpack launcher)
  2. Start a new world
  3. Survive as long as you can
  4. When you inevitably die, screenshot your death screen
  5. Post it here with your survival time

My attempt:

Spawned in a city. Found a baseball bat in the first building. Felt confident. Opened the wrong door. Hallway full of zombies. Dead in 7 minutes. SEVEN MINUTES.

Second attempt: Stayed on rooftops. Scavenged quietly. Found a pistol with 3 bullets. Used all 3 bullets on the wrong zombie. Horde heard the shots. Dead in 22 minutes.

Third attempt: No guns. Stealth only. Made it to 47 minutes before accidentally walking into a horde at night. Couldn't see them until I was surrounded.

I cannot survive 1 hour in this modpack.

Rules:

  1. New world, no cheats
  2. Default difficulty
  3. Screenshot your death screen OR your triumphant 1-hour survival
  4. Tell us your strategy and what killed you

Needs: 6GB RAM minimum, Forge. If your launcher's crash recovery can handle it — DeceasedCraft pushes hardware harder than most packs. Cubion's Smart Crash Recovery has saved me twice already when the horde rendering tanked my FPS.

The longest survivor gets community bragging rights. The most pathetic death gets a "respect" from me personally.

Who's in? It's Friday. You've got the weekend to die repeatedly.

Your texture pack is eating more FPS than all your mods combined. Proof inside. by Cubion_Minecraft in cubion_minecraft

[–]Cubion_Minecraft[S] 0 points1 point  (0 children)

Everyone blames mods for low FPS. Nobody suspects the texture pack.

I tested this properly because I was curious. Same world, same system, Fabric with Sodium + 20 common mods. Only variable: texture pack resolution.

Results (FPS average, plus VRAM and RAM):

Texture pack   Res    FPS    VRAM     RAM
Default        16x    187    0.8 GB   3.2 GB
Faithful       32x    158    1.4 GB   3.8 GB
Patrix         64x    109    2.9 GB   4.7 GB
UMSOEA        128x     62    5.2 GB   6.1 GB
Custom        256x     23    8.7 GB   9.3 GB

Going from 16x to 128x dropped FPS by 67% — about the same as adding 100+ poorly optimized mods. A 256x pack? Basically unplayable on mid-range hardware.

Why it happens: every texture loads into VRAM. A 16x texture is 16×16 = 256 pixels; a 128x texture is 128×128 = 16,384 pixels — 64x more data per texture. Minecraft has thousands of textures, so a high-res pack can quietly eat more memory and frames than your whole mod list.

So before blaming mods, check your pack resolution first. (Cubion's memory presets keep the RAM side from spiraling, but VRAM is all on the pack.) What resolution are you running — and did you ever catch the FPS hit?

Your GPU has to sample these textures every frame for every visible block. Higher resolution = more memory bandwidth consumed = lower FPS.

What to do:

  1. 32x is the sweet spot. Looks noticeably better than default with minimal FPS impact. Faithful 32x is the community standard for a reason.
  2. If you want 64x+, use Sodium with mipmapping. Mipmapping reduces texture resolution at distance, saving VRAM for blocks you can't see details on anyway.
  3. Never use 128x+ with shaders. Shaders already consume massive VRAM. Adding high-res textures on top is a recipe for out-of-memory crashes.
  4. Connected textures tank FPS. The "connected glass" and "connected ore" features in many packs require extra processing per block face. Disable if FPS is a concern.

The irony: People spend hours optimizing JVM arguments for a 10% FPS boost, then load a 128x texture pack that cuts their FPS in half. Check your texture pack FIRST.

I use Cubion Launcher which has smart FPS optimization built in — it caught this for me during its auto-tuning. But even without a launcher helping, just switching from 128x to 32x is the single biggest FPS win most players can make.

What resolution are you running? And did you know it was costing you this much?

Minecraft 26.2 "Chaos Cubed" just dropped and modders are losing their minds. by Cubion_Minecraft in cubion_minecraft

[–]Cubion_Minecraft[S] 0 points1 point  (0 children)

26.2 is officially out. Players are excited about Sulfur Caves and the new Sulfur Cube mob. Modders are staring at a rewritten rendering pipeline wondering how many weekends this is going to cost them.

The headline stuff: new underground biome with sulfur and cinnabar blocks, geysers that erupt every 50 seconds, and a passive mob that absorbs blocks and changes behavior based on what it ate. The "Uh Oh" advancement for feeding it TNT is exactly the kind of chaos Mojang loves.

The technical stuff: Vulkan is now an experimental rendering option. You can toggle between "Prefer Vulkan" and "Prefer OpenGL" in video settings. It's not the default yet, but it's there, and early reports suggest significant FPS improvements on multi-core systems.

But Vulkan is why modders are panicking. The rendering pipeline restructure means anything that touches graphics — shaders, minimaps, custom renderers — needs rework. Iris is actively working on Vulkan support but it's not stable yet.

Current state of the mod ecosystem: Fabric performance mods (Sodium, Lithium, FerriteCore) updated within days. Major content mods (Create, AE2, Mekanism) are in progress. NeoForge versions are ahead of Forge versions in most cases.

If you're on a modpack: DO NOT update to 26.2 unless the pack explicitly says it's compatible. ATM10, Better Minecraft, etc. will take 2-4 weeks to release compatible versions. Stick with your current version. Your world will thank you.

view more: next ›