Android - Revision history

Bssarkar: /* The Settings menu (Splash screen) */ add how to access menu

2026-08-16T06:42:56Z

‎The Settings menu (Splash screen): add how to access menu

Bssarkar: /* The Settings menu (Splash screen) */ Add content for splash screen menus

2026-08-16T06:39:26Z

‎The Settings menu (Splash screen): Add content for splash screen menus

Bssarkar: /* Playing controls */ mention reachmap not vanishing

2026-04-04T03:12:34Z

‎Playing controls: mention reachmap not vanishing

Bssarkar: /* Dev Notes */ add info about manifest.txt and status.properties files. syntax info will be added later.

2026-02-13T09:11:17Z

‎Dev Notes: add info about manifest.txt and status.properties files. syntax info will be added later.

Bssarkar: /* Dev Notes */ Promote section header levels

2026-02-13T08:55:01Z

‎Dev Notes: Promote section header levels

Bssarkar: /* Playing controls */ Long press menu info

2025-10-11T12:05:17Z

‎Playing controls: Long press menu info

AI: /* MMMPPpxxVA */

2025-10-03T05:09:34Z

‎MMMPPpxxVA

Soliton: /* Other version code scheme drafts */

2025-10-02T11:04:15Z

‎Other version code scheme drafts

AI: /* Other version code scheme drafts */

2025-10-02T10:17:46Z

‎Other version code scheme drafts

AI: /* Other version code scheme drafts */

2025-10-02T09:21:50Z

‎Other version code scheme drafts

@@ Line 10: / Line 10: @@
 == The Settings menu (Splash screen) ==
 [[File:Settings-menu-android.png|thumb|Android Settings Menu]]
 * '''Clear Gamedata''': Delete all game data but preserve userdata, like addons, saves, logs etc. Next time you start, the game will prompt for data download unless the data is manually installed via the '''Install Gamedata ZIP''' option.

← Older revision		Revision as of 06:39, 16 August 2026
Line 9:		Line 9:

	== The Settings menu (Splash screen) ==		== The Settings menu (Splash screen) ==
		+	[[File:Settings-menu-android.png\|thumb\|Android Settings Menu]]
		+
		+	* '''Clear Gamedata''': Delete all game data but preserve userdata, like addons, saves, logs etc. Next time you start, the game will prompt for data download unless the data is manually installed via the '''Install Gamedata ZIP''' option.
		+
		+	* '''Install Gamedata ZIP''': Manually install gamedata for Wesnoth to use. This can be used to test modifications or copy over data from a PC installation if you don't want to download. the user must be careful about exercising this option because it can cause version mismatch issues, which in turn may cause Wesnoth to partly or wholly fail. Automatic download are also suppressed unless you clear the manually installed gamedata first via '''Clear Gamedata'''.
		+
		+	* '''Import/Export Userdata''': A workaround for modders so that they can modify the data of wesnoth, as well as allow player to access/modify savefiles/logs/preferences etc. Due to Android SAF restrictions, accessing the internal data of an app is very difficult in Android 11+, which may create difficulties for UMC work. The workflow on Android is: ''Export Userdata -> modify/update -> Import'' instead of directly editing those files. Import '''overwrites''' internal data.

	== Logs and debugging steps ==		== Logs and debugging steps ==

@@ Line 2: / Line 2: @@
 == Playing controls ==
-* Tap a unit to select/deselect it.
+* Tap a unit to select/deselect it. (After deselection, the reachmap won't vanish, but it was deselected, so if you touch another unit the reachmap will change.)
 * Tap a unit, then tap the target hex to show defense stats of that unit and footsteps. (Similar to hover on PC)
 * Tap a unit, then double tap on the target hex to move it. Alternative, you can drag along the path to choose the exact path which the unit is supposed to move by.

@@ Line 26: / Line 26: @@
 == Dev Notes ==
 === Version Code scheme (1191601001 - post 1.19.16 fixup) ===
 <code>MmmPPppVVV</code>

@@ Line 25: / Line 25: @@
 Go to System > Developer Options and turn off  the '''Use developer options''' toggle.
-=== Dev Notes ===
+== Dev Notes ==
-==== Version Code scheme (1191601001 - post 1.19.16 fixup) ====
+=== Version Code scheme (1191601001 - post 1.19.16 fixup) ===
 <code>MmmPPppVVV</code>
@@ Line 38: / Line 38: @@
 ** Rest unused (variants if we need them)
-==== New Version Code scheme draft ====
+=== New Version Code scheme draft ===
 This is but one possible idea among many, and is not final.
@@ Line 59: / Line 59: @@
 E.g., 1.20.14 with hotfix 1, Fdroid, arm64 ABI would be: <code>120020140102</code>.
-==== Other version code scheme drafts ====
+=== Other version code scheme drafts ===
 Given that we only have 10 digits to work with (max being 2.1e9, which is signed INT_MAX with some margin), the above scheme is not possible. The PR to remove/disable the existing version codes on f-droid has been rejected, so we're probably stuck with version codes > 1.19e9.
@@ Line 73: / Line 73: @@
 Drafts of possible approaches:
-===== <code>MMMPPpxxVA</code> =====
+==== <code>MMMPPpxxVA</code> ====
 * MMM - Combined Major/Minor: 1.19 = 119, but each subsequent minor *or* major bump increases this number by 1. This remains visually the same until 2.0 happens.
 * PP - Patch version
@@ Line 83: / Line 83: @@
 Example: <code>1220320002</code> would be version 1.22 (or 2.0 or 2.2, but 2 stables from 1.18), patch 3, android patch 2, default (clean) variant, arm64
-===== <code>12MMMPPpVA</code> =====
+==== <code>12MMMPPpVA</code> ====
 Basically the same thing, just shifted to the right by eating up the unspecified digits, and with the first digits fixed to 12. Leaves 8 "additional epochs" available for future expansion.
 Example: <code>1212203202</code> would be version 1.22.3.2 clean arm64, as above.
-===== <code>12MMPPpxVA</code> =====
+==== <code>12MMPPpxVA</code> ====
 Removes the major version digit, freeing up 1 digit. Not functionally different from the major-minor scheme, but reduces the number of available version bumps until epoch change.
 Example: <code>1222032002</code> would be version 1.22.3.2 clean arm64, as above.

@@ Line 78: / Line 78: @@
 * V - Build variant (0 is clean, 1 might be google play integrations. Could be a bitfield or an enum)
 * A - ABI (as above)
-* x - Unspecified, available for expanding these fields or adding other flags (like store and/or integrations)
+* x - Unspecified, available for expanding these fields or adding other flags
 Example: <code>1220320002</code> would be version 1.22 (or 2.0 or 2.2, but 2 stables from 1.18), patch 3, android patch 2, default (clean) variant, arm64

@@ Line 67: / Line 67: @@
 * each ABI needs its own version code
 * we may have multiple APK releases for one "regular wesnoth version" to fix android-only issues (android patch version)
-* we may have builds that differ per store (F-droid creates the file /data/Dist with contents "F-Droid" during the build process)
+* we may have builds that differ per store (F-droid creates the file /data/dist with contents "F-Droid" during the build process)
 * we may want various variants of builds, that is, a "clean" build, a build with google play integrations, a build with a different integration, and so on. This may or may not be tied to the store the APK is distributed on