You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gamemakin LLC and its product Linter makes no effort to check for legal compliance for your project on your behalf. We are not lawyers and do not have that capability and can not offer legal advice. That said, we vehemently recommend not breaking the law.
⭕ Sometimes a graceful no-logic fail is acceptable. See #3.4.5
70
Custom Blueprint nodes contain "Static" prefix
❌ If this refers to a node's name, this makes zero sense, and Epic doesn't follow this in any form. If this refers to the fact that a function might be static, this also makes no sense and this rule should be re-written. After several months I have not been able to get clarification from the marketplace team as to what is intended here.
71
Custom Blueprint nodes from plugins categorized with plugin name as preface
⭕ Style guide only applies this to static functions in a plugin. See #3.3.5
72
Functions, variables, and events use names that reflect intended purposes
⭕ This reads like a 1:1 relationship between SoundWaves and SoundCues, when its very common to have one SoundCue reference many SoundWaves. Not sure of Marketplace Team's intention.
78
Audio is clean and not bitcrunched
⭕ Currently a subjective check.
79
Audio sample rate is appropriate (44100 Hz or 22050 Hz for Game Assets)
⭕ Style guide currently does not have rules for audio format.
80
Sound cues and wavs in separate "Cue" and "Wave" folders
❌ This style guide actively fights against the folder structure desired. See #2
Characters
Gamemakin LLC's Style Guide does not have character specfics as characters are quite diverse. Epic forces characters to adhere to the Epic Skeleton for marketplace assets even when a character should have a different skeleton due to things like having facial animations, having articulation and movements not supported by Epic's skeleton, having wildly different proportions to the point where using even re-targeted Epic animations don't make sense, and other factors.
When a humanoid does warrant being rigged to the Epic skeleton, we agree with every review item in this list. This checklist however is not fully compatible because we don't believe line item 83 should be enforced as strictly as it currently is.
Line
Review Check Item
Compatibility Notes
82
Pack contains Characters
✅💚
83
Humanoid assets rigged to Epic skeleton
⭕ See section note above.
84
Bones are not renamed
⭕✅ If using Epic skeleton, agree completely. See Section note.
85
Character is not weighted to any IK joints
⭕✅ If using Epic skeleton, agree completely. See Section note.
86
Epic Skeleton IK Joints are in skeleton hierarchy
⭕✅ If using Epic skeleton, agree completely. See Section note.
87
Joint orientations remain intact
⭕✅ If using Epic skeleton, agree completely. See Section note.
88
Skeleton is not scaled
⭕✅ If using Epic skeleton, agree completely. See Section note.
Animation
Line
Review Check Item
Compatibility Notes
90
Pack contains Animations
✅💚
91
All animations imported from individual .FBX files
❌ Does not make sense. What about animations baked from physical simulations within UE4? What about single frame poses extracted from animations used for reference and additive posing within UE4? What about .FBX's with multiple takes in standard mo-cap pipelines using Motion Builder?
92
Animations are clean, consistent, and function as intended
✅ All assets, regardless of type, should not be broken.
Weapons
Line
Review Check Item
Compatibility Notes
94
Pack contains Weapons
✅💚
95
Weapons are scaled to epic skeleton and appear relatively scaled as intended when imported into a new project
Particle systems meant to be viewed at multiple distances have correct LODs
⭕ Currently a subjective check.
101
Effects optimized for their intended use
⭕ Currently a subjective check.
Plugins
Line
Review Check Item
Compatibility Notes
103
Pack utilizes Plugins
✅
104
Required plugins in project are available on UE Marketplace
⭕ Marketplace specific rule, style guide does not apply.
105
Unnecessary/Unused plugins are disabled
⭕ Blueprint only projects can sometimes be forced to need C++ compiling when disabling unused built-in plugins. Until this is fixed, can not recommend fully disabling every unused plugin.
Notes From Reviewer
Line
Review Check Item
Compatibility Notes
107
Changes have previously been requested
⭕ Specific to Marketplace Review Process, style guide does not apply.
108
Requested Changes Have Been Implemented
⭕ Specific to Marketplace Review Process, style guide does not apply.