Unreal Tournament 99

Portage 0.1.2

Portage natif d'Unreal Tournament 99 sur iPhone, iPad et Mac.

Portage natif d'Unreal Tournament 99 sur iPhone, iPad et Mac.

Jeux contenus

1999 Windows Linux Macintosh

Unreal Tournament

Tir à la première personne multijoueur, pensé pour l’arène : capture de drapeau et domination, bots réglables et armes au double tir.

Architecture

iOS iOS

Aucun binaire n’est distribué ici. Le code source est disponible : ce logiciel s’obtient en le compilant, ou par installation hors App Store.

Téléchargement et liens

Historique des versions

0.1.3
  • La taille initiale de l’interface suit désormais celle de la fenêtre hôte, corrigant un affichage erroné sur écrans externes ou fenêtres redimensionnées.
  • Les contrôles tactiles respectent désormais le paramètre Auto-hide Touch Controls with Controller en temps réel, avec un indicateur visuel dans le menu des paramètres.
  • La compilation utilise PadMint et nécessite une réinstallation sur l’existant sans désinstallation préalable, avec la même identité de signature.
  • Les tests automatisés (make test) valident les géométries d’affichage (paysage, portrait, écrans externes) et les configurations tactiles (basculade avec/sans contrôleur).
  • Seuls le fichier de configuration UTP-v0.1.3-padmint.json et le SHA256SUMS sont publiés, sans données de jeu ni application préemballée.

UTP 0.1.3

UTP now starts the engine at the size of the window that hosts the game. Earlier builds sized Unreal's startup viewport from the iPhone or iPad's main screen, so a game shown in a smaller or resized window, or on an external display such as a TV, could start at the wrong size. Later rotation, resizing and display moves already followed the window and are unchanged.

Touch controls now follow the Auto-hide Touch Controls with Controller setting while a controller is connected. Earlier builds hid touch when a controller connected and ignored later changes to that setting until the controller disconnected. Turning the setting off now shows touch immediately, and turning it on hides touch immediately. Show Touch Controls in the ••• menu keeps the controls visible with a controller connected by turning auto-hide off; turn it back on to hide them again. The settings panel's touch switch shows whether the controls are actually visible, and its row is now named Auto-hide with controller.

Rebuild with PadMint and install over the existing app using the same signing identity. Do not uninstall first.

Validation

  • make test passes, including new display-geometry checks (landscape, portrait-measured, 1x external-display-sized, unmeasured windows and invalid scale) and touch-configuration checks (default on, controller connected and disconnected, Show overriding a connected controller, persistence across reload).
  • App metadata is 0.1.3/build 6.
  • Physical TV and controller acceptance is pending: these changes have not yet been exercised on an external display or with a physical controller.

Only UTP-v0.1.3-padmint.json and SHA256SUMS are published. PadMint builds the app locally; no app or game data is included.

Release checks: a clean current-main PadMint build (scripts/player-check.sh with the release commit, Apple Python 3.9.6 and an empty PadMint folder) passed before tagging in 145.6 seconds; the package reports 0.1.3/build 6. Check after publishing is still to run.

0.1.2
  • Correction majeure du système de rollback interrompu : préservation des dossiers et fichiers de récupération au lieu de suppression.
  • Ajout d’un suivi des éléments manquants pour distinguer les fichiers absents initialement des sauvegardes perdues.
  • Affichage d’un message "Repair game data" : utilisation obligatoire de "Get Game Data" ou "Import Files" pour remplacer les données corrompues.
  • Récompilation avec PadMint et installation directe sur l’appli existante sans désinstallation préalable.
  • Maintien des fichiers de récupération antérieurs après une réparation réussie (les pertes antérieures à la mise à jour restent irréversibles).

UTP 0.1.2

An interrupted rollback from UTP 0.1.0 can leave a restored folder whose backup has already been consumed. Recovery now preserves that folder and the remaining recovery files instead of deleting it. New imports record which items existed before replacement, so recovery can distinguish an originally absent item from a missing backup.

If Repair game data appears, use Get Game Data or Import Files to install a verified replacement. A failed repair keeps the previous recovery state and remains retryable. If a content-only import lacks the required runtime support, UTP stays in setup and directs you to Get Game Data. Normal play, Safe Mode and direct launch all require ready data.

Rebuild with PadMint and install over the existing app using the same signing identity. Do not uninstall first. Earlier recovery files are retained after a successful repair; files already lost before this update cannot be reconstructed.

Validation

  • The legacy consumed-backup fixture fails at runtime against the actual 0.1.1 transaction implementation.
  • Native regressions cover the legacy upgrade, failed replacement preparation, failed repair and retry, interrupted cleanup, successful repair, incomplete recorded backups, complete older journals and originally absent items.
  • App metadata is 0.1.2/build 5. Package and source checks do not establish new physical-device, gameplay or Files-provider acceptance.

Only UTP-v0.1.2-padmint.json and SHA256SUMS are published. PadMint builds the app locally; no app or game data is included.

Completed release checks: full native suite and exact-head public-safety CI passed. Clean current-main PadMint builds passed before tagging (101.9 seconds) and through the published release (94.5 seconds), using Apple Python 3.9 and empty PadMint folders. Both actual packages report 0.1.2/build 5. Public recipe/checksum and source audits passed, and anonymous release downloads match the audited assets.

0.1.1
  • Correction majeure du risque de perte de données lors d’une récupération interrompue ou échouée d’un import de données de jeu.
  • Rétention intégrale du backup jusqu’à restauration complète de chaque élément avant enregistrement de la fin.
  • Réessai de récupération ne supprime plus le contenu déjà restauré avant l’interruption.
  • Nécessité de reconstruire avec PadMint et d’utiliser la même identité de signature pour éviter les échecs de retry.
  • Validation réussie sur le test suite complet, incluant un build propre avec Python 3.9 d’Apple et un dossier PadMint vide.

Superseded by UTP 0.1.2. Follow-up review found that 0.1.1 did not fully handle a rollback already interrupted in 0.1.0. Version 0.1.2 preserves that older recovery state and provides a retryable repair path. Rebuild with PadMint to receive the correction; keep the existing app data and backups.

UTP 0.1.1 fixes a data-loss path when recovery of an interrupted game-data import is itself interrupted or fails. Recovery now retains the full backup until every item has been restored, then records completion before cleanup. Retrying recovery no longer deletes content that was already restored.

Rebuild UTP with PadMint and install the update using the same signing identity to retain its container. This prevents the demonstrated retry failure; it cannot reconstruct data already lost by an earlier interrupted rollback. It does not change file-picker selection policy.

Validation: the regression fails on the old recovery code and passes with the fix; the full test suite passes. A clean current-main PadMint build with Apple's Python 3.9 and an empty PadMint folder passed both before publication and through the normal published-release route afterward; both generated apps report 0.1.1/build 4. Release recipe and checksum passed the private artifact gate. Physical-device and Files-provider selection acceptance are separate.

Only the PadMint recipe and SHA256SUMS are published. No app or game data is included.

Réagir sur le forum

Une question, un retour d’expérience ? Ouvrez la discussion sur le forum.

Réagir sur le forum