Skip to content

Add Asset Security and Protection Guidance to Packaging Games Guide #161

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

AristurtleDev
Copy link
Contributor

Description

This pull request addresses community feedback regarding security and sensitivity of assets once packaged by adding comprehensive guidance to the packaging games documentation.

Resolves: Issue #115

Changes Made

Added a new "Asset Security and Protection" section to "Chapter 25: Packaging Your Game for Distribution" that provides practical guidance on:

  • XNB Asset Protection: Explains how MonoGame's built-in XNB compression provides sufficient protection for most use cases
  • Code Obfuscation Considerations: Details the performance costs and trade-offs of obfuscation
  • Modern Security Reality: Discusses the practical limitations of client-side protection in today's digital landscape
  • Practical Recommendations: Provides actionable advice for developers on security approaches

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feedback] Update Packaging guides with information/guidance on security
1 participant