Account guide

My RV import guide

Import guide · Updated 31 October 2026

By Wintira · Aniiland creator and guide writer

I make Aniiland, keep the planner data in line with the game, and write these guides from in-game testing, screenshots, data checks and all the little planner edge cases that show up once people actually use the tool.

Importing your RV data is the fastest way to stop building plans from memory and start building them from your real account.

Storage unit — Import matters because Homeland planning gets more reliable once the tool knows your real buildings, modules and storage instead of guessed values.

What the import is for

The My RV import pulls together the account-side details that change a plan: your RV level, facilities, modules and related Homeland data. Once that information is in, the planner can stop acting like your setup is generic and start acting like it is yours.

How to use it well

Import your latest data.
Check whether the detected RV level and buildings look right.
Open the planner with that imported setup.
If needed, fine-tune your current goal and worker mode.

Sandcastle — Imported facilities help the site understand what you can actually produce.

Egg incubator — Module and facility context matters, even when the visible change seems small.

Storage information helps keep upgrade and material planning honest.

What to do after importing

The most useful follow-up is to compare what you thought your bottleneck was with what the planner says your bottleneck is. That is where imports usually pay off. People often remember their broad progress correctly but forget the exact facility balance or storage side.

What the lookup can and cannot tell you

The import feature is there to reduce manual entry, not to turn a game account into a perfect live simulation. Depending on which profile data is available, it can help populate RV information, facility levels and counts, modules and selected Homeland details. Some fields may not be available through every lookup path. The result should therefore be treated as a starting snapshot rather than a guarantee that every item in storage is fully up to date.

Always check the timestamp or freshness of the information when the interface provides it. A profile imported yesterday might still be valid, but it should not overrule a building you upgraded in game five minutes ago. When important values differ, use the game's current state as the source of truth and update Custom Setup accordingly.

Account lookup versus simple lookup

The site has different lookup paths. Some are designed for basic player information, while account-linked features can provide a fuller saved profile experience. That distinction matters when the same UUID seems to reveal different amounts of information in different places. A limited result is not necessarily a broken result; the lookup may simply not have access to all fields.

If you sign in to save profiles, keep in mind that syncing is a separate feature from performing a calculation. The calculator can still be used without a sign-in. The account feature is useful when you want your saved setup and profile information to follow you between devices.

Check the imported setup before calculating

Make sure the displayed RV level is the one you currently have.
Confirm the count and levels of important facilities such as Farmland, Woodland, Mine and Generator.
Review your RV modules and any optional upgrades that affect production.
Check the goal, worker mode and event settings separately; they may reflect your previous choices.
Run the planner and read any warning about an incomplete setup before trusting the output.

That check is especially important if the importer picked up a partial profile. Missing a single generator or important production building can make a plan look impossible, while an extra building you do not own can make the result look too optimistic.

When an import goes wrong

Start by reporting the specific field rather than simply saying the import failed. Include the RV level shown, the facility or module that is wrong, the value visible in game, and which lookup path you used. A screenshot of the mismatch is much more useful than a generic error message. Do not share a password or session token in a bug report.

It is worth keeping an exported setup as a backup when changing devices or testing major updates. You can also compare a fresh import with your saved profile to work out whether the issue is stale data, a lookup limitation or a field mapping that changed after a game patch.

Written by Wintira.

This page is meant to make the import feel less mysterious and more like the practical shortcut it is.

Want to use your live setup? Open the planner and start from your imported RV data.

Open the planner