Issue Checklist
What is your suggestion, and why should it be implemented?
Basically with how ModPath works there's no way to be specific with what lowerend mod it's assigned to, especially if the system is gonna be like Psych Engine's.
// current way, not specific enough
Paths.image('mod:icons/ui/dad');
// the idea, makes it easier for the game to remember what lowerend mod the asset is from
Paths.image('[mod id here]:icons/ui/dad');
Note: This would only work for lowerend mods since only 1 upperend is allowed at a time. "But what about specifying the fallback and current upperend?" The "main" and "solo" references already exist, so there's no need for path type specification when specifying mod id.
Issue Checklist
What is your suggestion, and why should it be implemented?
Basically with how ModPath works there's no way to be specific with what lowerend mod it's assigned to, especially if the system is gonna be like Psych Engine's.
Note: This would only work for lowerend mods since only 1 upperend is allowed at a time. "But what about specifying the fallback and current upperend?" The "main" and "solo" references already exist, so there's no need for path type specification when specifying mod id.