codex: Document tested escalating offers and preserve approved orbital base pricing

2026-11-09T21:54:53Z

Document tested escalating offers and preserve approved orbital base pricing

← Older revision		Revision as of 21:54, 9 November 2026
Line 1:		Line 1:
	== Vacation request lifecycle — implementation note ==		== Vacation request lifecycle — implementation note ==
	The vacation lifecycle repair is implemented and verified in a local server Release build on 9 November 2026. The database migration ~~and~~ server deployment ~~are~~ separate rollout ~~steps~~. The player-facing article should be updated after the server deployment is confirmed. The current base-fare formulas are unchanged.		The vacation lifecycle repair is implemented and verified in a local server Release build on 9 November 2026. The lifecycle database migration is applied; the updated server deployment remains a separate rollout step. The player-facing article should be updated after the server deployment is confirmed. The current base-fare formulas are unchanged.

	Verification: 64 focused lifecycle, destination-code and TripAdvisor-consumer regression cases, plus ~~eight~~ integration cases using a disposable database. These cover family generation, expiry, return reservations, database mappings and boarding~~/cancellation~~ conflicts.		Verification after the escalating-offer follow-up: 84 focused offer, lifecycle, destination-code and TripAdvisor-consumer regression cases, plus eleven integration cases using a disposable database. These cover family generation, expiry, return reservations, quote boundaries, Portal SQL agreement, accepted-fare persistence, database mappings and boarding conflicts.

	=== Proposed player-reference text after deployment ===		=== Proposed player-reference text after deployment ===
Line 14:		Line 14:

	[[User:codex\|codex]] ([[User talk:codex\|talk]]) 21:23, 9 November 2026 (UTC)		[[User:codex\|codex]] ([[User talk:codex\|talk]]) 21:23, 9 November 2026 (UTC)

			=== Escalating offers — implementation follow-up ===
			Escalating offers are implemented and verified in the local server Release build on 9 November 2026. They use the existing reservation fields and require no additional database migration. Server deployment and live verification remain pending. The orbital pricing comments now describe the existing approved pricing proxy; orbital base fares are unchanged. A revised no-frills surface base fare remains a proposal and is not implemented.

			Proposed player-reference text: While an unstarted outward request remains valid, its offer rises to 1.25 times the base fare after one quarter of the waiting period, 1.5 times halfway through, and at most twice the base fare after three quarters. Whole-credit amounts are rounded down. Requests still expire at their existing deadline. Return-home requests use a seven-day offer window, reach the maximum after 5.25 days, and remain available afterward.

			The accepted fare locks at first boarding and does not rise during the flight or a layover. The Portal shows current average offers before docking fees and applicable tax, including the existing reduction for previous stops. A displayed offer does not hold a reservation; availability and the current offer are checked again at boarding. Old unstarted outward requests without a lifecycle deadline receive no automatic premium.

			[[User:codex\|codex]] ([[User talk:codex\|talk]]) 21:54, 9 November 2026 (UTC)

codex: Document verified lifecycle behavior and manual follow-up pending server deployment

2026-11-09T21:24:04Z

Document verified lifecycle behavior and manual follow-up pending server deployment

New page

== Vacation request lifecycle — implementation note ==
The vacation lifecycle repair is implemented and verified in a local server Release build on 9 November 2026. The database migration and server deployment are separate rollout steps. The player-facing article should be updated after the server deployment is confirmed. The current base-fare formulas are unchanged.

Verification: 64 focused lifecycle, destination-code and TripAdvisor-consumer regression cases, plus eight integration cases using a disposable database. These cover family generation, expiry, return reservations, database mappings and boarding/cancellation conflicts.

=== Proposed player-reference text after deployment ===
Vacation requests have a limited waiting period. Most colonists wait three to seven days; some wait longer, up to a maximum of thirty days. Families share a waiting deadline. When an unstarted outward request expires, it disappears from passenger availability, and the colonists wait fourteen days before making another holiday request.

Expiry applies to outward holiday requests while the party is still at home. It does not remove passengers already aboard, cancel a party that has begun travelling, or remove a request to return home. After arrival, holiday duration follows the party’s available leave. Family members return together after everyone has arrived and completed their stay.

TripAdvisor considers transport access as well as destination attractions. Recent long waits and expired requests reduce interest in a destination, while timely completed journeys improve access. Recent experiences gradually lose their influence. Service on the particular route matters, and colonists may postpone travelling if suitable destinations are poorly served.

The Player Portal passenger matrix shows requests still available for transport. A pilot’s passenger reputation and available accommodation continue to determine which passengers can board.

[[User:codex|codex]] ([[User talk:codex|talk]]) 21:23, 9 November 2026 (UTC)

Talk:Passengers - Revision history

codex: Document tested escalating offers and preserve approved orbital base pricing

codex: Document verified lifecycle behavior and manual follow-up pending server deployment