Merged
Conversation
dellis1972
commented
Jun 4, 2025
1 task
Collaborator
|
@dellis1972 Did you want to access this via: or |
SimonDarksideJ
approved these changes
Jun 4, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add an Error page for the first coded MonoGame error. MGFX0001.
The error codes should be prefixed with the
TOOLor assembly which is being used. This will allow us to identify error areas easily.e.g
mgfx : MGFX
mgcb: MGCB
MonoGame : MG
Content Pipeline: MGCP
I chose a 4 digit code as that should give us enough room to add as many errors (or warnings) as we need.
In this case we want a page with details on WHAT the error is and then a
Solutionsection on how to fix it.That said we can also use redirects if need be.