As I was trying to say, rel-less ports with the ASL Tool's codes would be useful. Mostly to prevent crashes, but also with these kinds of problems.
That said, though, I think it makes sense to set a placeholder for a stage being problematic if it's necessary to use a half-buggy code. Did/does P:M have issues with that, too?
No issues in Project M. Maybe they're doing something special to work around it?
Anyway, here's what I think I'll do:
STGCUSTOM01 -> Castle Siege static stages
STGCUSTOM25 -> Online Practice Stage and variants
STGCUSTOM26 -> Target Smash!! 1, 2, 4, 5
I'd like to use STGCUSTOMs here now that I set them up to have 3 alts each - that way people can easily replace the stages themselves. I decided to skip Target Smash 3 because the launch pad doesn't show up when you use it outside target smash mode.
Post Merge: June 11, 2016, 02:38:13 PM
Lylat Cruise has the same problem, but I don't have a good replacement version of it. Should I take it out?
If I did, I'd probably move the online practice stage (STGCUSTOM25, icon 60) to that spot on the SSS, and add an STGCUSTOM27 (reuse Lylat's icon 15?) in the second-to-last row on page 1. Either way, the STGCUSTOMs are a bit out of order. I suppose I'd replace it with ALM5252's Lylat Cruise omega stage (which doesn't look the same as in SSB4 Wii U, but that's all right.)
Either way, I'm also going to make a version of the pack with the ASRL code taken out (and Castle Siege and Lylat Cruise back in) when I'm done.