Updates and hotfixes

Original release

The podium, battle-point tabs and results tables share the centre of the available content area beside the category sidebar. Podiums remain on page one only across all ranking categories.

Players and Tribes now have an As Supporter battle-point tab, with ordinary pagination and its own first-page podium. Scores are recorded by both battle-processing paths when stationed troops defend another player's village.

Enemy casualties are measured in farm population, consistent with existing lifetime battle points. Each external troop owner's share is proportional to the stationed population before casualties, combining multiple origins belonging to the same owner. The defender keeps the remainder. Own troops defending another owned village and the attacker's stationed troops are excluded from supporter credit, as are self attacks and battles without enemy losses. Rounding remains with the defender, so defender and support shares do not count the same enemy casualty twice.

Supporter shares update the player, the tribe they belong to at battle time, total battle points and daily Support scores. A battle/player ledger prevents the supporter share being awarded again if the credit routine is replayed. Existing serialized battle processing and its broader retry behavior remain unchanged.

New worlds include the supporter columns. Existing worlds gain them and the credit ledger automatically. Historical battle-point totals are preserved; the new lifetime supporter subtotal starts at zero and records new battles after upgrading. Past support contributions cannot be reconstructed reliably from the stored reports and are not invented or backfilled.

Updates and hotfixes

Original release

Mass message now lists world checkboxes with Select all. The current world is selected initially. Messages go to all registered players in each selected world; an account with registrations in multiple selected worlds receives a message in each corresponding inbox. Archived worlds cannot receive new broadcasts. Registry IDs, staff permissions and the existing form token protect the action. The result shows recipient counts by world.

Rally Point has a Troop Templates submenu. Players can save up to 20 named templates per world, edit or delete them, and choose a fixed quantity or All per unit. The unit columns follow world settings, including Paladin and archer availability. Templates are private to the owning player and world and can be applied in the Rally Point or map window.

Map troop presets and available quantities are brown hyperlinks. Noble adds exactly one noble to the current selection, up to availability. Attack and Support lead to an editable confirmation window before dispatch. Add additional commands, change each composition independently, select templates, remove rows and review the aggregate total against village availability. Travel, arrival and carrying capacity are calculated by the server for every row; morale follows the world rules. Catapult targets appear when catapults are selected for an attack.

Four beben rows containing 100 axes and 25 light cavalry produce four separate movements, using 400 axes and 100 light cavalry in total. The final server action validates enabled units and aggregate availability, reserves the total with one guarded update, and creates one movement and scheduler event per row. The existing repeated-command Rally Point flow remains compatible.

Updates and hotfixes

Original release

This release adds a public report link with selectable disclosure fields and revocation. Copy the URL or insert it as [report_display]URL[/report_display] in a message or profile.

The communication editor now offers BBCode controls for font size, color, table, coordinates, unit and building icons, and named emoji such as :pensive:. The same formatter handles player profiles, tribe descriptions and announcements, and mail. The public report view is available without a login only while its owner keeps the share active.

Deploy using README.md. Back up the database first. The public_reports table is created automatically.

Updates and hotfixes

Original release

Based on V1.9.6.13.

Relics appear in a world-specific Treasury, opened with a custom telescope icon immediately to the right of Flags. The eighteen relic types have original vector artwork.

No starter relics. Barbarian village takeovers yield a relic; other conquests have a 35% discovery chance. Successful resource raids and village defenses each have a 3% discovery chance. The movement ID prevents duplicate awards on retry.

Five qualities: Shoddy, Basic, Enhanced, Superior, Renowned. Main stats give 2/4/6/8/10%; two distinct secondary stats give 1/2/3/4/5%. A stat's combined relic bonus is capped at 10%.

Up to ten owned villages can equip one relic each. Range is 1/1/2/2/3 map tiles, depending on quality. Placement locks the relic for 24 hours. Conquering an equipped village transfers its relic to the conqueror's Treasury.

Merge three unassigned relics of the same quality. Three of the same type retain their type and secondary stats; mixed types roll a new type and secondary stats. The first discovery or merger of a Superior or Renowned type on a world names that quality/type after its discoverer.

Resource production, barracks/stable/workshop recruitment, haul, applicable unit combat, and scouting bonuses are wired into gameplay. Longbow and Shortbow do not drop when archers are disabled.

World Settings has Enable relics below Flags with Locked after players join. Existing Alpha/Beta worlds (IDs 1-4) default to Yes; other worlds and newly created worlds default to No. The setting cannot change after players join.

Updates and hotfixes

Original release

Fixed unowned/barbarian villages remaining at their starting size even when growth was enabled.

The scheduler worker is intentionally recycled after roughly 59 seconds, but maintenance previously required 60 uninterrupted seconds. Its timestamp was reset on every restart, so the growth task never ran.

Maintenance is now due immediately after every world worker starts.

Further maintenance passes honor each world's configured growth interval up to the normal 60-second cadence. A 0.5-minute interval runs approximately every 30 seconds.

The fix applies independently to every active world, including World 4 (Beta 2).

No database migration or setting change is required.

Existing barbarian villages retain their buildings, resources and last-growth timestamps. Overdue eligible villages resume normal one-level-at-a-time growth after deployment.

Player-owned villages remain excluded, and the configured point ceiling and building prerequisites remain enforced.

Updates and hotfixes

Original release

This release makes major gameplay systems selectable per world before players join.

Scavenging: when disabled, Scavenging and Mass Scavenging disappear from the Rally Point and scheduler processing is skipped.

Paladin: may be disabled or capped at exactly one or ten Paladins. Disabled worlds expose neither the Statue nor Paladin unit/screens. Single-Paladin worlds enforce one slot and use the compact resident-oriented interface.

Flags: when disabled, the header control is hidden and rewards, assignment, and bonuses are inactive.

Inventory: when disabled, the header control is hidden and item usage, staff grants, and active effects are rejected or ignored.

Church: remains world-specific and joins the highlighted game-changing section.

These settings are enforced server-side and cannot change once a player has joined the world. Existing worlds default to enabled with a ten-Paladin limit.

Game-changing settings use darker rows and display “Locked after players join.”

Farm System now uses named Classic and Modern choices. Classic is the S1 curve with 22,782 level-30 capacity; Modern is the current 24,000 curve.

The map command modal uses a centered white X on brown, while troop counts and preset labels use high-contrast brown text.

Attack and Support button styling is unchanged.

The Docker build includes regression checks for feature defaults, server-side gates, Paladin limits, Farm curves, and command-window styling.

Updates and hotfixes

Original release

Redesigned the lower village header around switching, village identity, resources, Flags, and Inventory.

Moved Map into the primary menu between Overview and Reports.

Replaced Permission with a clear Loyalty meter.

Added keyboard-accessible hover descriptions to active Item Bonuses.

Good Connections now grants +25% Warehouse capacity and +25% merchant capacity.

Applied merchant capacity consistently to Market screens, overviews, and Account Manager deliveries.

Resource amounts are black normally, brown from 90% capacity, and red at full capacity, without bold text.

This is an in-place upgrade from V1.9.3.2; no manual database migration is required.

Updates and hotfixes

Original release

Due commands are now fetched through a composite (event_time, id) index in ordered batches of 500.

A busy world keeps draining further batches during the same scheduler tick instead of waiting for the next pass.

Attacks, support, returns, recruitment, construction, research, merchants and Paladin deployment take priority over background work.

Full-world lifecycle, village-growth, Paladin-item, premium and ranking maintenance no longer runs inside every one-second command pass.

Attack resolution no longer performs four full global ranking rebuilds for every processed movement.

Account Manager and scavenging idle capacity is raised from 250 to 500, but these processors yield whenever the command queue is backlogged.

The scheduler keeps its database connection for the worker lifetime instead of reconnecting every second.

Updates and hotfixes

Original release

Item Bonus panel below Flag Bonus on both village overview modes.

Permanent labels and live countdowns for active Inventory effects; the overview refreshes when a timed effect expires.

Miscellaneous global profile achievements for account age and world victories.

Compact, quality-bordered achievements from every other world on public profiles, including hover names and sorting.

Compact rounded Inventory chest shortcut matching the Flags shortcut.

Village name and coordinates align vertically with the Map header.

Village overview production figures now include active Inventory production effects.

No manual SQL migration is required.

Updates and hotfixes

Original release

Chest shortcut beside Flags with original SVG artwork.

Responsive Inventory screen with category filtering, search, count badges, details, use confirmation and active-effect status.

World-local inventory, effect and append-only grant/use log tables.

Recruitment, percentage resource package, unit and village item catalogue.

Timed, permanent and instant item handling, including safe one-village relocation.

Inventory modifiers integrated with resource production, recruitment and core combat calculations.

Secure World Moderation grant form with quantity validation and audit logging.

Docker-build inventory regression and Smarty compilation coverage.

No manual SQL migration is required. Back up the live database before upgrading.

Updates and hotfixes

Original release

Flags are accessible immediately to the right of the resource and farm indicators. The screen displays an eight-type, nine-level inventory grid, the current village's flag, a village assignment overview and the latest 20 rewards. Flag artwork is supplied as local SVG assets.

Each newly attained achievement stage and each completed Nobleman produces one random flag. Types have equal 1-in-8 odds and levels have equal 1-in-9 odds, independently. Existing completed achievements and previously produced Noblemen are not backfilled. An achievement stage cannot reward the same player twice if their rank drops and recovers. Nobleman batch completions award individually, with retry keys preventing duplicate rewards.

Flags are scoped to the player and world. One flag can benefit only one village at a time, and each village can use only one flag. Assignments lock for 24 hours. Afterward, remove a flag to return it to the available inventory and assign it elsewhere. Replacing a flag returns the previous one to inventory. Losing a village returns its flag to the original player's inventory. No player trading, cross-world transfers, flag combining or world enable/disable setting is included.

Values are percentages for levels 1 through 9, except luck, which uses percentage points.

| Type | Values | Effect | | --- | --- | --- | | Resource production | 4, 6, 8, 10, 12, 14, 16, 17, 18 | Increases all three resources; settles accrued resources before changing flags. | | Recruitment speed | 6, 8, 10, 12, 14, 16, 18, 19, 20 | New recruitment times are divided by 1 + bonus/100. Existing queues retain their times. | | Attack strength | 2, 3, 4, 5, 6, 7, 8, 9, 10 | Improves attacks from the assigned village. | | Defense strength | 2, 3, 4, 5, 6, 7, 8, 9, 10 | Improves troops defending the assigned village, including support. | | Offensive luck | 6, 8, 10, 12, 14, 16, 18, 19, 20 | Moves each attack's luck roll toward zero by this many points. | | Population | 2, 3, 4, 5, 6, 7, 8, 9, 10 | Increases farm capacity, including bonus villages. | | Coin costs | 10, 12, 14, 16, 18, 20, 22, 23, 24 | Discounts gold coin resource costs, rounded up. | | Haul capacity | 2, 3, 4, 5, 6, 7, 8, 9, 10 | Increases surviving attackers' carrying capacity. |

Combat and haul bonuses use the village flag at battle resolution. Population flags cannot be removed or downgraded if the village would exceed its resulting farm capacity. The Troop Manager retains its existing 24,000 population target cap.

Reference: https://help.tribalwars.net/wiki/Flags . Reward sources, random levels and world isolation follow the custom rules for this clone.

The application creates tw_flags automatically in each world database. No manual SQL is required. A unique player/source key protects reward retries; a unique assigned-village key prevents two active flags in a village. Assignment actions use POST, session-token verification, player ownership checks and the existing world action lock. Sitters cannot change flags. Archived-world action restrictions remain in place.

The achievement refresh also now handles unchanged stages without emitting an invalid UPDATE statement.

Original release

When a world reaches its configured victory condition, V1.8.0 records one durable victory for every winning player:

For a tribe victory, every player who belonged to the winning tribe in the final world snapshot receives one victory.

For a player victory, each declared winning player receives one victory.

Tied winners continue to be supported.

Each archived-world/player pair is unique, preventing duplicate awards if finalization is retried.

The homepage Victories total combines any existing legacy users.wins value with archived-world awards.

On startup, existing final snapshots are safely backfilled. This makes the already-archived Alpha 2 victory appear for all POLAND members without reopening or re-finalizing the world. Older tribe snapshots are matched using the archived tribe name; new snapshots also retain the tribe ID.

Archived worlds now use the same red artwork family as Logout while retaining the World archived caption.

Close keeps its brown Select World-style appearance and now forces white text in normal and hover states.

Asset cache identifiers are updated to V1.8.0.

The application creates tw_world_victory_awards automatically in the main database. No manual SQL is required.

Updates and hotfixes

Original release

Completed the previously dormant per-world Church feature.

Church-enabled worlds now receive the required village schema migration automatically, including existing managed worlds such as a world routed as w7.

Existing players without a Church receive level 1 in their oldest village, while new players receive level 1 in their first village.

Registered the Church as a buildable three-level building with the bundled artwork and its own information screen.

Added faith radii of 4, 6 and 8 fields for Church levels 1, 2 and 3.

Connected Church coverage to the existing combat faith multiplier: troops outside their owner's coverage fight at 50% strength.

Church-disabled worlds retain the disabled Church artwork and do not expose the building.

Added an owner-only Log in as this user (selected world only) control to World Moderation.

Reuses the player's most recent valid session in that world, or creates one without invalidating the player's other sessions.

Uses an audited, single-use handoff that expires after two minutes and a world-path-scoped browser cookie.

Added a list of the 10 closest unowned villages within 25 fields of a selected player's villages.

Staff with village-management permission can assign one of those villages to the selected player.

Assignment rechecks distance and ownership at submission time, recounts player/tribe points and ranks, refreshes map state, and records the action.

V1.7.8 village artwork positioning.

Draggable panels and per-player/per-world layout persistence.

Existing V1.6 security hardening and later gameplay changes.

Original release

Fixed the farm-field artwork fragment appearing between the village overview and the sidebar panels.

Constrained the graphical village canvas to its native 600×418 dimensions so all absolutely positioned village artwork remains anchored to the intended scene.

The farm field now appears in the brown field area at the top-right of the village artwork.

Preserved draggable panels, per-player/per-world layout persistence, and all V1.7.7 security and gameplay changes.

Events remain excluded from the draggable dashboard.

Original release

Removed the jQuery UI initialization path that still failed to activate on the deployed overview.

Dashboard title rows now receive direct mouse and touch handlers using the already-loaded core jQuery runtime.

Dragging begins after a four-pixel movement threshold, while title text selection is suppressed immediately.

A cloned panel follows the pointer and a full-height placeholder marks the destination.

Drop detection supports reordering inside either column and moving between columns.

Layout persistence remains per player and per world and is written only after a completed drag.

Links and controls inside title rows remain clickable and do not start dragging.

Events remain excluded.

Existing layout validation, CSRF protection, gameplay changes, and security hardening remain intact.

Original release

Replaced unreliable browser-native dragging on legacy table/form panels with the bundled jQuery UI 1.8.18 mouse-drag implementation.

Panel headers are now explicit drag handles.

A visible cloned panel and correctly sized placeholder show where a panel will be dropped.

Panels can be reordered within either column and moved between the main column and sidebar.

Layout saving occurs only after the drop completes and continues to be scoped to the player and current world.

Removed the previous native draggable path so two drag systems cannot conflict.

Events remain excluded.

Preserved all V1.7.4 layout validation, CSRF protection, runtime schema creation, and earlier gameplay behavior.

Original release

Reworked the graphical village overview into a wide main column and compact sidebar matching the requested reference layout.

Village, Incoming, Commands, Production, Building Queue, Units, Paladin bonuses, and Loyalty are draggable panels.

Panels can be reordered within a column or moved between columns.

The layout is saved for the logged-in player in the current world. Each world therefore retains an independent arrangement.

Events are intentionally excluded from this release.

Layout writes use the existing session CSRF key, accept only known panel identifiers, and restore omitted panels safely.

Existing V1.7.3 building deltas, queue controls, button contrast, Headquarters, Smithy, Account Manager, Speed Up, security, and world-session behavior remain intact.

Original release

Changed submit, button, and action-button labels to high-contrast white throughout the served game and public styles, including red and green actions.

Added small aggregate +N and -N level indicators beside buildings with queued upgrades or demolitions on both graphical and non-graphical village overviews.

Added a Building Queue panel between Production and Units on both overview variants.

Each overview queue row shows the building artwork, name, individual level change, projected target level, live completion countdown, and cancellation control.

Added a Docker regression gate covering queue ordering, target-level projection, cancellation links, overview placement, delta badges, and button contrast.

Headquarters construction and Demolition redesigns.

Five normal-cost construction orders, with the original extra-resource penalty beginning with order six.

Account Manager five-order construction queues.

Building Speed Up only during the final ten minutes, without shortening construction time by half.

Smithy research presentation, individual Research buttons, and the maximum three-order research queue.

V1.6.4 cross-world session repair and V1.6.0 security hardening.

Original release

Replaced the Smithy's inverted two-row research assignment box with a full-width queue styled like the Village Headquarters.

The queue now shows the technology artwork, target level, duration, completion time, and a high-contrast Cancel button for every order.

Added support for up to three sequential research orders per village; a fourth order is rejected server-side.

Individual Research buttons remain available while one or two queue slots are occupied.

Queued research uses projected technology levels so each order receives the correct resource cost and duration.

The same technology cannot be queued twice simultaneously, preventing level/cost ambiguity when an earlier order is cancelled.

Cancelling any queued order refunds its exact cost, removes only that order, and pulls subsequent completion times forward.

Completing or cancelling the active order updates smith_tec to the next queued technology for village overview timers.

Added a Docker regression gate covering the three-order limit, scheduling, cancellation, queue presentation, and next-order state.

Headquarters construction and Demolition redesigns.

Five normal-cost construction orders and the original penalty beginning with order six.

Account Manager five-order construction queues.

Building Speed Up only during the final ten minutes.

V1.6.4 cross-world session repair and V1.6.0 security hardening.

Original release

Renamed the Headquarters Demolish mode to Demolition.

Redesigned the complete Demolition table to match the V1.7.0 Headquarters construction layout.

Added classic detailed building artwork, demolition time, villagers needed, minimum-level messaging, and white-text Downgrade buttons.

Converted individual Smithy research links into matching brown buttons with high-contrast white labels.

Renamed the initial Smithy Search action to Research for consistent wording.

Removed hotfix suffixes from all visible V1.7.1 footer labels.

Expanded the Docker regression gate to compile and validate the construction, Demolition, and Smithy templates.

Five normal-cost construction orders and the original penalty beginning with order six.

Account Manager five-order construction queues.

Speed Up only during the final ten minutes, with instant completion rather than halving.

Classic detailed Headquarters artwork and high-contrast action labels.

V1.6.4 cross-world session repair and V1.6.0 security hardening.

Updates and hotfixes

Original release

V1.7.0 introduces a complete Headquarters redesign based on the classic compact construction view.

Replaced the old progress-bar building list with a compact table showing each building's artwork, current level, wood, clay, iron, population, duration, and next-level construction button.

Added a separate Not yet available section with the prerequisite buildings and levels required to unlock each entry.

Restyled the active construction queue with clear construction, duration, completion, cancellation, and Speed Up controls.

Kept demolition mode, village renaming, queue cancellation, resource availability timers, maximum-level handling, and all prerequisite/storage/farm checks.

No premium or -20% construction-time reduction is shown or applied.

Speed Up appears only for the active building during its final 10 minutes.

Using it completes that building immediately; it never halves or partially shortens a timer.

Requests are checked again on the server, so a modified URL cannot speed up a building with more than 10 minutes remaining.

Any later queue entries move forward only by the exact remaining time removed from the completed building.

V1.6.0 application security hardening.

V1.6.1-V1.6.2 minimap corrections.

V1.6.4 cross-world session repair.

Original release

V1.6.4 is the definitive cross-world session repair based directly on V1.6.3.

A valid global login now authorizes entry to any world in which the player is a member without writing to that world's legacy sessions table.

World 2, World 3, and older dynamically created worlds no longer depend on matching World 1's session-table schema.

Duplicate session cookies left by older releases are detected from the complete Cookie header instead of trusting only the single value exposed by PHP.

The valid 64-character cryptographic token is selected and the canonical root cookie is refreshed.

A legacy cookie scoped to the currently selected world is expired so it cannot continue shadowing the root cookie.

Direct-world and vacation-replacement sessions remain available as a compatibility fallback.

The obsolete V1.6.3 Docker assertion was replaced with regression gates for schema-independent authentication and duplicate-cookie recovery.

V1.6.0 application security hardening.

V1.6.1 minimap endpoint repair.

V1.6.2 right-minimap geometry across all supported map sizes.

Original release

V1.6.3 is a session-switching maintenance release based directly on V1.6.2.

Restored switching between every registered world without being redirected to the session-timeout page.

Made the valid global login session authoritative during cross-world navigation.

Replaces stale or duplicate world-local session rows with one exact copy before entering the selected world.

Verifies the complete session ID and action key after the world-local copy is written and before redirecting.

Transparently repairs a missing or outdated world-local session from the global session on subsequent requests.

Preserved direct world login and vacation-replacement session compatibility when no global session exists.

Added a mandatory Docker-build regression test for the complete cross-world session contract.

V1.6.0 application security hardening, including 64-character cryptographic session IDs.

V1.6.1 minimap endpoint repair.

V1.6.2 right-minimap geometry and all supported map sizes.

Original release

V1.6.2 is a map-layout maintenance release based directly on V1.6.1.

Corrected the right navigation minimap frame overflowing across its right-hand navigation control.

Replaced equal-width fixed table columns with explicit 11px, 267px, and 11px columns.

Set the frame to its exact 291px outer width: a 267×267 minimap, two 11px navigation columns, and two 1px borders.

Removed inherited generic table-cell padding inside the minimap frame so it cannot silently enlarge the centre column.

Kept the right minimap at its native 267×267 resolution for every main-map view size from 7×7 through 17×17.

Extended the minimap regression test to require the exact frame and column geometry.

V1.6.0 application security hardening.

V1.6.1 minimap endpoint dependency fix.

Main-map drag behavior, coordinate overlays, map-size choices, pinned village popups, and two-way minimap navigation.

Original release

V1.6.1 is a map rendering maintenance release based directly on V1.6.0.

Restored the right-side navigation minimap on the main map screen.

Restored the village-information minimap used on village detail pages.

Corrected the shared minimap.php endpoint so it loads the V1.6 security validation helper before using it.

Fixed the right minimap panel at its intended 267×267 image size instead of sizing its container as 77% of the remaining page column.

Prevented 7×7, 9×9, and 11×11 views from stretching the right minimap as the main-map viewport becomes narrower.

Preserved the main map's real 53×38-pixel tile scale at every supported view size.

Added an automated minimap regression test to the Docker build.

Includes all V1.6.0 security changes.

Requires no manual database changes.

Existing worlds, accounts, sessions, and .env configuration remain compatible.

Original release

V1.6.0 is a security-focused release based on V1.5.2-hotfix. It retains the fully opaque green village-overview badges and white building-level text introduced by that release.

Removed confirmed SQL injection paths in bonus-village lookup, global/world preferences, quest rewards, and tribe homepage/IRC settings.

Added strict integer validation and SQL escaping helpers for security-sensitive legacy queries.

Added village ownership authorization, CSRF validation, and one-time atomic claiming to quest rewards.

Prevented invalid or expired troop movements from entering the cancellation path.

Replaced predictable player session IDs and four-character action keys with 256-bit values generated by random_bytes().

Removed session identifiers from world-login URLs and rejected legacy-sized session tokens.

Added HttpOnly, SameSite=Lax, and HTTPS-aware Secure player cookies.

Added modern password_hash() storage with transparent verification and migration of both historical password formats.

Added database-backed login throttling: ten failed attempts within fifteen minutes per account or address.

Removed username enumeration from global login responses.

Restricted BBCode URLs and images to HTTP(S), added safe link attributes, and suppressed referrer data on remote images.

Re-encodes profile and tribe images as PNG after validating real image content, dimensions, size, and upload origin.

Replaced browser-visible SQL diagnostics with generic errors and server-side logging.

Added CSRF protection to friend mutations and quest completion.

Added browser hardening headers and stricter PHP upload/session settings.

Bound Adminer to loopback by default. Set TRIBALWARS_ADMINER_BIND only when deliberate remote exposure is protected by a firewall or VPN.

Removed hardcoded database and administration passwords from application configuration and the legacy initialization script.

Existing accounts retain their passwords. Their legacy hashes are upgraded automatically after successful authentication.

Existing sessions are intentionally invalidated once because V1.6.0 accepts only the new cryptographically secure token format.

Existing databases are migrated automatically to support modern password hashes and login-attempt tracking.

The container remains on PHP 7.4 because the bundled 2014-era application and Smarty 2 runtime rely on behavior removed from newer PHP versions. V1.6.0 mitigates the identified application-level vulnerabilities, but PHP 7.4 itself is end-of-life. Moving to a supported PHP release requires a separately tested modernization of constructors, Smarty, and compatibility functions; changing only the base image would make the game unusable.

Original release

Building-level badges now use a fully opaque green background.

Building-level numbers and badge timer text are forced to solid white for reliable contrast.

Legacy browser opacity filters are explicitly disabled so an earlier translucent rule cannot leak into the final badge style.

The correction is synchronized across all packaged copies of the game stylesheet.

The Docker image build includes a regression test covering the background, opacity reset, legacy filter reset, and white badge text.

Original release

Limits the log table to 25 rows per page by default.

Adds 25, 50, and 100 row-size options.

Adds compact first/previous/nearby/next/last page navigation.

Adds filters for attacks, movement processing, updates, deletions, errors, and other actions.

Preserves the action and row-count selections while changing pages.

Shows the matching record count and current result range.

Decodes legacy URL-encoded log entries into readable separators.

Orders results by newest record ID for stable pagination.

The Docker image build includes regression coverage for pagination, filters, action classification, decoding, and template controls.

Original release

Added one shared server-side content policy rather than relying on browser validation.

Matching normalizes case, HTML, accents, punctuation, repeated characters and common number/symbol substitutions.

Exact-token matching avoids broad substring blocks that would reject innocent words containing a shorter sequence.

Protected write points include registration usernames, player profile text/location, tribe names/tags/profiles/member titles/internal text/welcome messages, the internal tribe forum, village names and notebook entries, personal note titles/bodies, Paladin names, village-group names, Account Manager template names, player mail and support-ticket text.

Existing stored text is not automatically rewritten or deleted. Administrators can correct existing usernames through Global Moderation.

Added Global Moderation above the renamed World Moderation menu item.

Lists all registered accounts with search, banned-only filtering and pagination.

Staff with moderation permission can review an account, rename it, apply a permanent global ban, or lift that ban.

Username changes update the global identity plus matching player/session identities in every registered world.

Global bans use the established account-ban flag enforced by login and remove active global/world sessions immediately.

Actions require the staff action token, explicit confirmation, a reason and a one-use request key.

Added append-only history recording actor, action, old/new username, reason and timestamp.

Original release

Paladin weapon combat-scope correction.

Audited every Paladin weapon path in the live combat engine.

Confirmed ordinary attack and defence multipliers are selected through the exact configured unit-to-weapon mapping.

Confirmed Ram, Catapult, Scout, and Nobleman special effects require their intended units and matching weapons.

Fixed defensive battles incorrectly considering a weapon belonging to an origin village whose support row contained no Paladin.

Defensive weapon discovery now considers only own or supporting armies with at least one Paladin physically present in the defending village.

Added build-time regression coverage for exact unit mapping and special-effect requirements.

Original release

Docker build correction for the V1.4.4 typography release.

Corrected the global typography regression test to resolve stylesheets inside the application document root.

Removed the invalid parent-directory lookup that stopped both the app and scheduler image builds.

Preserved all V1.4.4 Arial/Verdana typography and rounded white building-level badge changes.

Verified every path used by the test exists in the packaged app tree.

Original release

Global typography and village building-level badge refresh.

Replaced the serif Georgia interface typography with a compact Arial/Verdana sans-serif stack matching the supplied reference.

Applied the typography consistently to the game, public pages, form controls, buttons, world selector, and administration interface.

Preserved deliberately monospace fields such as HEX colour inputs and technical output.

Rounded the green building-level badges on the graphical village overview.

Changed building-level text and every link state to high-contrast white.

Added a subtle dark outline, shadow, and text shadow to keep levels readable over village artwork.

Added build-time regression coverage for global typography and building-level badge contrast.

Original release

Compact Paladin weapon-bonus display.

Removed weapon artwork from the village-overview bonus panel.

Preserved the Paladin name, weapon name, affected unit, and exact bonus text.

Kept the panel compact in both graphical and non-graphical village views.

Added regression coverage preventing the oversized artwork from returning.

Original release

Village-overview Paladin identity and weapon-bonus release.

Replaced the obsolete account-wide knight name on the village overview with the actual stationed Paladin's individual name.

Shows N Paladins when multiple own or supporting Paladins are stationed in the village.

Keeps Paladin names and counts linked to the Paladin unit-details popup.

Added a weapon-bonus panel directly below the troop list in graphical and table village views.

Shows the Paladin, equipped weapon, affected unit, and exact configured combat or special effect.

Added explicit descriptions for Scout, Ram, Catapult, and Nobleman weapon effects.

Updated the Paladin unit description for the permanent ten-slot system and shared Weapons Room.

Added build-time regression coverage for names, plural counts, support lookup, popup links, and bonuses.

Original release

Paladin residents, placement, and shared weapons.

Restored the original village-specific Resident concept. It now shows the Paladin physically stationed in the currently viewed village, their home, equipped weapon artwork, and exact attack, defense, and special multipliers.

Moved the ten-slot roster to a dedicated Paladin Overview tab.

Added explicit village selection when recruiting or reviving every Paladin.

Recruitment resources and population are charged to the selected village rather than whichever village happened to be open in the browser.

A Paladin cannot be recruited in a village where another Paladin is stationed or already being recruited.

Stationing also rejects occupied destinations, enforcing one Paladin placement per village for all new actions.

Added persistent individual weapon assignments to every Paladin slot.

Kept one player-wide Weapons Room and shared discovery progress.

Limited each weapon to two equipped Paladins and added a clear rejection message when the limit is reached.

Added weapon usage counters, current-assignment controls, unequip actions, exact bonus displays, and equipped-weapon portraits.

Updated battle processing so an attacking or defending Paladin uses the weapon assigned to that specific Paladin rather than one global weapon.

Automatically migrates the legacy globally equipped weapon to Paladin 1 and adds the new schema columns to existing V1.4.0 worlds.

Added regression coverage for the Resident, Overview, recruitment placement, weapon cap, artwork, schema, and combat integration.

Original release

Multiple Paladins.

Added up to 10 Paladin slots, unlocked permanently at 1, 3, 5, 10, 20, 35, 50, 65, 80, and 100 owned villages.

Slot unlocks are permanent. Losing villages never removes a previously earned Paladin slot, and a fallen Paladin in that slot can still be revived.

Rebuilt the Statue resident view as a responsive two-column Paladin overview inspired by the supplied reference.

Added an individual persistent name, life/recruitment state, and home village for every Paladin slot.

Added per-slot recruitment, revival, cancellation, renaming, and stationing.

Changed stationing to move exactly one Paladin instead of overwriting the village Paladin count, allowing several Paladins to coexist.

Existing single-Paladin worlds migrate automatically: earned slots are created and existing Paladin units are imported into the registry.

Retained the shared Paladin weapons room and item progress system.

Added schema and Docker build regression coverage for all unlock thresholds, permanent slots, per-slot actions, and the new overview.

Original release

Fixed World Dominance showing 0 days forever for legacy and open immediately worlds.

Scheduled worlds continue to calculate age from their configured opening timestamp.

Immediate worlds now calculate age from the earliest player-owned village creation timestamp, the earliest durable world-local evidence that gameplay began.

Empty immediate worlds remain at 0 days until the first player village exists.

Added lifecycle and World Dominance regression checks for scheduled and immediate worlds.

Updated all current build, configuration, Support, Admin, lobby, and game version labels to V1.3.7.

Original release

Restored distinct red Attack and green Support Rally Point actions.

Standardized both command labels in title case and gave them consistent sizing.

Increased foreground/background contrast for red and green action buttons across normal and hover states.

Prevented the global link-color rule from making destructive link-buttons unreadable.

Made Tribe Properties Disband a clearly visible, high-contrast destructive action.

Added regression checks for the command labels, action colors, and Disband treatment.

Updated all current build, configuration, Support, Admin, lobby, and game version labels to V1.3.6.

Original release

Applied a consistent Tribal Wars-themed appearance to every in-game submit, button, and reset control, including legacy controls without a button class.

Added unified hover, pressed, keyboard-focus, and disabled states.

Improved text, password, number, email, URL, date, time, select, textarea, checkbox, radio, and file-upload controls.

Preserved the existing green, red, grey, scavenging, account-manager, and other specialized control variants.

Synchronized the root and browser-served copies of game.css.

Capitalized the Tribe Properties Disband action, styled it as destructive, and repaired its malformed confirmation call.

Added a Docker build test that prevents unstyled legacy buttons and diverged CDN styles from returning.

Updated all hardcoded configuration and footer labels to V1.3.5.

Original release

Fixed missing status images beside player names on Tribe > Members.

Replaced the incorrect world-relative graphic/stat/ URL with the configured CDN path.

Added version-based cache busting to member status images.

Corrected Vacation Mode from nonexistent blue.png to the included vacation.png artwork.

Normalized every member status to an array before rendering.

Removed a duplicate unreachable banned-status branch.

Added a Docker build test covering all six possible member-status artworks in both CDN trees.

Updated all hardcoded configuration and footer labels to V1.3.4.

Original release

Added an IPinfo public-IP lookup before player login.

Cached the browser lookup in session storage for five minutes to avoid repeated IPinfo requests.

Stored validated public IPv4 or IPv6 addresses against the authenticated player.

Used a fresh cached public IP for subsequent world-entry login-history records.

Retained the server-observed address as the fallback whenever IPinfo is unavailable, slow, invalid, private, or reserved.

Added build tests covering the lookup URL, five-minute cache, validation, fallback behavior, and world-login integration.

Updated previously hardcoded V1.3.0 configuration and footer labels to V1.3.3.

Existing login-history entries are intentionally unchanged. New entries use this behavior after V1.3.3 is deployed.

Original release

Fixed the four scavenging card artworks not loading in the browser.

Added all four 182 x 180 PNG assets to the browser-served path at app/tribalwars/global_cdn/graphic/scavenging/.

Retained a matching copy under app/global_cdn/graphic/scavenging/ for compatibility with root-based installations.

Added v=1.3.2 cache busting to the artwork URLs so previously cached missing responses are not reused.

Strengthened the scavenging build test so future releases must contain the artwork in the actual browser-served CDN tree.

The V1.3.1 clickable troop counts, styled controls, and ordered mass unlocking remain unchanged.

Original release

Restored the four supplied scavenging artworks as clean 182 x 180 card assets.

Made each parenthesized available troop count clickable so that unit's full available amount is entered immediately.

Retained the All troops shortcut and added input clamping to prevent values outside the available range.

Reworked the Scavenging and Mass Scavenging presentation with game-themed panels, cards, buttons, hover states, and responsive layouts.

Added ordered mass unlocking for selected villages. Each submission unlocks the next valid option only, preserving the required 1 -> 2 -> 3 -> 4 sequence.

Mass unlock skips villages with an unlock already in progress, insufficient resources, or all options already unlocked.

Added per-village unlock progress and next-option status to Mass Scavenging.

Original release

Scavenging.

Added four Rally Point scavenging options: Lackadaisical Looters, Humble Haulers, Clever Collectors, and Great Gatherers.

Added sequential unlock costs of 100, 500, 2,500, and 12,500 of each resource.

Added unlock times of 5, 30, 90, and 360 minutes, divided by world speed.

Scavenging hauls use the original 10%, 25%, 50%, and 75% carry-capacity efficiencies and are divided almost equally between all three resources.

Gathering duration follows the original capacity/efficiency formula with the world-speed duration factor.

Only eligible troops stationed in the village can gather. Troops remain unavailable until they return.

All four options can run concurrently, but each option can run only once per village and cannot be cancelled.

Completed runs return troops, add resources up to warehouse capacity, and generate a detailed report.

Added Mass Scavenging with village selection and automatic assignment of all eligible stationed troops.

Extracted and included the four supplied scavenging artworks.

Added automatic schema migration and Docker build regression coverage.

Original release

Village information redesign.

Redesigned every owned, player-owned, barbarian, and bonus village information page around the same responsive two-column layout.

Added a minimap centered on the displayed village plus coordinates, points, player, and tribe details.

Added a private per-player notebook for every village, including existing worlds through an automatic schema migration.

Added own attack/support commands travelling to the displayed village with arrival time, live countdown, details, and cancellation where permitted.

Added direct Center Map, Send Troops, and Send Resources actions without a troop-template selector.

Added General View of Village as the final action when the displayed village belongs to the logged-in player.

Added the latest 50 attack reports involving the village, with Select All and CSRF-protected deletion.

Added Docker build regression coverage for the complete village-information feature.

Original release

Public path hotfix.

Installed the supplied Farm Militia artwork under /tribalwars/global_cdn, matching the CDN URL resolved by world pages.

Fixed the expired-session Home page link so it resolves to the application root /index.php rather than the nonexistent /tribalwars/index.php.

Added release checks for both browser-facing paths.

All Militia simulator and report behavior from V1.2.2 remains unchanged.

Original release

Farm Militia artwork path hotfix.

Installed the supplied Militia artwork in the actual global_cdn asset tree used by world pages.

Kept the Farm presentation and all V1.2.2 Militia simulator/report behavior unchanged.

Updated the Militia release check to validate the browser-resolvable CDN asset location.

Original release

Militia simulator, report, and Farm artwork hotfix.

Added Militia to the Rally Point simulator exclusively on the Defender side.

Added defender Militia totals and losses to simulator results.

Defender troop tables in attack reports now always include the Militia column, including a visible zero-state column for reports created before Militia existed.

Replaced the Farm's generic building illustration with the supplied Militia artwork.

Extended the Militia release checks to protect the defender-only simulator rule, report rendering, and Farm asset.

Militia remains non-recruitable and cannot be sent or entered as an attacking unit.

Original release

This hotfix improves the presentation and discoverability of the V1.2.0 militia feature.

Restyled the Farm into a reference-inspired two-column layout.

Population capacity and current usage are displayed before the militia controls.

The Farm militia panel switches between Call Militia and Militia in Village according to deployment state.

Active surviving militia appear in the graphical village Overview troop list.

The militia icon and name open a dedicated unit-information popup with its statistics, deployment rules, cost and Farm availability.

Overview production figures now visibly include the active 35% militia penalty.

Militia remain separate from normal units and therefore cannot be recruited, placed in Troop Manager templates, or sent away from the village.

Original release

Every owned village can call militia from its Farm; village count does not restrict access.

A call provides 50 militia per Farm level (1,500 at level 30) for exactly three hours.

Militia have 5 offensive strength, 15 general defense, 45 cavalry defense and 25 archer defense. They require no research.

Militia are defensive-only, never leave their village and cannot be recruited or managed through any troop recruitment interface.

Wood, clay and iron production are reduced by 35% during the complete three-hour deployment.

Battle losses reduce the stationed militia. If all militia die, the village remains in recovery and cannot call them again until the original timer ends; the production penalty also remains until then.

Defense reports show militia and militia losses to the defending player only.

Existing worlds create the village_militia state table automatically on first use. Fresh installations include it in the world database templates.

Original release

V1.1.9 fixes the V1.1.8 container build regression.

Updated the Public Profile regression test to recognize that the obsolete minimap viewport polygon is now removed for every normal map.

Preserved Public Profile minimap coloring and the new single white synchronized viewport overlay.

No database migration or manual data change is required.

Original release

V1.1.8 makes both map views and their navigation information stay synchronized.

The Continent heading now follows the live map center when either map is dragged or clicked.

The X and Y center fields update with the live map position.

The main map now displays X coordinates along its lower border and Y coordinates along its left border.

Coordinate labels follow the map during dragging and respect the selected 7x7 through 17x17 view size.

Removed the old viewport rectangle drawn into the minimap image.

The remaining white minimap rectangle matches the selected main-map view size and moves live with either map.

No database migration or manual data change is required.

Original release

V1.1.7 prevents the Troop Manager from scheduling more population than a village can support.

Calculates population occupied by every completed building level.

Includes population reserved by queued construction; pending demolitions do not free population prematurely.

Includes all existing troops belonging to the village, including noblemen and the paladin.

Includes every unfinished recruitment order before scheduling another batch.

Uses the village's current farm capacity with an absolute maximum of 24,000 population; 10% population bonus villages receive no additional allowance.

Retains the existing limit of five queued batches per recruitment building and 50 troops per batch.

No database migration or manual data change is required.

Original release

V1.1.6 adds direct navigation to every Account Manager section.

The top Account Manager button now opens a dropdown consistent with the other primary navigation buttons.

The dropdown links directly to Overview, Construction, Troops, and Deliveries.

Existing Account Manager page tabs remain available for navigation inside the manager.

The legacy winter navigation receives the same four destinations.

No database migration or manual data change is required.

Original release

V1.1.5 corrects an awkward Academy translation.

Replaced It can still be generated: with Noblemen that can still be educated: on the Academy nobleman availability table.

No database migration or manual data change is required.

Original release

V1.1.4 expands Account Manager capacity and adds clearer troop and template management.

Construction assignments, troop assignments and due delivery routes now process up to 250 records per scheduler pass instead of 25.

Troop Manager shows each village's currently owned troops above its assigned template targets.

Troop progress is red below 75%, orange from 75% through 99%, and green when the target is met.

Saved custom construction templates can be edited or deleted.

Saved troop templates can be edited or deleted.

Deleting a template safely stops management for villages assigned to it. Existing construction and recruitment orders continue normally.

The built-in default construction template remains protected.

The 250-record pass limit was selected for a host providing 12 vCPUs from an Intel Core Ultra 9 185H while also running other services. It is a deployment reference, not a minimum hardware requirement. Actual load depends on world activity, database performance and the number of managed villages and routes.

No database migration or manual data change is required.

Original release

V1.1.3 improves the Account Manager troop scheduler.

Troop Manager now maintains independent recruitment queues for the Barracks, Stable, and Workshop.

Each recruitment order contains no more than 50 troops.

Each recruitment building is capped at five active batches per village.

Barracks, Stable, and Workshop queues can be populated during the same manager pass.

Existing queued troops are included when comparing current strength with template targets.

New batches are chained after the final active batch in their respective building.

No database migration or manual data change is required.

Original release

V1.1.2 improves the Account Manager construction scheduler and cleans up the Village Headquarters labels.

Construction Manager now maintains up to three queued building upgrades per managed village.

Already queued upgrades are projected when selecting subsequent upgrades, so template targets and prerequisites remain correct.

Added orders are scheduled sequentially through the existing build and event pipeline and remain individually cancellable.

Villages with demolition orders are skipped by automatic construction management.

The active construction table now uses Construction, Duration, Completion, and Cancellation.

The available-buildings table now uses Duration instead of During.

No database migration or manual data change is required.

Original release

Redesigned the Account Manager to match the compact visual style of the village overview.

Added a clearer selected-state treatment to the Overview, Construction, Troops and Deliveries tabs.

Added a dashboard-style Account Manager overview with summary cards.

Added Select All Villages controls above and below the construction and troop village lists.

Added green managed and red unmanaged status icons for every village.

Construction and troop lists now display the actual assigned template name.

Moved Stop management into the relevant village row.

Linked village names directly to their village overviews.

Moved template creation into collapsible management panels to keep long village lists readable.

Redesigned delivery creation and scheduled-route tables with village coordinates, resource icons, route state and compact inline actions.

Added responsive styling for narrower screens.

This patch does not change the permanent ten-village Account Manager unlock or its automation rules.

Original release

Added a free Account Manager that is always visible in the main navigation.

Access unlocks permanently for a player in a specific world after that player owns at least 10 villages there.

Losing villages after the unlock does not revoke it.

Added an overview showing active managers.

Added Construction Manager templates and per-village assignments.

The built-in construction template prioritizes Warehouse, resource buildings, Farm, then every remaining building.

Added custom construction templates with target levels.

Added Troop Manager templates with per-village troop targets and assignments.

Recruitment respects resources, population, research, recruitment buildings and existing queues.

Paladins and noblemen remain manually controlled.

Added scheduled Delivery Manager routes with source, destination, resources, weekdays and UTC time.

Deliveries use ordinary merchants and wait when resources or merchants are unavailable.

All automation runs through the existing world scheduler and creates ordinary visible queues and transports.

Replaced the former top-level Notes button with Account Manager.

Moved Notes into Settings directly beneath My Account in both the dropdown and left-side menu.

Existing direct Notes links redirect to the new Settings location.

Added world-local Account Manager unlock, template, assignment and delivery-route tables.

Existing worlds create these tables automatically on first scheduler or Account Manager use.

New worlds receive them from the clean world database template.

Original release

Removed the global World goal / Victory goal strip from ordinary game screens.

Victory conditions, progress, contenders, deadlines and archive status remain available exclusively under Ranking → World Dominance.

Removed the redundant lifecycle-display preparation previously performed on every game page.

No database migration is required.

Updates and hotfixes

Original release

An idle Paladin can now be stationed in any village owned by the player. Open the Statue, choose an eligible owned village from Station Paladin, and confirm the move. The destination does not need its own Statue.

Relocation uses the existing Paladin travel event, so the Paladin is unavailable as a troop while travelling. On arrival, he becomes a home troop of the selected village and can be sent from that village through its Rally Point.

The selector shows coordinates and free population for every owned village. It disables the current station and destinations that cannot house the Paladin. Capacity is calculated separately for each destination, including the larger Farm capacity of population-bonus villages. Returning a Paladin who is stationed as support to his original home does not reserve his population twice.

Server-side checks require an idle Paladin, a valid request token, an owned destination, and sufficient population. The update also consumes the exact idle Paladin row before scheduling travel, preventing a stale page from dispatching the same Paladin twice.

The packaged V0.9.9 release also includes the build-test correction discovered during first deployment: destination identifiers must use their canonical decimal form, so malformed values such as 04 are rejected consistently by both the validator and regression test.

Original release

The Rally Point form now has a Commands field (1-20, default 1). Enter troops per command and one destination coordinate pair, then choose Attack or Support. For example, 3 commands with 100 axemen sends three separate commands of 100 axemen each to that destination and requires 300 axemen at home.

Confirmation shows the command count, troops per command and aggregate troop requirements. Both the preview and final submission validate total availability. All commands use the same troop composition, destination and selected catapult target, and depart together. They appear individually in the movement list. This is immediate repeated dispatch, not a timed wave scheduler or a list of different destinations. Existing beginner-protection and target checks apply.

The outgoing command link now reads “Cancel”. The support confirmation heading and destination label were also corrected.

Original release

The homepage now temporarily caches the browser's HTTPS response from https://ipinfo.io/ip in sessionStorage for five minutes. The cache is bound to the current player and login session, so signing in again or changing accounts forces a new lookup. If browser storage is blocked, capture and saving still work.

The browser submits the captured IP to an authenticated POST endpoint. The endpoint derives the player ID from the existing main-site login session, checks a session-bound CSRF token, validates IPv4/IPv6 and capture age, and saves the latest capture in a new main-database table, tw_player_public_ip. This table is created automatically; no manual SQL is required. It retains one latest capture per player after the temporary browser cache expires. Older captures from other tabs cannot overwrite a newer capture.

Moderation → Player details → Last login IP now reads this saved IPinfo value, with capture time and the source label “IPinfo (browser-reported)”. It no longer uses the server/proxy address for that field. Existing server-observed login history remains unchanged. This is a browser-reported public IP, not verified identity evidence; a modified client can submit a different valid IP.

After upgrading, open the game homepage while logged in (or sign in again) to populate the field. Other players must do the same. Until a successful capture is saved, their field says “Not recorded yet”. Capture time is when IPinfo was queried, not a rewritten authentication timestamp.

If IPinfo is unavailable, fails CORS, is blocked or returns invalid content, no fallback proxy address is saved. The last successful saved capture remains. If saving fails, the homepage address tooltip says so and a reload retries. Trusted-proxy settings are not needed for this IPinfo capture; they continue to apply separately to the original server connection logs.

Back up your database and .env, copy the archive to /home/atxsu/, and run:

Open the homepage while logged in, allow the IPinfo lookup/save to finish, then refresh your Moderation player profile. Its Last login IP should match the homepage's IPinfo address. The address tooltip indicates whether it saved.

Original release

Refilling selected villages now loads each village's warehouse capacity using its own bonus type. A level-30 normal warehouse fills to 400,000 wood, clay and iron; the warehouse bonus fills each to 600,000. Mixed selections are handled separately. The corrected values are included in the existing saved operation plan and audit flow. Other bonuses do not increase storage.

Player details now shows Last login IP, the recorded UTC timestamp, and its source (Game home or Selected world). Uses the most recent direct-player login across those two histories; sitter/vacation logins are excluded. Missing history displays Not recorded. Values are HTML-escaped and remain inside the existing staff-only Moderation page.

This displays server login records, not the browser IPinfo result. Historical proxy addresses are not rewritten. Configure trusted proxy forwarding as described in RELEASE-V0.9.5.md to capture the original client IP for future logins. No schema migration is required.

Original release

Removed Premium Points from the homepage user-info panel. Stored balances remain unchanged.

Logged-in players' browsers request their public IP from https://ipinfo.io/ip over HTTPS. No game cookies or referrer are sent. This contacts IPinfo directly and displays its response only; it is not saved as verified login evidence.

Requests time out after four seconds. If blocked, unavailable, or returning invalid content, the panel retains the server-observed address. Hover over the address to see its source.

Added trusted-proxy client IP resolution for server-side login history and existing request-IP uses. Supports IPv4/IPv6 and explicit IP/CIDR trust lists. Untrusted request headers are ignored. Traverses X-Forwarded-For from the nearest hop to the first untrusted address.

Set TW_TRUSTED_PROXIES in /opt/tribalwars/.env to the actual reverse-proxy address seen by the app, and any additional trusted proxy hops, comma-separated. No proxies are trusted by default. Do not trust arbitrary private networks or every address.

Your HTTP reverse proxy must supply X-Forwarded-For with the actual connecting client's IP. Configure its handling of upstream headers so clients cannot impersonate other addresses. Pure NAT/port forwarding cannot recover an original address that has already been lost; the first HTTP proxy must see the client address.

The screenshot's 10.250.0.1 may be a gateway or proxy. Verify that role before adding it to the trust list. Browser IPinfo display works without this setting, but server-side records require correct forwarding and trust configuration. Existing login history is not rewritten. VPN/shared public IPs identify connections, not unique people.

Back up the database and .env first, copy the archive to /home/atxsu/, then:

No schema migration is required. After adding/changing TW_TRUSTED_PROXIES, recreate app and scheduler with docker compose up -d --force-recreate app scheduler.

Original release

Fixed the resource lookup shared by the Other offers list and offer acceptance. The legacy expression $$row['buy_ress'] is evaluated differently under PHP 7, so it could reject trades with “Not enough resources” even when the village had the requested wood, clay or iron. An explicit resource map now checks the requested resource against the amount for the selected trade quantity.

A successful acceptance now returns the status expected by the controller, which redirects back to the offer list. Zero-quantity requests and offers with no remaining reservations cannot create empty shipments. Failed submissions now distinguish insufficient merchants, insufficient resources and unavailable offer quantities.

The change covers the shared world implementation and the legacy root copy. No database migration or resource/troop recalculation is required.

Original release

Notes now supports up to 100 separate titled notes per player per world. A compact title list sits beside the editor. Create, edit and permanently delete notes with an explicit deletion confirmation. Notes are available across all your villages in the same world.

The old notepad is imported once as My original note on first opening Notes. Its original database value is retained as a fallback; deleting the imported note does not reimport it. New tables are created automatically.

Titles and contents are plain text and escaped on display. All note lookups and mutations are scoped to the signed-in player and selected world. Writes require POST and a session-bound token. Revision checks prevent stale tabs overwriting newer text. Limits: 120 bytes per title, 10,000 bytes per note.

Includes all V0.9.2 features. No new game-rules page is added.

Validation: added Docker build checks for input limits, one-time migration, unknown-note rejection, scoped mutations, stale edits, deletion confirmation and escaped template rendering. PHP and Docker are unavailable in this environment, so these checks still need to run during the container build.

Original release

Fix dropdowns closing while moving from a top navigation button into its submenu: anchor each popup to its parent cell, remove the old margin and overlap the edge by one pixel.

Apply the same darker gold button styling to all top-level items, including Notes and Logout. Only dropdown buttons display arrows.

Preserve submenu row styling, destinations and keyboard focus access.

Update the navigation stylesheet cache version for every world using the shared game template.

Includes all V0.9.1 features. No database changes are required for this styling update.

Validation: source checks passed. Browser hover testing was unavailable because Chromium is not installed; the full PHP/Docker build was not run here.

Original release

World lifecycle controls are available under Admin → World Settings → World Lifecycle for Owners and the built-in administrator. Existing routine Administrator permissions remain unchanged.

Schedule opening, registration closing and an optional ending in UTC.

Closing registration prevents new world memberships; existing players can continue.

Choose a player or tribe points target, or the highest player/tribe score at the scheduled end.

Points use the sum of currently owned village points. Tied top scores share victory. A target triggers on detection; the highest eligible score wins. A deadline with an unmet target archives standings without a winner.

Finalization freezes gameplay and stores immutable player and tribe leaderboards. View these through Statistics → Archived final leaderboards.

Archives survive deletion of the live world. Finished worlds cannot be reopened or reset; create another world for a new round.

Manual access closure does not pause timers or victory checks. A future opening date pauses event processing until opening.

Saving lifecycle settings enables access at the specified opening time. Registration has its own enabled/disabled selection. Opening time cannot change once players have joined.

Original release

The Admin panel now has Staff Accounts for Owners and Administrators, plus My Staff Account for every staff member. Staff identities are global across worlds and Support, and remain separate from player accounts.

| Role | Permissions | Can create | |---|---|---| | Built-in superuser | Every permission, using the existing container-configured credentials | Any staff role | | Owner | Every Admin and Support tool, including world resets, creation/deletion and legacy utilities | Owner, Administrator, Moderator, Support | | Administrator | Player moderation, village creation/changes/destruction, routine world settings, starting buildings, health, global info, mass mail, logs and tickets | Administrator, Moderator, Support | | Moderator | Player bans, lifting bans, private moderation notes, and support tickets | None | | Support | Ticket replies, private ticket notes, status and priority; no player moderation, village tools or world controls | None |

Administrators may manage existing Moderator and Support accounts. Only Owners/the built-in superuser may manage existing Administrator and Owner accounts. No staff member can change their own role or enabled status. Everyone with a staff account can change their own password after entering the current one. The built-in superuser is never a mutable directory entry and cannot be disabled, renamed, reset or downgraded here: its credentials remain TW_ADMIN_USER and TW_ADMIN_PASSWORD in the container configuration.

Account creation defaults to Support. Usernames are case-insensitive and normalized to lowercase, 3-40 letters/digits/dots/underscores/hyphens. The configured superuser name is reserved. Staff passwords are hashed with PHP's password API and must be 12-72 bytes. Creation does not send email; give the initial password directly to the staff member.

One shared staff login for Admin and Support. Player login never grants staff privileges.

Opaque random session cookies, with only their SHA-256 hashes stored in the database, expiring after 12 hours. Existing static admin cookies are not accepted; sign in once after upgrading.

Role and enabled status are fetched from the database on every request. Role/status/password changes revoke all sessions for the affected staff account. Already-running requests are not forcibly interrupted.

Built-in sessions are invalidated if the container credentials change. Logout revokes the current server-side session.

Staff login is limited to eight attempts per username per 15-minute window; the counter clears after successful login.

Menus reflect capabilities, while server-side dispatch also rejects unauthorized direct URLs, village actions/recovery requests, world lifecycle requests and staff-management submissions.

Legacy admin PHP action/module files reject direct requests outside the authenticated dispatcher. Unmapped legacy screens are Owner-only.

Staff changes use CSRF checks and transactional account checks. Account changes and sign-ins are recorded in the staff audit; moderation/village decisions and ticket replies use the actual staff name.

Older main-menu mutation forms now require POST and a session-bound action token. Reset World remains Owner-only, requires a typed world-specific confirmation, and records the request in the staff audit. A legacy malformed sessions-table reset query was corrected. New announcements accept plain text and safe HTTP(S)/site-relative links; displayed announcements, logs and mail form values are escaped. Bonus-village creation validates its numeric bonus type.

Support ticket privacy now means the ticket owner and authorized staff. Private staff notes remain hidden from players. Staff replies continue to feed unread support notifications. The explicit player-ticket view still works when a staff member also has a player login.

Original release

A compact parchment notification bar now appears above each in-game screen, with consistent counts and direct links for incoming attacks, pending tribe invitations and tickets with unread support replies.

Attacks are counted from visible, live attack movements targeting your villages in the selected world. The previous cached attack badge is replaced by this shared bar.

Invitations count pending invitations from existing tribes when the player has no tribe; the link opens the tribe invitation screen.

Support counts tickets, not individual messages, across all worlds. Only public administrator replies count. Private staff notes, player replies, system entries and imported legacy entries do not.

Opening your own ticket marks only the administrator replies included in the loaded history as read. A later reply becomes unread again. Administrator viewing does not clear player read markers.

The support link explicitly selects the player view even if the browser also holds an administrator login. Use Administrator login to return to the administrator view; existing authentication and ownership checks remain required.

Counts refresh when loading or refreshing a game page. This release does not add background polling or external notifications.

The new global tw_support_reads table is created automatically when authenticated Support opens. Existing public administrator replies initially count as unread until opened. In-game counting also works before this table exists. Existing tickets and game data are preserved.

Validation: unread SQL was exercised with an in-memory SQLite fixture for owner isolation, private/system exclusions, read markers, subsequent replies, counting one ticket for multiple replies, qualified list correlation and upgrade fallback. Source and route wiring were inspected. PHP helper/ownership/upgrade/syntax checks are included in the Docker build. PHP, MariaDB, Docker and browser runtime tests could not be executed in this workspace; deploy only after the Docker build succeeds.

Original release

Village groups are available under Overview > Village Groups and the Groups overview tab. Add Offense/Defense/Resources with one button, create custom groups, rename/delete groups, and assign checked villages in bulk or return them to Ungrouped. A village has one group; groups are private per player and world. Deleting a group leaves villages intact. Village assignment lists are paginated at 100 rows.

Combined, Production, Troops and Groups offer All/Ungrouped/named-group filters and sorting by name, points or coordinates, ascending or descending. Selections carry between overview tabs via links. Commands and Incoming intentionally remain unfiltered and arrival-ordered so group selection never hides troop activity. Sorting does not alter village-arrow order.

New world-local tables store groups and memberships without repurposing legacy group fields. Tables initialize automatically. POST changes use a session-bound signed token, world locking and server-side ownership validation; changes to the new tables are transactional. Captured villages do not inherit the previous owner's private group in the new owner's view.

Based on V0.8.7. Source wiring reviewed. Docker build includes validation/sorting/ownership fixtures; PHP, database and browser execution were unavailable here, so these fixtures and integration behavior remain unverified at runtime. Archive checksums verified.

Original release

Admin Home begins with World health for the selected world. The summary observes the scheduler advisory lock and counts construction, demolition and movement entries more than 120 seconds overdue. The worker-lock indicator is an observation, not proof of successful processing or a heartbeat history. No worker lock can briefly occur during worker restart; rescan before treating it as an outage.

Run read-only scan shows up to 30 oldest overdue events per category and checks 100 player-owned villages per page, with navigation through the whole world. It compares cached troop totals with all troop-location rows belonging to each idle village, including support stationed elsewhere. Population is calculated from cumulative building requirements plus those troops, with the village's bonus-aware capacity.

Villages with movements, recruitment or building/demolition queues are deferred. Missing home rows, invalid troop values, duplicate destinations or missing destination villages require record review instead of numeric repair. Repeated source reads detect concurrent changes; results remain provisional in a live MyISAM world. Over-capacity population is distinguished from a cached-value mismatch and does not propose troop deletion.

Expandable repair previews display stored and calculated values. These are proposals only, not executable SQL. Overdue-event guidance directs staff to investigate logs and resume normal event processing instead of deleting events. No repair action, scheduler restart, troop change or database migration is performed by this dashboard. The health reader rejects non-SELECT queries and avoids the standard world manager's schema initialization. Access is through the existing administrator-authenticated Home route.

Includes V0.8.6. Source/schema checks completed and archive checksums verified. New Docker build fixtures cover stationed support totals, population, bonus capacity, mismatch previews and the read-only query guard. PHP/Docker, live database integration and browser rendering were unavailable here; fixtures were not executed in the authoring environment.

Original release

Top-level dropdown triggers now have subtle parchment/gold shading, inset brown borders, a small downward caret, and a brighter hover/focus state. Includes Overview, Reports, Messages, Ranking, Settings, and Tribe when its dropdown is available. Popup item styling, text and destinations are preserved. Keyboard focus also exposes the existing popup.

Based on V0.8.5. Popup link markup and archive integrity checked; browser rendering and PHP/Docker execution not performed. No database changes.

Original release

Reports dropdown now matches the sidebar: All, Attacks, Defense, Support, Trade, Other. The Trade filter no longer displays Market. Existing links and filtering are unchanged. Includes all V0.8.4 changes.

All six label-to-route mappings and archive checksums verified. Runtime/browser testing not performed. No database changes.

Original release

Messages dropdown and sidebar now use the same labels and order: Inbox, Outbox, Archive, Write Message, Block Sender. Existing routes are preserved. Based on V0.8.3, including wider layouts and all prior features. No database changes.

Verified all five dropdown labels against their routes and sidebar entries. Archive checksums verified. PHP/Docker and browser execution not performed.

Original release

Game desktop layout expanded from 980px to 1176px (+20%), including the header, navigation, game panel and footer. Intermediate screens use the available width, retaining the existing 980px minimum for legacy game tables. Font sizes are unchanged. Combined and Production overview names, headings and population links avoid awkward line wrapping.

Admin content maximum width expanded from 1180px to 1416px (+20%). Moderation gives the village list slightly more space, keeps short table headings/coordinates/points together, and stacks the profile columns on narrower screens.

Includes all V0.8.2 functionality. No database changes. Source and archive integrity checked; browser rendering and PHP/Docker execution unavailable here.

Original release

Moderation player profiles now let administrators apply, replace or remove a bonus on selected villages, or choose a bonus while creating a village. All six existing bonus types are available. Creation defaults to ordinary villages. The player's village list marks existing bonus types.

Uses existing administrator form verification, world locking, ownership validation, operation recovery and audit history. Bonus updates record the requested type and settle accrued resources under the old bonus before changing it. Buildings, ownership and troops are retained. Existing queues are not rescheduled. Removing a capacity bonus can leave over-capacity population; normal game limits apply. No manual SQL required.

Based on V0.8.1. Source and archive checks completed; PHP, Docker, database integration and browser execution were unavailable here.

Original release

Combined and Production overviews now load farm and warehouse capacity separately for each village, using its own bonus configuration rather than the currently selected village. No population or troop data is modified. At the standard level-30 farm capacity, 26,385 used population in a population-bonus village now shows 15 available (26,400 capacity), instead of -2,385. Genuine over-capacity values remain visible.

Both overviews include a compact Bonus column with a building icon and a hover description; ordinary villages show a dash. Saved V0.8.0 features and the support cookie hotfix are retained.

PHP/Docker and browser execution were unavailable. Archive integrity and source wiring were checked locally; a focused PHP capacity regression check is included in the Docker build.

Original release

Based on V0.7.9 hotfix 1, including support cookie cleanup.

Village arrows now wrap: previous on the first village opens the last village, and next on the last opens the first. The existing name/ID ordering, current screen and mode are preserved. Navigation stays within the current player and world. For a single village, arrows remain disabled.

Settings shows 1 January 1970 when no valid birthday is saved. Existing valid birthdays remain unchanged; this does not overwrite player data.

No manual SQL or environment changes are required. PHP/Docker/browser execution was unavailable here; source changes and archive integrity were checked locally.

Original release

Based on V0.7.8, including the corrected growth test and preceding navigation fixes.

The support portal at /zapping_support/ now uses the player's existing main-page login. Each player sees only their own tickets, replies and previous attachments. They can create tickets with a subject, category, world and description, reply, resolve and reopen them. A reply reopens a resolved ticket. General/account tickets can be filed without selecting a world, including requests about world access.

The administrator can view the full queue, filter active/all/resolved and individual statuses, search subjects or ticket numbers, reply, change priorities, set Open / In progress / Waiting for player / Resolved, and add private notes. Notes are never included in the player's history query. Changes are recorded in the ticket thread. Lists are paginated in groups of 25. Timestamps are UTC. No email notifications or new file uploads are implemented in this release.

/zapping_support/admin/ uses the exact administrator credentials and admin_auth cookie used by the game Admin panel. An existing administrator session is recognised. Otherwise, sign in there with TW_ADMIN_USER and TW_ADMIN_PASSWORD as configured for the server. Support no longer grants rights from player administration flags or legacy support_session values. The Manage users tab and its old action endpoint have been removed.

Every ticket read, reply, status update, priority change and attachment download checks administrator authority or ticket ownership on the server. The player cannot access another player's ticket by changing an ID. Players cannot add private notes or set administrator-only workflow statuses/priorities. All mutations require POST and a session-bound CSRF token. Ticket updates use row locks, revisions and transactions to reject stale forms. Creation/replies have request keys to avoid duplicate submissions. Ticket text and imported legacy text are rendered as escaped plain text.

Support logout logs out the shared administrator account; it does not erase the player's game session. The portal does not use the old independent support password login.

The first authenticated portal requests create tw_support_tickets and tw_support_messages in the main database and import previous support_ticket/support_response records in batches. Migration preserves recorded ticket owner IDs and original tables, and uses unique legacy IDs to avoid duplicate imports. Legacy replies are labelled legacy rather than inferring trusted administrator roles from their author text. Tickets whose recorded owner no longer exists remain available to the administrator.

Old showticket links map to imported tickets and then pass through the same ownership check. Old direct-action scripts no longer run their former SQL or accept state-changing GET links. Public access to the uploads directory and support log files is denied by the Apache configuration. Previous attachment metadata is shown only on an authorised ticket; its download resolves the stored file within the uploads directory, checks ownership again and serves it as an attachment. If the old file is absent, the portal reports it as unavailable. No new attachments are accepted in this release.

No manual SQL or changes to .env are required. Existing game data and world routing are retained. Use the usual extraction, build and recreate procedure without deleting database volumes.

Original release

Based on V0.7.7, retaining the V0.7.6 growth-test hotfix.

Registration information now reads "Registered on 21.08.2026 at 14:24:52", using an explicit date rather than appending the generic "On/Today/Tomorrow" formatter. Other date displays are unchanged.

Statistics opens at /?screen=stats inside the existing main-page layout.

The legacy /stats.php entry point redirects to /?screen=stats. An old /stats.php?screen=home link redirects to /?screen=home; other supported main-page screens work similarly. Unsupported screen values fall back to stats.

Main navigation links for Home, Rules, Team and Statistics use root-relative URLs, preventing the current script filename from becoming part of the destination.

No database changes or manual SQL are required. Validation: source/link review, template structure and archive integrity checks. PHP and Docker execution are unavailable in the authoring environment; existing build gates remain enabled.

Original release

Based on V0.7.6 hotfix 1, including its corrected zero-point Rally Point growth test.

The main-page and in-game player world selectors share a compact parchment panel, green world buttons, status text below each button, and a centred Close control. The current in-game world has a green non-link button and a Current world caption. Other joined, accessible worlds retain their existing authenticated login links.

The in-game panel opens above Select World and is clamped within the viewport horizontally. Close, Escape and outside-click dismissal are retained. Resizing repositions an open panel. The main-page popup now fully contains two buttons and wraps additional worlds into rows; long names wrap instead of spilling outside. The selectors share a versioned stylesheet so every world receives the same appearance.

World eligibility, memberships, bans, world switching, growth and moderation logic are unchanged. No database migration or manual SQL is needed.

Validation performed: JavaScript syntax and isolated interaction checks for opening, closing, Escape, outside clicks, focus restoration and viewport clamping; template block checks; release diff and archive integrity checks. A browser render could not run because the local browser executable is unavailable. PHP/Docker checks could not run in this workspace; existing build checks remain in place.

Original release

Hotfix 1: corrected the growth test to allow the zero-point Rally Point level-1 upgrade at the ceiling. A second case verifies that no positive-point upgrade fits after Rally Point is built. Gameplay files are unchanged from V0.7.6. The reported host build passed all earlier fixtures; the corrected growth fixture has not been executed in this authoring environment.

Moderation > Review player now offers:

Create one village at specified empty coordinates, using the selected world's starting building defaults. Academy and Statue start at zero; no troops are granted.

Max buildings in up to 20 selected villages. Construction and demolition queues must be empty; troops, research and ownership remain unchanged. Resource production is settled at the old building levels first.

Fill resources up to each selected village's current warehouse capacity.

Destroy selected villages with the existing exact-selection preview and typed confirmation, while player access stays open.

Destruction still refuses active movements, merchants, offers, queues, events, outside/supporting troops and noble-origin dependencies. Finish or cancel those dependencies first. It does not silently delete other players' armies or outstanding trades.

New operations record reasons, affected IDs and snapshots. Creation does not reuse deleted village IDs. Points, village counts, player and tribe rankings, population use and map refresh flags are updated as appropriate. There is no one-click Undo.

World Settings includes an enable switch, a point ceiling (initially 9,000) and minutes between upgrades (initially 0.5, matching the previous configured interval). These are separate per world and can be edited after players join.

Abandoned, barbarian and unowned bonus villages can gain one eligible building level per interval. Ownership, prerequisites, maximum building levels and the resulting point total are checked. An upgrade never crosses the ceiling. Some ceilings cannot be reached exactly; the village stops when no legal upgrade fits. Lowering the ceiling pauses growth above it rather than demolishing ordinary buildings. Raising it allows growth to continue. Player-owned bonus villages are excluded.

Academy and Statue never grow. Existing unowned villages have these two buildings removed on the next scheduler tick, even when ordinary growth is disabled. Other buildings and stationed troops are retained. Newly generated unowned villages also start without Academy or Statue. Captured villages stop automatic growth once they belong to a player.

The previous growth query omitted l_grow even though the function used it. This is corrected, and point checks use the actual building levels rather than stale cached totals. Growth settles resources before changing production levels.

Web game requests and scheduler event ticks now share a per-world database advisory lock. Event workers release it before sleeping; they do not hold it for the full daemon minute. Village tools use the same lock, so players need not be logged out and world access need not be closed. Separate worlds use separate locks. Requests may wait briefly during another action; a timeout refuses the request instead of proceeding without a lock.

The legacy world tables are MyISAM. New village tools journal their planned changes in the global tw_village_tools table; destruction retains tw_village_deletions and its table locks. An interrupted prepared operation temporarily blocks game actions and event processing for that world until an administrator resumes it from the affected player's moderation profile. This prevents play against partially changed data. Snapshot records are not a database backup or rollback transaction. The recovery buttons replay the stored operation, not a new creation.

Original release

Based on V0.7.4. The scheduler and timer fix, moderation, shared stylesheet cache key and earlier gameplay changes are retained.

Every administration section now has the same bounded content column, consistent table sizing and form widths. The left Main Functions menu remains in place. A shared Select World dialog is available on every authenticated admin page, with world buttons, current-world indication and player-access status. Switching preserves the section but drops player IDs, village selections and action parameters. Global pages are identified as global.

The existing self-ban safeguard remains. The moderation profile now explains why the signed-in player's Ban option is hidden. Online status does not stop another player from being banned. The owner can moderate that account from a separate administrator browser session without a player login.

1. Close player access for that world in World Settings. Background events continue. 2. Open Moderation and review the player. 3. Select up to 20 owned villages, provide a reason and choose Review selected villages. 4. Review the exact village names, IDs, coordinates and points. Type the displayed DESTROY N VILLAGES phrase and confirm. 5. Reopen the world after successful completion.

This removes the selected villages from the map, including their home troops and stored resources. It does not convert them to barbarian villages or refund resources. The player's other villages remain intact. A player losing their last village follows the game's normal village-creation rules on next login.

Deletion is refused while movements, merchants, market offers, construction, demolition, recruitment, research, pending events or non-home stationed troops reference the selection. Surviving conquered villages cannot be left referring to a deleted noble-origin village. These conditions are checked again immediately before deletion. Village ownership and identity must still match the reviewed selection.

The operation waits for the current daemon batch, then locks world tables for final checks and deletion while the world is closed. Player/tribe points, village counts, ranks and relevant surviving conquest counters are recalculated. Historical reports and messages are retained; old links to deleted villages no longer open a live village.

The global database automatically receives tw_village_deletions, containing snapshots of removed villages and their troop-placement rows, reason, administrator, request ID and prepared/complete status. Moderation history records preparation and completion. These snapshots are recovery data, not a one-click Undo feature.

The legacy world tables use MyISAM, so this is not claimed to be a rollback transaction. If a process stops mid-operation, keep the world closed and use Review and finish this operation on the player's moderation profile. Completion is retryable with the same operation ID. World Settings refuses to reopen a world with a prepared operation. Unexpected schema/database errors may need administrator investigation before recovery can finish. Do not manually reset/delete a world while a prepared operation is unresolved.

Forms bind confirmation to the world, player, exact village IDs and identity fingerprint, have expiring signed tokens, and require the typed phrase. Selection changes require a new review.

Original release

The event daemon already processes each world for approximately 59 seconds. The scheduler then slept another 60 seconds, leaving a minute-long gap with no event processing. Reduce this additional sleep to a one-second restart backoff. Existing per-world daemon locks and parallel processing remain intact.

Overdue Town Hall construction/demolition queues show “Completing…” instead of a negative duration and refresh every three seconds until the event worker completes the job. Refresh uses a clean viewing URL, never a build/cancel action URL. Refresh pauses in a hidden tab or after input has been edited to preserve unsaved form data.

This does not alter building durations, world speed or stored queue timestamps. The scheduler improvement also reduces the processing gap for other scheduled events. No database migration is needed.

Shell syntax and JavaScript syntax/behaviour checks passed locally; archive contents verified. Live Docker/PHP/database validation was unavailable. A worker that fails to run still requires its logs to be inspected; the UI does not mark an unprocessed build complete.

Original release

Based on V0.7.2. All worlds now load the same canonical administration stylesheet with a SHA-256 content cache key. This applies to the administration login, administration pages and world-ban notice. The actual CSS and all moderation/gameplay behaviour are unchanged.

The content key changes whenever admin.css changes, avoiding stale per-world cached styling after an upgrade. No database migration or manual CSS edit is required.

Validation: verified the CSS is byte-identical to V0.7.2, both admin templates receive the shared URL, and the notice uses the same helper. Archive files checked against their SHA-256 manifest. PHP/Docker/browser runtime testing was unavailable in this workspace.

Original release

Select the world using the world links at the top of Moderation.

Search players by name or ID; filter by active bans or activity within five minutes.

Review points, rank, tribe, account registration, last activity and owned villages.

Ban for one hour, 24 hours, seven days, 30 days, or permanently. Replacing a ban explicitly creates a new recorded decision.

Lift active bans with a reason. Add private staff notes independently of bans.

Browse paginated player and world audit history. Records retain the player name, administrator login name, reason, action and timestamps in UTC.

Ban reasons and expiry are shown to the player, alongside Support/Appeal and world selection links. Private notes and unban reasons are not shown to players.

Signed-in players are checked on their next authenticated world request. Vacation replacement also checks the replacement player's world restriction.

Timed bans expire automatically when access is checked. There is no dependence on a scheduled expiry task. Past decisions stay in the audit history.

World bans do not prevent access to other worlds or Support. Production, movements, incoming attacks and recruitment timers are not paused.

The admin's signed-in global player account cannot be banned from the same browser session. Administration still uses the existing shared administrator login; the history records that login, not separate staff identities.

An InnoDB append-only moderation ledger is automatically created in the global database. Records are scoped by both world ID and world database. Existing legacy world bans remain effective until lifted. Once a decision exists, the ledger determines access; do not edit the old users.banned field to change a moderated player's status. Old administration ban routes redirect to Moderation.

Ban/unban decisions do not alter troop counts, villages, resources, gameplay timers or the global account ban flag. This release does not reconcile the earlier stale troop-total issue.

Forms use signed, world/player-bound tokens with a 30-minute expiry, explicit confirmation, single-use request IDs and revision checks. Per-player locks serialize decisions. The audit event itself is the authoritative state change, so no separate ban flag can be committed without its matching history record.

Original release

Based on V0.7.0. Adds Disband beside Recruit on unified recruitment, Barracks, Stable and Workshop. Mass recruitment remains available.

Disband accepts specific quantities of the selected village's own completed troops currently at home. Individual building screens accept only that building's units. Paladins and noblemen remain excluded. No support from another village, travelling troops, away support or queued recruitment is removed.

Disbanding is immediate and permanent, with no resource refund. The home troop count, stored total and used farm population decrease together in one guarded multi-table UPDATE. The server verifies the authenticated village owner, security key, confirmation, allowed units, integer quantities and sufficient counters/population. Invalid quantities or insufficient counts cause no update. Refreshing after success does not repeat the action.

This feature does not reconcile pre-existing stale troop or population totals.

Validation: local template structure and source route checks; archive hashes. Docker retains earlier checks and adds PHP tests for quantity validation, guarded query accounting, and Smarty rendering of all four Disband screens. These are fixture/static tests, not a live database integration test. PHP/Docker were unavailable locally; build and live gameplay tests must run on the host.

Upgrade over the existing installation, preserving .env and database volumes. Existing w1/world routes are retained. No database migration required.

Original release

Based on V0.6.9.

Main-page navigation now labels the Team page as Team.

Restored /stats.php, which renders Statistics inside the existing main-page layout. ?screen=stats works too.

Live per-world aggregates: registered players, active players within five minutes, tribes, player-owned villages, barbarian/unowned villages, and total player-village points. World access status is shown.

Global account totals and activity are separate from world membership counts. No player emails, IP addresses, or private account details are added to Statistics.

Statistics work for visitors and signed-in players, with an empty state when there are no worlds.

Local verification covers routes, template structure, shell/Compose syntax and archive hashes. The Docker build retains existing checks and adds statistics query, formatting, Smarty rendering and PHP syntax checks. PHP/Docker were unavailable in the editing workspace; live database/browser verification remains for the host.

Upgrade by extracting over the installation with --strip-components=1, building app/scheduler and recreating services. Existing .env, world settings and routes are preserved. No new database migration.

Original release

Based on V0.6.8.

Friends now has the Settings heading above the shared sidebar and Friends content, matching the other Settings pages.

The in-game footer replaces Forum with Discord, using the community URL saved in Administration → Global Info. If no URL is configured, the link is hidden, matching the main page.

Footer Help opens /zapping_support/, the existing support directory, from any world route.

Existing world routes and .env are preserved. No database migration. Template structure, link targets and archive hashes checked locally. The changed game PHP entry point is included in the existing Docker syntax gate. PHP/Docker and live browser checks were unavailable locally.

Original release

Based on V0.6.7. Reorders the administration Main Functions menu and applies the requested capitalization:

1. Home 2. Global Info 3. Mass Mail 4. World Settings 5. Starting Building Levels 6. Barbarian Villages 7. Bonus Villages 8. Reset World 9. Logs 10. Logout

Menu destinations are unchanged. Verified exact order and labels, and compared against V0.6.7 to confirm only the menu and release version labels changed. No database migration. Existing world routes, including w1, remain stored in the database. Preserve .env and database volumes during upgrade.

Original release

Based on V0.6.6. Support branding only, plus release version labels.

Replaced 15 legacy publisher header images across player/admin support pages with TribalWarsClone text.

Removed both Tribal Wars game-logo placements (support entry and admin user-management pages).

Replaced all 12 existing support footers with exactly © 2026 TribalWarsClone.

Updated the support name, page title and legacy footer configuration.

Local source scans and shell syntax checks passed. All changed support PHP files are included in the existing Docker PHP syntax gate. PHP/Docker and live browser validation were unavailable locally. Existing game functionality is retained from V0.6.6.

Extract over the installation with --strip-components=1, build app/scheduler and recreate services. The archive contains no .env and does not delete database volumes.

Original release

Based on V0.6.5.

Select World in the fixed bottom bar opens a parchment popup listing the player's joined, open worlds. The current world is marked. Closed, future, ended, unjoined and banned worlds are excluded. Closing registration does not hide a world from existing members.

Switching uses the existing authenticated main-account login route. A player whose main account session has expired may need to log in again; no new session bypass was added.

The popup closes with its close button, Escape, another click on Select World, or a click outside it.

Friends sits next to Forum, Help and Profile.

The in-game title is lowered by 14 pixels. The normal night village view is brightened by 16%, keeping the night artwork. Day artwork is unchanged.

The Settings dropdown, Settings sidebar and Friends sidebar share the same menu: Profile, My Account, Change Password, Holiday, Friends, Logged In.

Upgrade normally over V0.6.5, preserving .env and database volumes. No database migration is required.

Local validation: JavaScript parsing and popup event tests; shell syntax, Compose structure, shared menu includes, and archive hash verification. New PHP build checks cover membership filtering, menu order, Smarty rendering and PHP syntax. PHP/Docker/browser execution was unavailable locally; the PHP checks run during the Docker build, and live switching requires testing on the host.

Original release

Based on V0.6.4.

Administration sidebar: World Settings contains world selection, configuration, creation and deletion. Global Info contains the community link, team and source credits. Home retains announcements and its existing login controls.

Each settings form saves and redirects to its own page. Global Info remains shared across worlds.

Player world selection uses direct links and displays Join world, Enter world, Registration closed, World closed, Not started yet, World ended, or Account banned.

Closed worlds explain why access is unavailable instead of silently redirecting home.

Corrected the swapped session ID/security-key columns when entering a world for the first time.

World registration uses a POST with the existing session security key. Joining a second world keeps the first world's membership and progress.

To open World 2, select it under World Settings, enable Player access open and Allow new players to register, and save. Scheduled start/end dates still apply. New worlds deliberately remain closed until opened by the host; this upgrade does not change those settings.

Upgrade by extracting over the existing installation with --strip-components=1, building app/scheduler and recreating services. The archive does not contain .env and does not remove database volumes.

Verification: local shell/Compose/template-structure and archive integrity checks. Docker build retains prior PHP tests and adds world access-state, menu-route, session-column and actual Smarty rendering checks. PHP/Docker were unavailable in the editing environment, so these PHP checks and live multi-world login still require execution on the host. No live database test is claimed.

Original release

Built forward from V0.6.3. This release adds world administration at Administration → Home.

Select a world using the links above the settings form. Its URL selects the database used by the other world administration tools. Main-page/community/team settings remain global.

Settings include name, player access, registration access, start/end dates, game speed, independent resource multiplier, movement multiplier, merchant speed, loyalty recovery/damage, protection, cancellation windows, starting village count, tribe controls, morale, scouts, gold coin costs, and existing unit/building system switches. Registration shows the effective settings from the same stored configuration.

Game speed multiplies production, movement, loyalty recovery, and build/research/recruitment speed. The resource multiplier additionally scales production; the movement multiplier additionally scales unit and merchant travel. Existing travel and queue completion timestamps are retained. Resource balances and loyalty accrue at the old rate before rate changes. Scheduler configuration refreshes each iteration.

Academy/farm systems, archer/church/paladin options, and capacity curves are locked after players join. These switches expose the legacy engine's existing behavior; this release does not add new combat or church mechanics. Capacity values scale the existing level curves, with zero retaining defaults.

Closing player access blocks game access but does not pause existing timers. Closing registration alone keeps existing players able to log in. Dates use the configured server time zone. Changes persist in the main database across rebuilds.

Creation copies the original world's table structures and saved settings, including schema defaults for starting buildings. It does not copy player data. Each new world receives its own database and URL and starts closed. Configure it, then enable player access and registration.

World URLs share the current release code. Routes are reconstructed from the world registry when containers start. Each world has its own scheduler process. Rebuilding does not remove worlds or their settings.

Deletion permanently drops a managed world's database and removes its registry entry. It requires closing the world first and typing its exact name. The original world is protected because it supplies the code and source schema. A busy scheduler may require retrying deletion after a minute. Back up databases before deleting a world.

The localization startup service grants the existing application account access to the restricted tw_world_ database namespace. Root credentials are used by that one-shot service, not passed to the application or scheduler.

Original release

Baseline: V0.6.2. Gameplay and existing selection/link styles are preserved.

The dead Forum menu item is replaced by a configurable community link (default label Discord). A blank URL hides the item. Configure it under world administration > startpage > Main page and team. Only complete HTTP/HTTPS URLs without embedded credentials are accepted.

The same form edits team members (one Name | Role per line), original source name, developer credit, and an optional source URL. Defaults credit Zapping Wars and Caique Portela (in-game: Felipe Medeiros), exactly as identified in the bundled app/include/config.php header. No original source URL has been assumed. The AI-assistance credit remains above the original-source attribution.

Settings are shared across worlds in the main database's tw_homepage_settings table, created automatically if absent. The table is retained in the database volume across rebuilds. Public reads use the configured main database; world administration uses TW_MAIN_DATABASE (default pkmhunters_imp). Admin authentication remains required, and saves require POST with a token derived from the authenticated admin cookie. Editable text is HTML-escaped when displayed.

Remove public sidebar Title and Rank and their unused ranks query. Lower the main-page wordmark by 16 pixels with increased top padding.

Validation: include resolution, template nesting, sidebar removal, and byte comparisons against V0.6.2 passed. A PHP build test covers default settings, save/reload, main-database targeting, invalid URL rejection, team parsing, and escaped Team template rendering. PHP/Docker and live browser checks are unavailable in the authoring workspace and must run on the host.

Upgrade:

Then open /tribalwars/wereld1/admin/index.php?screen=startpage and save the community URL and team details. Verify the public Home and Team pages and verify settings remain after rebuilding. Existing .env is preserved.

Original release

Baseline: V0.6.1. Presentation changes only.

Remove the black text/image selection declarations from all three game stylesheets. Apply browser/system Highlight and HighlightText selection colors across the game, landing/login, admin, forum, and support theme stylesheets. Image selection backgrounds are transparent.

Hyperlinks use bold brown (#804000, matching Spearman) in normal, visited, hover, active, and focus states. Red/glowing link overrides are superseded. Resource-header anchors retain their existing URLs and counters, with the inherited text-color override removed. Resource warning spans retain their warning styling.

Validation: all ten theme files checked for selection and link declarations, no original black selection rules remaining, and baseline byte comparisons limit changes to theme CSS, header styling, version markers, and release notes. No gameplay or database changes. Live browser rendering was not available in this workspace; hard-refresh after deployment to discard cached CSS.

Upgrade:

Press Ctrl+Shift+R after deployment. Check selected text/images and normal/visited/hovered links in the game, login, admin, forum, and support pages. The archive excludes .env and preserves earlier gameplay fixes.

Original release

Baseline: V0.6.0. Replace the hard-coded Research everything action with a configuration-driven bulk action. Premium is not required, consistent with the earlier request to remove the gate.

The existing instant-completion behavior is retained and explained beside the button. Technologies are processed in configured order, completing affordable levels up to their configured maximum. Completed technologies, unmet building requirements, disabled technologies, and unaffordable research are skipped. Actual per-level costs are deducted cumulatively; resources cannot be spent twice within the batch. A current research order blocks the bulk action.

Submission uses POST with the existing session security key. The server re-reads the village, checks ownership, and checks active research while holding MyISAM-compatible table locks; selected levels and costs are applied in one update. A successful action redirects back to the Smithy. Ordinary research and cancellation code are unchanged.

Validation: source scope comparison, existing research/cancellation byte comparison, template block nesting, and request checks passed. Added PHP build fixtures cover low-level buildings, real costs, exact/partial resources, completed research, capacity, enabled/disabled archers, ownership, active research, and unlock behavior. PHP/Docker are unavailable here; executable fixture checks run during the host build. Live database/browser behavior still needs host verification.

Upgrade:

No database schema changes. The archive preserves .env. Test the button without premium, in a low-level village, with only enough resources for part of the available research, and while an individual research order is active.

Original release

Baseline: V0.5.7, including the format_time/format_date coin-test hotfix.

Remove the extra outer table cell from market confirmation and use a readable 600px maximum table width within the existing game content area.

Calculate arrival and return from numeric travel seconds; label the one-way duration Travel Time.

Decode shipment hives data as wood;clay;iron instead of market-offer fields, including existing reports. Show all three quantities with resource icons.

Generate subjects as Village (Player) supplied Village (Player). Normalize existing shipment subjects on display in both report lists and details using current village/player names; missing entities have English fallbacks. No database migration is required.

Retain all previous build gates and the complete coin modifier repair. Add shipment/report fixture and template-render checks to the Docker build.

Validation completed here: baseline byte comparisons limiting changes to market/report files, coin test repair, build wiring, and version markers; HTML structure checks; modifier dependency checks; shell syntax; archive manifest integrity. PHP/Docker are unavailable in the authoring workspace, so PHP fixture execution and live database/browser verification remain host-side checks. Tests use database fixtures, not a live world.

Original release

Academy gold-coin minting update built directly from the approved V0.5.5 archive.

The Gold Coins section now has a Quantity field, Mint, and Mint maximum. Requirements are clearly labeled per coin. Mint maximum calculates affordability again on submission using the current database balances, rather than trusting the displayed maximum. An unaffordable requested quantity is rejected without partially minting it.

With the screenshot's 101,356 wood, 101,356 clay, and 372,009 iron, the maximum is 3 coins at 28,000 / 30,000 / 25,000 per coin. The batch costs 84,000 wood, 90,000 clay, and 75,000 iron, leaving 17,356 / 11,356 / 297,009 before further production.

The server requires POST and a valid session request key, checks village ownership and Academy availability, locks the legacy MyISAM tables before reading balances, and updates resources, coins, the next-noble threshold, and gold-medal progress in one guarded database statement. Locks are released after success or validation failure. Successful requests redirect back to the Academy.

The next-noble calculation handles batches spanning several thresholds. For example, 21 existing coins plus 24 newly minted coins gives 45 total and 10 until the next nobleman.

Two adjacent fixes are necessary for this feature: the existing recruitment form now closes before the mint form, and resource refresh adds wood production to the wood balance instead of incorrectly starting from the clay balance. The same one-line resource fix applies to both legacy copies of that routine. The insufficient-iron wait calculation also uses the configured iron price instead of an undefined variable.

Original release

Command display update built directly from V0.5.4. The V0.5.4 ranking fixes are retained.

Both outgoing and incoming command details now show these fields in order:

1. Source 2. Attacker 3. Destination 4. Defender 5. Arrival 6. Arrival In

Village links retain the full name, coordinates, and continent. Player links use the correct attacker and defender IDs. Ownerless destinations show “No player” without an invalid profile link. The attacker/defender identities refer to the original command participants, including when inspecting a returning command.

Fixed the village-label cache shared by command listings: the first and every subsequent command now retain the complete label, such as TT (500|499) K45. The cache is keyed by the village actually displayed and escapes names once. Return journeys use their origin village; cancelled commands retain their original target label. This covers the village overview, Rally Point, combined command overview, and incoming destination labels. Also corrected the combined overview's home-village label and separate player-name cache.

Existing command authorization and troop visibility are retained. Incoming opponents' unit counts and loot are not exposed. Own-command troop information and existing cancellation links remain available. Arrival countdowns on command details cannot become negative.

Original release

Ranking repair release built directly from the approved V0.5.3 archive, SHA-256 d3c80b7b1cdbe55fc29b03f6eaa3860e286a1aa4567dccd8968749bf6884da4f.

Ranking menus consistently show Battle Points (Player), Battle Points (Tribe), and Medals.

Players, Tribes, Medals, and all six battle-point lists use shared pagination. Requested pages are honored; invalid pages use page 1 and excessive page numbers clamp to the last page.

Links read <<< Up and Down >>>. Links only appear when another page exists and retain the village, ranking category, and battle tab. Medals no longer redirects to Players.

Ranks are calculated from the current ordered scores, starting at 1 and continuing across pages. Equal scores use ascending IDs for stable, distinct positions. Zero scores receive a valid position too.

Player ranking uses points, tribe ranking uses top-40 points, Medals uses total medal stages, and battle rankings use their selected attack/defense/total scores.

Corrected both copies of the tribe battle-rank refresh: they now read tribe records instead of player records. Player and tribe battle-rank refreshes have deterministic tie ordering.

Tribe battle-ranking names open tribe profiles. Medal names open the correct player profile using the player ID, not the medal record ID. Medal tribe names and achievement counts are populated correctly.

Zero-village players and zero-member/zero-village tribes no longer cause division-by-zero averages in ranking views.

Original release

Translation release built directly from the approved V0.5.2 archive (SHA-256 b8fd3ba53db0d48642869df80e6a172cb86840a033a4ed779764b5ca7d03ed30). V0.5.2 remains the behavioral baseline.

The audit inventoried the entire baseline and reviewed PHP, Smarty templates, JavaScript, CSS, language catalogs, SQL seeds, generated messages, and image text. Corrections cover player pages, recruitment/help text, reports and medals, movement and event logs, chat, forums, administration modules, validation messages, tooltips, and source comments.

Both player and administrator zapping_support pages are covered: ticket creation, replies, status labels, attachments, FAQ, authentication, validation, and language selection. English is the only selectable support language. Legacy PT/NL catalog paths remain compatible and contain English content.

New events are generated in English. The existing startup migration is extended for legacy system log phrases and additional medal titles, including URL-encoded logs. Player-authored messages, tickets, profiles, names, and custom content are not automatically translated.

Unused promotional screenshots containing German or Portuguese text were removed after checking source references. Their exact paths are listed in RETIRED-ASSETS.txt. No active map images or UI layouts were replaced.

Internal database column names, routes, identifiers, proper names, license attributions, and foreign-language migration search patterns remain intact for compatibility. These are not untranslated display text. Renaming database keys would be a separate refactor.

Original release

Canonical source for the next release: this complete archive. Do not rebuild from an older workspace tree.

Base: V0.5.1, SHA-256 c8101e099e022a8f5f94c55c0aa214e1ab5e6bf2a82dc0f367293089e5d2179e. Map source: V0.3.2, SHA-256 e49d40a560d01e3ecdeac049c46f2379835c51336cad80969de57bb97f626f55.

Restored V0.3.2 map, minimap, popup, marker templates, handlers and renderer together. Retained their drag/pin/synchronization behavior. Escaped marker CSS for Smarty and made its HEX pattern template-safe.

Fixed the shared recruitment function returning a string rather than an associative array. Individual buildings now receive configured units. Fixed remaining generated Paladin SELECT lists and the Academy owner-ID lookup.

Preserved mass recruitment. Restricted the individual recruiter cancellation branch to cancellation requests.

Added Friends to the Settings dropdown and Settings navigation to the Friends page.

Replaced the legacy image headers with TribalWarsClone text. Credited Atxsu / Ogky as owner, developer and staff. Updated the main footers.

Styled the separate administration login; preserved its existing authentication endpoint and fields.

Translated report generation and added migration of old report titles. Added missing Paladin language entries, configured item names/effects, corrected inventory links, and bounded the progress display.

Translated additional game and administration labels. Removed language caches and replaced the size-only cache check with direct English parsing.

Restored the marked_ally migration required by the V0.3.2 map.