The answer before the background

Our recommendation

Use this Shogun's Empire Hex Commander wiki as a source directory, not an undocumented list of exact values. The current client owns live unit stats, province output, campaign rules and prices. Apple history owns mobile version changes; Google Play owns Android package and offline status; Steam owns desktop requirements, license and HNG Cloud facts; Home Net Games owns product identity. Steam discussions and other community posts are useful for strategy hypotheses only when they retain platform, version, clan, mode and evidence.

Match each fact to the authority that can verify it

QuestionBest sourceRequired context
Current unit valueLive clientPlatform, version, mode and experience.
Mobile patch changeApple version historyVersion number and date.
Android identityGoogle PlayPackage com.HomeNetGames.Shogun.
PC requirementsSteam app 1093760Operating-system tab and current store status.
Cloud behaviorSteam and Home Net Games supportSteam Cloud versus optional HNG account.
Strategy ideaSteam discussions or community postClan, map, difficulty, army and reproducible turns.

Store strategic and tactical objects separately

  • Clan row: starting provinces, campaign, difficulty, special access and reviewed version.
  • Province row: Gold, Rice, buildings, unit unlocks, borders and reinforcement distance.
  • Unit row: role, weapon, range, movement, experience and reliable counters.
  • General row: morale, army-size and combat bonuses plus the formation tested.
  • Battle row: map, terrain, objective, armies, turn sequence and result.
  • Source row: exact URL or screenshot, platform, language, version and verification date.

Preserve a changed rule instead of deleting the conflict

Apple history records material older changes: version 1.6 added three archer generals and adjusted difficulty; 1.5 changed AI war conditions, rebellion and Rice costs; 1.4 changed starting Honor and Gold, declarations and plunder; version 2.0 added an FPS option; 2.0.4 delivered a Unity security update; 2.1 updated SDKs.

A guide written under 1.4 can therefore disagree with 2.1 without either author fabricating data. Mark the older row historical, attach the old version and create a new current row only after verifying the client.

Turn a forum answer into a repeatable test

Steam discussions can reveal tactics or migration problems, but the reply must retain edition, clan, mode, difficulty, unit experience and battle map. Reproduce the sequence in the official client before stating that it is generally valid.

Do not treat a download attachment, trainer, cloud file or purchase workaround as wiki evidence. Link official product pages for access; keep community material focused on questions, screenshots and controlled play observations.

Common questions

Is there an official Shogun's Empire wiki?

No single publisher-maintained public wiki was established during this review; use the current client and official store records as the factual base.

Where should unit stats come from?

Read them in the current client and record platform, version, mode, experience and language.

Are Steam discussions reliable?

They are useful community leads when the exact conditions and evidence are preserved and reproduced.

How should old patch facts be handled?

Keep them as dated historical rows and do not silently present them as current mobile 2.1 or current Steam values.

What we checked

Official listings establish current availability and product facts. Community pages are used for mechanics and build history, then labeled separately.