Glossary

868 practical terms for game development, porting, remakes, remasters, and cross-platform release work.

Legacy game delivery32-bit architecture during an Unreal Engine migration32-bit architecture covers older technology, source recovery, and the practical limits of bringing a legacy title back. It shapes the technical choices made when a project moves from a legacy codebase or engine into Unreal Engine.Legacy game delivery32-bit architecture for a cross-platform release32-bit architecture covers older technology, source recovery, and the practical limits of bringing a legacy title back. It keeps the release consistent across console, PC, handheld, and mobile targets.Legacy game delivery32-bit architecture for game porting32-bit architecture covers older technology, source recovery, and the practical limits of bringing a legacy title back. It covers the work needed to move an existing game to another platform without breaking the intended player experience.Legacy game delivery32-bit architecture in a remake or remaster32-bit architecture covers older technology, source recovery, and the practical limits of bringing a legacy title back. It helps a team update an older title while keeping the parts players remember intact.Legacy game delivery64-bit migration during an Unreal Engine migration64-bit migration covers older technology, source recovery, and the practical limits of bringing a legacy title back. It shapes the technical choices made when a project moves from a legacy codebase or engine into Unreal Engine.Legacy game delivery64-bit migration for a cross-platform release64-bit migration covers older technology, source recovery, and the practical limits of bringing a legacy title back. It keeps the release consistent across console, PC, handheld, and mobile targets.Legacy game delivery64-bit migration for game porting64-bit migration covers older technology, source recovery, and the practical limits of bringing a legacy title back. It covers the work needed to move an existing game to another platform without breaking the intended player experience.Legacy game delivery64-bit migration in a remake or remaster64-bit migration covers older technology, source recovery, and the practical limits of bringing a legacy title back. It helps a team update an older title while keeping the parts players remember intact.ProductionAcceptance criteria during an Unreal Engine migrationAcceptance criteria covers scope, planning, ownership, and the commercial boundaries of a game project. It shapes the technical choices made when a project moves from a legacy codebase or engine into Unreal Engine.ProductionAcceptance criteria for a cross-platform releaseAcceptance criteria covers scope, planning, ownership, and the commercial boundaries of a game project. It keeps the release consistent across console, PC, handheld, and mobile targets.ProductionAcceptance criteria for game portingAcceptance criteria covers scope, planning, ownership, and the commercial boundaries of a game project. It covers the work needed to move an existing game to another platform without breaking the intended player experience.ProductionAcceptance criteria in a remake or remasterAcceptance criteria covers scope, planning, ownership, and the commercial boundaries of a game project. It helps a team update an older title while keeping the parts players remember intact.CertificationAccessibility compliance during an Unreal Engine migrationAccessibility compliance covers first-party requirements, submission evidence, and release approval. It shapes the technical choices made when a project moves from a legacy codebase or engine into Unreal Engine.CertificationAccessibility compliance for a cross-platform releaseAccessibility compliance covers first-party requirements, submission evidence, and release approval. It keeps the release consistent across console, PC, handheld, and mobile targets.CertificationAccessibility compliance for game portingAccessibility compliance covers first-party requirements, submission evidence, and release approval. It covers the work needed to move an existing game to another platform without breaking the intended player experience.CertificationAccessibility compliance in a remake or remasterAccessibility compliance covers first-party requirements, submission evidence, and release approval. It helps a team update an older title while keeping the parts players remember intact.Input and accessibilityAccessibility preset during an Unreal Engine migrationAccessibility preset covers controls, readability, and player options across devices. It shapes the technical choices made when a project moves from a legacy codebase or engine into Unreal Engine.Input and accessibilityAccessibility preset for a cross-platform releaseAccessibility preset covers controls, readability, and player options across devices. It keeps the release consistent across console, PC, handheld, and mobile targets.Input and accessibilityAccessibility preset for game portingAccessibility preset covers controls, readability, and player options across devices. It covers the work needed to move an existing game to another platform without breaking the intended player experience.Input and accessibilityAccessibility preset in a remake or remasterAccessibility preset covers controls, readability, and player options across devices. It helps a team update an older title while keeping the parts players remember intact.CertificationAchievement compliance during an Unreal Engine migrationAchievement compliance covers first-party requirements, submission evidence, and release approval. It shapes the technical choices made when a project moves from a legacy codebase or engine into Unreal Engine.CertificationAchievement compliance for a cross-platform releaseAchievement compliance covers first-party requirements, submission evidence, and release approval. It keeps the release consistent across console, PC, handheld, and mobile targets.CertificationAchievement compliance for game portingAchievement compliance covers first-party requirements, submission evidence, and release approval. It covers the work needed to move an existing game to another platform without breaking the intended player experience.CertificationAchievement compliance in a remake or remasterAchievement compliance covers first-party requirements, submission evidence, and release approval. It helps a team update an older title while keeping the parts players remember intact.

Tell us your engine, platforms, and target date.

Free technical assessment. First estimate in 3 business days. No commitment.

Krystian Mlodziejewski

Krystian Mlodziejewski

Business & Relations Director

What’s needed?
contact@lynxbytegames.com

Trusted by studios and publishers