Well after a lot of hair pulling and testing and failed attempts to get anything useful from support, I have solved the issue on my own. It seems the file size indicator is dead wrong, because anything over 97.75% results in you being unable to publish. I have reported this as a bug, but be warned that 100% is false, keep it to about 97%.
What really bites is this is to small to have a good 5 mission arc with lots of interesting mission goals and story. Granted, it's the creation of a custom enemy group that takes up a TON of space, so if you use stock things you're ok and have plenty of space. So much for originality, apparently they don't actually want you to make custom groups in a story, you can either do a story with a stock group, or a custom group and make a single mission, which pretty much kills the intent of a custom group in my opinion.
My one published arc is 99.51%, so I dunno what the trouble it's giving you with 97.75%, but it seems to be rather isolated in occurrence.
As far as the Custom critters goes, while I am somewhat disappointed in just how much space individual mobs take up, I can understand it...
There are likely already hundreds, possibly even thousands of custom critter groups, if they didn't set some kind of limitation on them the servers simply couldn't handle it. Custom Groups use a lot more memory storage than Stock groups, because they tend to be a LOT more detailed in appearance.
My arc uses 2 custom groups (and a stock enemy group) of which one custom group has 3 minions, 2lieutenants, 1 boss, and 1 Archvillain, the other has 2 minions, 1 lieutenant and 1 boss, plus 1 Archvillain.
@Oathbound & @Oathbound Too
[ QUOTE ]
Well after a lot of hair pulling and testing and failed attempts to get anything useful from support, I have solved the issue on my own. It seems the file size indicator is dead wrong, because anything over 97.75% results in you being unable to publish. I have reported this as a bug, but be warned that 100% is false, keep it to about 97%.
[/ QUOTE ]
There's definitely something wonky. I had my story at 99.4% and was unable to publish. I then ran a double-space removal script over the storyarc file, getting it down to 99.2%, and could publish.
Later I went back and added some extra words here and there... and lo and behold, my story is now 99.5% and still publishable.
I think there is some field in there somewhere that is "silently" overflowing, and that's what's preventing you from publishing. I have no good ideas on how to find said field if you're in this situation, though. This caused me about two days of grief.
And for a while things were cold,
They were scared down in their holes
The forest that once was green
Was colored black by those killing machines
[ QUOTE ]
My arc uses 2 custom groups (and a stock enemy group) of which one custom group has 3 minions, 2lieutenants, 1 boss, and 1 Archvillain, the other has 2 minions, 1 lieutenant and 1 boss, plus 1 Archvillain.
[/ QUOTE ]
Do you only have one or two missions? You have more custom mobs in those groups than I do, and my custom group takes up a good 65% of my file space. With a lot of tweaking I think I managed to not cut to much story, but the description and back story had to be trimmed a lot. I really don't know what they expect to come out of this system when a decent souvenir takes 5% of your file space, that's just crazy.
I've also found in messing with settings that less text and more mission parameters allow you to get closer to the 100% mark without being denied Publish. I've also been looking at the actual file size of the mission and it's always over 100kb no mater if I can publish or not. There are definitely glitches in the system.
I spent days making and testing a 5 mission arc and now I can not publish it. On the "my local stories" tab when I look at the arc the Publish and Test buttons are grey (disabled) so they do nothing. I can edit the mission and there are no errors reported. From the editor I can "save and test" and test the mission, so it makes even less sense for that button to be disabled on the other screen. What's the problem here? Has anyone encountered this? I put in a bug report but since it's a local story they can't look at the issue. I made a quick test mission and that shows as publishable for what that's worth.