How Do I Install Pokémon Rising Ruby?

Pokémon Rising Ruby is Drayano’s difficulty and availability overhaul of Pokémon Omega Ruby for Nintendo 3DS. Together with its Alpha Sapphire counterpart, Pokémon Sinking Sapphire, it brings the Drayano-style enhancement formula into Generation 6.

Rising Ruby does not replace Hoenn with a completely different region or storyline. Instead, it rebuilds the gameplay around Omega Ruby. All 721 Pokémon available through Generation 6 can be obtained, Trainer teams are substantially stronger, most major bosses use six Pokémon, evolutions are changed to remove trade requirements, weaker Pokémon receive buffs, wild encounters are completely rebuilt, and many moves, abilities, items, Mega Stones, gifts, and static encounters are changed.

As of August 30, 2026, the latest official version remains:

Pokémon Rising Ruby v2.1.0

Drayano’s official Project Pokémon thread lists v2.1.0 as the current version, last updated October 16, 2016.

Unlike most Game Boy, GBA, and DS hacks, Rising Ruby is not simply an IPS, BPS, or xDelta patch. It was distributed as modified 3DS game files intended to be loaded through systems such as Luma3DS, HANS, or a compatible emulator’s LayeredFS/mod system. Drayano recommended Luma3DS with a CIA installation when the project was released.

In 2026, the easiest modern routes are:

Real Nintendo 3DS: Omega Ruby v1.0.0 + Luma3DS game patching + Rising Ruby v2.1 mod files

PC/Mac/Android: Your legally dumped Omega Ruby game + Azahar + Rising Ruby v2.1 mod files

Rom Professor does not host, provide, or link to copyrighted Pokémon Omega Ruby files, pre-patched .3ds/.cia games, encryption keys, or ROM-derived packages. Use your own legally obtained copy of Pokémon Omega Ruby and legitimate mod files.

What You Need Before Installing Pokémon Rising Ruby

You need:

• Pokémon Omega Ruby
• Rising Ruby v2.1.0 mod files
• A mod-capable Nintendo 3DS or compatible 3DS emulator
• A backup of your Omega Ruby save
• A backup of the unmodified game/dump
• The correct Rising Ruby files for your setup
• Omega Ruby running as v1.0.0, without the official game update overriding the hack

Pokémon Rising Ruby Installation Requirements

Requirement	Correct Choice
Hack	Pokémon Rising Ruby
Creator	Drayano
Base game	Pokémon Omega Ruby
Platform	Nintendo 3DS
Current version	v2.1.0
Last official update	October 16, 2016
Traditional IPS/BPS patch?	No
Mod method	RomFS / ExeFS / CRO-style files
Real hardware	Luma3DS LayeredFS/game patching
Modern desktop emulator	Azahar
Android emulator	Azahar
iPhone/iPad	Folium possible; more complicated
Base game version	Omega Ruby v1.0.0 recommended
Official ORAS update	Disable/remove for full mod behavior
All 721 Pokémon obtainable	Yes
Status	Complete

Drayano describes Rising Ruby and Sinking Sapphire as completed 721-Pokémon hacks and identifies v2.1.0 as their final current release.

What Is the Latest Version of Pokémon Rising Ruby?

The latest official release is:

Pokémon Rising Ruby v2.1.0

The official thread lists:

Current Version: v2.1.0

Last Updated: 16th October, 2016.

Version 2.1 fixed issues from the earlier v2 release, including a known Sinking Sapphire Trainer-level problem, and added some requested move changes plus alternate files that removed certain nonstandard modifications.

I could not verify any official:

• v2.2
• v3.0
• Rising Ruby Redux
• Rising Ruby DX

release from Drayano that supersedes v2.1.0.

For a new playthrough in 2026:

use Rising Ruby v2.1.0.

Is Pokémon Rising Ruby Complete?

Yes.

Drayano explicitly describes Rising Ruby as a:

completed 721 hack for Pokémon Omega Ruby.

It includes the complete Omega Ruby campaign:

• Hoenn
• Eight Gym Leaders
• Team Magma storyline
• Pokémon League
• Delta Episode
• Battle Resort
• Postgame legendary content

The story itself remains largely Omega Ruby because Generation 6 script editing was extremely limited when Rising Ruby was developed. Drayano specifically notes that the project focuses on enhancing the gameplay rather than rewriting the main story events.

What Does Pokémon Rising Ruby Change?

Rising Ruby dramatically changes the gameplay surrounding Omega Ruby.

Drayano’s official documentation lists changes including:

• All 721 Pokémon obtainable
• Completely rebuilt wild encounters
• 10–11 different Pokémon in many areas
• Much stronger Trainer rosters
• Higher Trainer levels
• Six-Pokémon boss teams
• Stronger AI for major Trainers
• Held items on important Trainer Pokémon
• Modified Pokémon stats
• Modified Pokémon types
• Modified abilities
• Rebuilt level-up learnsets
• New moves on certain Pokémon
• Buffed attacks
• Changed evolution methods
• Trade evolutions removed
• Lowered excessive evolution levels
• Reworked Poké Mart inventories
• Purchasable evolution items
• Purchasable Mega Stones
• Modified gift Pokémon
• Modified static encounters
• Battle Resort rematch-style Trainer battles

The result feels much more like a Drayano game than ordinary Omega Ruby.

Can You Catch All 721 Pokémon in Rising Ruby?

Yes.

Rising Ruby was explicitly built as a:

721 Pokémon hack.

Most basic-stage Pokémon become available relatively early, and Drayano says almost everything besides legendary Pokémon and Spiritomb can be captured before the seventh Badge. A large portion of the Pokédex becomes available before even the fourth Badge.

This makes Rising Ruby especially good for players who enjoy:

• Team variety
• Monotype runs
• Nuzlockes
• Building unusual teams
• Using Pokémon that normally appear too late

Does Rising Ruby Require Trading for Evolutions?

No.

Drayano changed evolution methods so that Pokémon do not need to be traded to evolve.

He also reduced several unusually high evolution levels—particularly for Pokémon whose original evolution levels were designed around later-game Generation 5 progression.

That makes completing the Pokédex much more practical in a single playthrough.

What Base Game Does Pokémon Rising Ruby Use?

Rising Ruby modifies:

Pokémon Omega Ruby

not Alpha Sapphire.

Rising Ruby

Base game:

Pokémon Omega Ruby

Sinking Sapphire

Base game:

Pokémon Alpha Sapphire

Do not apply Rising Ruby files to Alpha Sapphire.

We will cover Sinking Sapphire separately in article #11.

Which Omega Ruby Version Should I Use?

For the most reliable Rising Ruby installation:

use Omega Ruby v1.0.0 without the official game update active.

This matters much more than it does for most older ROM hacks.

Community troubleshooting around Rising Ruby found that installing later official Omega Ruby updates can override parts of the hack, particularly modified Poké Mart inventories. A direct Rising Ruby troubleshooting response recommends using Omega Ruby v1.0.0 rather than running the official update.

The original Project Pokémon discussion also notes that Rising Ruby players needed to remain on an earlier ORAS version for the hack rather than current retail-update behavior.

More recent 2026 discussion in the same official project thread confirms the same basic problem on Sinking Sapphire: removing the official ORAS update restored modded shop behavior.

For Rom Professor:

Rising Ruby = Omega Ruby v1.0.0 + Rising Ruby files

Do Not Install the Official Omega Ruby Update

If the game appears mostly modified but:

• Mega Stones are missing from shops
• Item inventories are vanilla
• Certain shop changes are missing

check whether the official Omega Ruby update is installed.

The official update can take precedence over modified game files.

On a real 3DS:

back up your save first, then remove the Omega Ruby update data—not the base game and not your save.

On an emulator:

do not install/enable the official Omega Ruby update while testing Rising Ruby.

Why Isn’t There a SHA-1 Like the GBA Install Guides?

3DS games are more complicated than Game Boy, GBA, or DS ROMs.

Omega Ruby can exist as:

• Physical cartridge dump
• Installed title
• .3ds
• .cci
• .cia
• Encrypted dump
• Decrypted dump
• Different regional releases

Those representations can produce different file hashes even when they represent a legitimate copy of the same game.

Rising Ruby also uses layered modified files rather than one binary patch that validates a single base-ROM checksum.

So I would not publish one universal Omega Ruby SHA-1 and pretend it applies to every Rising Ruby installation.

The important checks are:

• You own/dumped Pokémon Omega Ruby
• The game itself is clean
• You are using the correct region-specific mod files if the package distinguishes regions
• The official Omega Ruby update is disabled
• You are using Rising Ruby v2.1.0

Where Do You Get Pokémon Rising Ruby?

The canonical source for Rising Ruby information is Drayano’s official Project Pokémon thread.

Pokémon Rising Ruby and Sinking Sapphire official project thread

That thread verifies:

• Creator
• Version
• Completion status
• Features
• Documentation
• Installation approach
• Known issues

Why Doesn’t the Official Thread Have the Original Download Link Anymore?

Project Pokémon removed the old download link because the package contained ROM-derived files. The site’s administrator explicitly confirmed the link was removed for that reason.

Because of that:

Rom Professor should not mirror that archive or direct readers to random pre-patched .3ds/.cia downloads.

Use creator-authorized mod files from a legitimate patch/mod archive if available to you.

Avoid anything offering:

• “Rising Ruby ROM”
• Pre-patched .3ds
• Pre-patched .cia
• Full Omega Ruby download
• “No patching needed” packages

Rising Ruby Is a Mod, Not a Traditional Patch

This distinction is important.

Many of our installation guides look like:

Clean ROM + IPS/BPS/xDelta = finished ROM

Rising Ruby is different.

Its original distribution contains modified files such as:

• RomFS data
• ExeFS/code data
• CRO-related modifications

These are loaded over your legal copy of Omega Ruby.

This technique is commonly called:

LayeredFS

because modified files take precedence over the corresponding files inside the original game.

Modern Luma3DS and 3DS emulators support this general style of game modding. Luma3DS includes asset-path redirection/LayeredFS as one of its game-mod features.

How to Install Pokémon Rising Ruby on a Real Nintendo 3DS

The easiest modern hardware method is:

Luma3DS game patching / LayeredFS.

Drayano originally recommended Luma3DS for the best Rising Ruby experience.

Before You Start

You need:

• Your own Pokémon Omega Ruby
• A 3DS already set up with current Luma3DS
• Rising Ruby v2.1 files
• SD card access
• A save backup

If your 3DS does not already have modern custom firmware, use the maintained 3DS Hacks Guide rather than old 2016 A9LH/browserhax videos.

Current 3DS Hacks Guide

Current Luma3DS installations support LayeredFS/game patching and modern homebrew tools such as Checkpoint.

Step 1: Back Up Your Omega Ruby Save

Before changing anything:

use Checkpoint or another trusted 3DS save-backup tool.

Make a backup of your Omega Ruby save.

Do this before:

• Removing updates
• Installing mod files
• Changing your SD structure
• Testing Rising Ruby

Save backups are much easier than rebuilding a 40-hour Hoenn save.

Step 2: Remove the Official Omega Ruby Update

Rising Ruby works best against:

Omega Ruby v1.0.0

If your 3DS has the official Omega Ruby update installed:

remove the update data.

Do not delete:

• Pokémon Omega Ruby itself
• Your cartridge data
• Your save

You are removing the separate game update.

This prevents official update files from overriding Rising Ruby’s modified content.

Step 3: Enable Luma Game Patching

Power the 3DS completely off.

Hold:

SELECT

while turning the console on.

The Luma3DS configuration menu should appear.

Enable:

Enable game patching

Then press:

START

to save and reboot.

Current LayeredFS instructions use this same procedure.

Step 4: Prepare the Rising Ruby Files

Rising Ruby’s old v2.1 package was built before modern Luma drag-and-drop layouts became standardized.

That means some copies of the original folder structure are confusing.

The important content is your Rising Ruby:

• romfs folder
• executable/code replacement where required

Community troubleshooting found that the old package’s nested exe layout does not work correctly with modern Luma in some setups. A working fix uses the uncompressed Rising Ruby code file, renamed:

code.bin

and placed alongside the romfs directory rather than buried in the old /exe folder.

Your final title-mod folder should conceptually resemble:

/luma/titles/<Omega Ruby Title ID>/

containing:

romfs/

and, when required:

code.bin

Do not blindly copy files intended for Sinking Sapphire.

Step 5: Use the Correct Omega Ruby Title Folder

Luma applies game mods by title ID.

The structure is:

/luma/titles/<TitleID>/

Current LayeredFS documentation confirms that mod files belong under that title-specific directory.

Use the title ID matching your own Omega Ruby region.

If the Rising Ruby package already supplies a correctly named title folder:

use the folder corresponding to your game.

Do not copy a different region’s folder and assume it will work.

Step 6: Copy the Rising Ruby RomFS

Place Rising Ruby’s:

romfs

directory inside the Omega Ruby title folder.

Do not add unnecessary extra directory levels.

Incorrect:

/luma/titles/<ID>/Rising Ruby/romfs/

Correct:

/luma/titles/<ID>/romfs/

LayeredFS needs to see the modded files directly beneath the title folder.

Step 7: Add the Correct code.bin if Your Package Uses It

Some Rising Ruby changes require executable modifications.

If using the original v2.1 package:

the community-tested fix is to locate the uncompressed Rising Ruby code file under the Ruby-specific ExeFS files, copy it into the title-mod folder, and rename it:

code.bin

so it sits alongside:

romfs

rather than inside an obsolete exe subfolder.

This is particularly important if:

• The hack boots
• Wild encounters change
• Trainer teams change
• But Poké Marts or other code-driven features remain vanilla

Step 8: Reinsert the SD Card

Safely eject the SD card from your computer.

Put it back into the 3DS.

Power the system on normally.

Step 9: Launch Pokémon Omega Ruby

Launch your normal Omega Ruby icon.

You do not need a second HOME Menu icon labeled Rising Ruby when using LayeredFS.

Luma intercepts the game files and loads the Rising Ruby replacements.

Step 10: Verify the Hack

Do not assume a successful boot means every component loaded.

Check:

• Title/game presentation
• Early wild encounters
• Early Trainer rosters
• Modified Pokémon data
• Later Poké Mart inventories

If wild encounters change but shop inventories remain normal:

suspect either:

• Official Omega Ruby update still installed
• Incorrect code.bin
• Incorrect mod folder structure

How to Install Pokémon Rising Ruby on Windows

In 2026, I recommend:

Azahar

rather than old abandoned Citra builds.

Azahar is an open-source 3DS emulator built from the merger of Lime3DS and PabloMK7’s post-Citra fork, and its developers intend it to be the primary continuation of Citra-era 3DS emulation.

Official Azahar project

Step 1: Install Azahar

Azahar provides Windows builds through its official release system.

The project currently supports Windows 10 64-bit and newer systems meeting its hardware requirements.

Step 2: Add Your Legally Dumped Omega Ruby

Use your own dumped Pokémon Omega Ruby game.

Do not download a pre-patched Rising Ruby .3ds or .cia.

Get vanilla Omega Ruby running correctly in Azahar before adding the mod.

Step 3: Do Not Install the Omega Ruby Update

Run the base:

v1.0.0

game.

If you have already installed the official Omega Ruby update inside the emulator:

remove or disable it before troubleshooting Rising Ruby.

Otherwise, some modified data may be overridden.

Step 4: Open the Game’s Mod Location

Azahar inherits the Citra-style mod framework.

The easiest approach is to use the game list and open the game’s mod directory rather than manually hunting for title IDs.

The underlying structure is:

load/mods/<Title ID>/

and supports:

• romfs
• ExeFS replacements
• code.bin
• other LayeredFS-style files

The current archived Citra/Azahar mod documentation specifically supports drop-in compatibility with Luma3DS-style mods.

Step 5: Copy the Rising Ruby Files

Place the Rising Ruby:

romfs

folder into the Omega Ruby mod location.

If your Rising Ruby setup needs the executable replacement:

place:

code.bin

in the mod directory as supported by the Citra/Azahar mod structure.

Step 6: Launch Omega Ruby

Start Omega Ruby normally.

Azahar should layer the Rising Ruby modifications over the base game.

Step 7: Verify Multiple Types of Changes

Check more than the first wild encounter.

Verify:

• Wild Pokémon
• Trainer teams
• Pokémon stats/types
• Item shops

A partially working installation is possible if only the RomFS files load but executable changes do not.

Best Emulator for Rising Ruby on Windows

Use:

Azahar

for a new installation.

Old Rising Ruby guides frequently say:

Citra

because that was the primary 3DS emulator for years.

Citra was later taken down, and Azahar was created from two of the main successor projects.

For a 2026 article:

Azahar should be the default recommendation.

Best Emulator for Rising Ruby on Mac

Use:

Azahar

Azahar provides:

• Universal macOS builds
• Apple Silicon builds
• Intel builds

depending on the Mac you use.

The Rising Ruby mod-loading process is essentially the same:

1. Add your own Omega Ruby dump.
2. Open the game’s mod location.
3. Add romfs.
4. Add code.bin if required.
5. Run Omega Ruby v1.0.0.
6. Verify the mod.

Can I Play Pokémon Rising Ruby on Android?

Yes.

Azahar officially supports Android.

The project provides:

• Google Play build
• Vanilla build
• APK releases

For most players, the developers recommend the Google Play build for easier installation.

Android Setup

1. Install Azahar.
2. Add your legally dumped Omega Ruby game.
3. Confirm vanilla Omega Ruby boots.
4. Do not install the official ORAS update.
5. Place Rising Ruby’s LayeredFS files into the appropriate Omega Ruby mod directory.
6. Launch the game.
7. Test saving and mod functionality.

Mod-directory access on Android can vary depending on the current Azahar build and Android’s storage restrictions, so use Azahar’s own mod-location/user-directory tools where available rather than guessing an outdated folder path.

Can I Play Pokémon Rising Ruby on iPhone or iPad?

Yes, but the situation is less convenient.

Azahar itself does not plan official iOS support in the foreseeable future.

A current iOS alternative is:

Folium

which supports Nintendo 3DS emulation through its Cytrus core. The App Store currently lists Nintendo 3DS and New Nintendo 3DS among Folium’s supported systems.

However:

Rising Ruby requires mod-file loading, not merely running Omega Ruby.

That makes setup significantly less straightforward on iOS than:

• Windows
• Mac
• Android
• Real 3DS hardware

Community reports indicate LayeredFS-style mods can be placed within Folium’s file structure, but this is less consistently documented than Azahar’s mod support.

For Rom Professor:

Windows/Mac Azahar or real 3DS + Luma3DS is the recommended Rising Ruby setup.

iPhone should be treated as an advanced option.

Best Rising Ruby Platform

Platform	Recommendation
Real 3DS/2DS	Excellent — Luma3DS
Windows	Excellent — Azahar
macOS	Excellent — Azahar
Android	Good — Azahar
iPhone/iPad	Possible — Folium, more complicated
Old Citra	Legacy option; not recommended for new setup

Does Rising Ruby Need the Omega Ruby v1.4 Update?

No.

In fact:

the official Omega Ruby update can interfere with Rising Ruby.

Use base Omega Ruby v1.0.0 when possible.

This is particularly important for modified:

• Poké Marts
• Mega Stone availability
• Other data touched by official updates

Community troubleshooting has repeatedly traced missing Rising Ruby shop changes to installed official ORAS updates.

Why Are My Poké Marts Still Vanilla?

This is probably the most useful Rising Ruby-specific troubleshooting question.

If:

• Wild encounters are changed
• Trainer battles are changed
• But shops are vanilla

check two things.

1. Remove the Official Omega Ruby Update

Run:

Omega Ruby v1.0.0

The official update can override the modded shop data.

2. Check Your code.bin

The legacy Rising Ruby package has a folder-layout issue for modern Luma setups.

A community-tested solution is to use the Ruby-specific:

uncompressed code file

rename it:

code.bin

and place it alongside the romfs folder.

Should You Use the Exp. Share?

Drayano designed Rising Ruby around:

Exp. Share OFF

when using a normal six-Pokémon party.

The official project description specifically says the level curve assumes:

• Six Pokémon
• Exp. Share disabled

for the intended difficulty experience.

You can leave it on if you want an easier playthrough.

But if you want the game balanced as Drayano intended:

turn the Exp. Share off.

Are Gym Leaders Harder?

Yes.

Major Trainers receive:

• Stronger AI
• Better moves
• Higher IVs
• Useful abilities
• Held items
• Larger teams

Every Gym Leader and Elite Four member uses a full six-Pokémon team, and major Team Magma characters also receive full rosters in their important battles.

Does Rising Ruby Have New Story Content?

Not significantly.

This is one major difference between Rising Ruby and later ROM hacks.

Drayano explains that event/script editing was not practical for Generation 6 when the game was developed, so Rising Ruby focuses on the:

gameplay experience

rather than rewriting Omega Ruby’s story.

You still follow the normal Omega Ruby plot.

The major differences are:

• Pokémon
• Trainers
• Difficulty
• Items
• Evolutions
• Battles
• Encounters
• Postgame Trainer content

Does Rising Ruby Change Pokémon Types and Abilities?

Yes.

Some weaker Pokémon receive:

• Higher base stats
• New typings
• Different abilities
• Hidden abilities as standard possibilities

Examples documented by Drayano include:

• Bug/Water Masquerain
• Grass/Dragon Serperior
• Fighting/Flying Farfetch’d
• Gale Wings Chatot
• Pixilate Dunsparce

This is a Complete-style Drayano enhancement, not merely an encounter randomizer.

Does Rising Ruby Add Fairy-Type Changes?

Generation 6 already has Fairy type, but Rising Ruby uses it more aggressively.

Drayano gives additional Pokémon Fairy typing and adjusts some weaker Fairy moves to make them more useful.

Are Pokémon Movesets Changed?

Yes.

Almost every Pokémon has a modified level-up pool intended to make it easier to use during the main campaign.

Moves normally restricted to:

• TMs
• HMs
• Egg moves
• Previous generations

may appear naturally in level-up learnsets.

Some Pokémon receive entirely new move options as well.

Can I Buy Evolution Items?

Yes.

Rising Ruby modifies Poké Marts and Hoenn stalls so players can obtain evolution items more conveniently.

Examples include:

• Evolution stones
• Dragon Scales
• Reaper Cloths

Certain held trade-evolution items are usable directly from the Bag.

Can You Buy Mega Stones Before the Elite Four?

Many of them, yes.

Drayano made Mega Stones for Pokémon normally unavailable before the Pokémon League purchasable after earning:

• Six Badges
• Or eight Badges for certain stones

depending on the item.

If these Mega Stones never appear:

check whether the official Omega Ruby update is overriding Rising Ruby.

Does Rising Ruby Have Battle Resort Rematches?

Yes.

Battle Resort Trainers are used as a type of:

hologram battle system

allowing battles against teams based on characters such as:

• Hoenn Gym Leaders
• Blue
• Cynthia
• Kalos Gym Leaders
• Kalos Elite Four

This gives the postgame more difficult Trainer content than normal Omega Ruby.

Is Rising Ruby Good for Nuzlockes?

Yes.

Drayano explicitly designed the wild encounter distribution so that many areas contain roughly equal encounter rates for a large group of Pokémon.

That reduces the chance of repeatedly receiving the same common Pokémon and creates significant route-to-route team variety.

The downside:

major Trainers are dramatically stronger.

Rising Ruby is a good Nuzlocke game for experienced players, but it is not an easy first Nuzlocke.

How to Update Pokémon Rising Ruby Without Losing Your Save

Rising Ruby has not received a new official release since v2.1.0, so there is no active update cycle.

Still, you may be moving from:

• Old Rising Ruby v1
• Rising Ruby v2
• A broken v2.1 installation
• HANS → Luma
• Citra → Azahar
• Real 3DS → emulator

Use a cautious process.

Step 1: Make a Normal In-Game Save

Save normally through Pokémon Omega Ruby.

Do not rely only on an emulator save state.

Step 2: Back Up Your Save

On a real 3DS:

use Checkpoint.

On an emulator:

make a copy of the emulator’s normal game-save data.

Keep the original untouched.

Step 3: Back Up Your Current Mod Setup

Copy your existing:

• Rising Ruby mod folder
• Emulator mod directory
• Luma title folder

before changing it.

That allows you to restore the exact previous configuration.

Step 4: Install v2.1 Separately

Do not randomly merge old Rising Ruby v1/v2 files into v2.1.

Replace the mod files as a complete set.

Keep:

old mod folder

and:

new v2.1 mod folder

separate until the new configuration is tested.

Step 5: Keep Omega Ruby at v1.0.0

Do not install the official Omega Ruby update during migration.

That introduces another variable and can override mod data.

Step 6: Test a Copy of Your Save

I could not verify a blanket Drayano statement guaranteeing save compatibility across every historical Rising Ruby package and every modern LayeredFS conversion.

So:

test a backup.

Check:

• Party
• PC boxes
• Items
• Badges
• Pokédex
• Story progress
• Current location
• Mega Stones
• Modified Pokémon data

Step 7: Save Again

After confirming v2.1 works:

1. Save normally.
2. Exit the game completely.
3. Relaunch Rising Ruby.
4. Load the save.
5. Verify the mod is still active.

Do Not Use a Save State as Your Only Backup

Save states contain emulator-specific runtime information.

They are not a substitute for:

• Checkpoint save backup
• Normal 3DS game save
• Emulator battery/system save

Use the game’s real save data.

Common Pokémon Rising Ruby Installation Problems

“The Game Looks Like Vanilla Omega Ruby”

Check:

• Luma game patching enabled
• Correct Omega Ruby title directory
• romfs location
• Azahar mod location
• Correct game region
• Whether you accidentally launched a different Omega Ruby copy

“Wild Encounters Changed, but Shops Didn’t”

This is a classic Rising Ruby problem.

First:

remove/disable the official Omega Ruby update.

Second:

check your executable/code file.

The legacy package may require the uncompressed Ruby-specific code file renamed:

code.bin

beside your romfs.

“Mega Stones Aren’t in Poké Marts”

Same likely cause:

official Omega Ruby update is overriding Rising Ruby data.

Use:

Omega Ruby v1.0.0.

“Rising Ruby Crashes on Launch With Luma”

Check your folder structure.

The old package was created before current Luma LayeredFS conventions.

Make sure:

romfs

is directly below the title folder and that any required:

code.bin

is in the correct location.

“My Old Package Has an /exe Folder”

Modern Luma does not simply use that legacy folder as-is.

The known Rising Ruby fix is to use the correct uncompressed Ruby code file and put the renamed:

code.bin

alongside:

romfs.

“Can I Just Download a Pre-Patched .3ds?”

Rom Professor does not recommend or link to pre-patched copyrighted games.

Use your own legally dumped Omega Ruby and LayeredFS-style mod files.

“Can I Rename a Mod Folder to .3ds?”

No.

Rising Ruby’s RomFS/ExeFS files are not a complete game image.

They are replacement files loaded over Omega Ruby.

“Azahar Boots Omega Ruby but the Mod Doesn’t Load”

Right-click/open the game’s mod location and verify:

• romfs is in the title’s mod directory
• code.bin is in the supported location if required
• No unnecessary extra directory layer exists
• You are launching the same Omega Ruby entry whose mod folder you edited

Azahar/Citra-style mod loading expects the game-specific mod directory structure.

“Should I Install the Omega Ruby Update in Azahar?”

No, not for Rising Ruby.

Run the base v1.0.0 game unless you have specific updated Rising Ruby files designed around a later official update.

“Why Can’t I Use Online Features?”

Rising Ruby was designed around an older Omega Ruby game version and also changes Pokémon data in ways that are not standard to retail ORAS.

The old project discussion already noted that remaining on the required earlier game version limited normal online functionality.

Treat Rising Ruby as primarily:

single-player.

“Does the DexNav Show Every Pokémon Correctly?”

Not always.

Drayano lists a known limitation where some Pokémon can appear at the very edge of the DexNav because each area contains more species than the interface was designed to display.

This does not mean your ROM is broken.

“Can I Use My Vanilla Omega Ruby Save?”

Possibly, because you are still launching Omega Ruby underneath the mod—but I could not verify an official blanket compatibility promise from Drayano.

Because Rising Ruby changes:

• Pokémon data
• Encounters
• Gifts
• Items
• Shops

I recommend:

backup first and preferably start a new Rising Ruby playthrough.

If you reuse a save:

test a copy.

“Can I Switch Back to Vanilla Omega Ruby?”

With LayeredFS:

yes, generally by disabling/removing the mod files.

But backup your save first.

A Pokémon caught or modified under Rising Ruby may use stats, moves, typings, or abilities that behave differently when the mod is disabled.

Do not casually move an important Rising Ruby save back and forth between modded and unmodded Omega Ruby.

How to Verify Pokémon Rising Ruby Installed Correctly

Check the Version

You want:

Rising Ruby v2.1.0.

Check the Base

You should be launching:

Pokémon Omega Ruby

without the official update overriding the mod.

Check Early Wild Encounters

Rising Ruby completely rebuilds encounter tables.

Most areas contain much broader Pokémon variety than vanilla Omega Ruby.

Check Trainer Teams

Trainer rosters should differ substantially.

Important Trainers eventually use full six-Pokémon parties with better:

• Moves
• IVs
• Abilities
• Items
• AI

Check Pokémon Data

Look for documented type/stat/ability changes.

Check Poké Marts

This is an excellent test for whether the executable/update side of the mod is working.

If encounters are modified but shop inventories remain vanilla:

troubleshoot:

• Omega Ruby update
• code.bin

Test Saving

1. Make a normal in-game save.
2. Close the game completely.
3. Relaunch Rising Ruby.
4. Confirm your save appears.
5. Load it.
6. Confirm the mod is still active.

If all of those checks pass:

your Rising Ruby setup is ready.

Pokémon Rising Ruby Installation FAQ

What is the latest version of Pokémon Rising Ruby?

v2.1.0, released October 16, 2016.

Who created Pokémon Rising Ruby?

Drayano.

Is Rising Ruby complete?

Yes.

Drayano identifies it as a completed 721-Pokémon hack.

What base game does Rising Ruby use?

Pokémon Omega Ruby.

Does Sinking Sapphire use the same base?

No.

Sinking Sapphire uses Pokémon Alpha Sapphire.

Is Rising Ruby an IPS patch?

No.

It uses modified 3DS game files such as RomFS/ExeFS-style replacements rather than one traditional IPS/BPS patch.

What version of Omega Ruby should I use?

v1.0.0 is the safest recommended base.

Official Omega Ruby updates can override certain Rising Ruby changes.

Should I install the Omega Ruby v1.4 update?

No, not for a normal Rising Ruby installation.

If modified shops or Mega Stones are missing:

remove the update and test again.

Where is the official Rising Ruby page?

Drayano’s Rising Ruby / Sinking Sapphire project thread

Why is the original download link missing?

Project Pokémon removed it because the old package contained ROM-derived files.

Can Rom Professor link a pre-patched Rising Ruby ROM?

No.

Use your own legal Omega Ruby copy/dump and legitimate mod files.

What is the best way to play Rising Ruby on a real 3DS?

Luma3DS LayeredFS/game patching.

Drayano recommended Luma3DS, and current Luma still supports game-file redirection.

What emulator should I use on Windows?

Azahar.

Azahar is the modern open-source continuation of Citra-era 3DS emulation.

What emulator should I use on Mac?

Azahar.

It has current Intel, Apple Silicon, and universal macOS builds.

Can I play Rising Ruby on Android?

Yes.

Azahar officially supports Android.

Can I play Rising Ruby on iPhone?

Possibly.

Folium currently supports Nintendo 3DS emulation, but LayeredFS ROM-hack setup is less straightforward than on Azahar or a real 3DS.

Does Azahar support Rising Ruby-style mods?

Azahar inherits the Citra-style game mod framework, including LayeredFS-style romfs and executable replacements.

Can I catch all 721 Pokémon?

Yes.

Do trade evolutions require trading?

No.

Drayano changed evolution methods so Pokémon can evolve without actual trading.

Are Gym Leaders harder?

Yes.

Major bosses use stronger AI, better moves and items, and full six-Pokémon teams.

Should I turn Exp. Share off?

For the intended difficulty:

yes.

Drayano balanced the game around six Pokémon with Exp. Share disabled.

Does Rising Ruby have a different story?

Mostly no.

The project focuses on enhanced gameplay because Generation 6 event editing was limited when it was developed.

Does Rising Ruby change Pokémon stats and types?

Yes.

Many weaker Pokémon receive buffs, and several species receive new typings and abilities.

Can I buy Mega Stones earlier?

Many Mega Stones become purchasable after six or eight Badges.

Why aren’t Mega Stones appearing?

Check whether the official Omega Ruby update is installed and whether your Rising Ruby code.bin is loading correctly.

Can I use an existing Omega Ruby save?

Maybe, but I recommend a backup and a new Rising Ruby save.

No blanket official save-compatibility guarantee was verified.

How do I update Rising Ruby?

v2.1.0 is currently the final official release.

If reinstalling:

replace the mod files cleanly rather than mixing old and new folders, and backup the save first.

Where should I go after installing Pokémon Rising Ruby?

Once the game is running correctly, read our Pokémon Rising Ruby beginner guide.

Rising Ruby changes enough gameplay data that ordinary Omega Ruby guides stop being reliable for many questions.

Useful supporting guides should eventually include:

• Pokémon Rising Ruby Gym Leader teams
• Rising Ruby Pokémon locations
• Rising Ruby evolution changes
• Rising Ruby Pokémon stat/type changes
• Rising Ruby Mega Stone locations
• Rising Ruby Elite Four guide
• Rising Ruby Battle Resort guide
• Rising Ruby Nuzlocke guide
• Rising Ruby vs. Sinking Sapphire
• Rising Ruby latest version guide

The official Project Pokémon thread is also useful for confirming the hack’s original feature set and v2.1.0 status.

Suggested article screenshots: Use a Rising Ruby title/gameplay screenshot, a Luma3DS “Enable game patching” screenshot, an SD-card folder screenshot showing romfs and code.bin in the correct game-mod folder, and an Azahar screenshot showing the Omega Ruby mod location. A particularly useful troubleshooting image would compare a modified Rising Ruby Poké Mart against vanilla Omega Ruby, since missing shop changes are one of the easiest ways to spot an incorrect v1.4-update or code.bin setup.