Disclaimer: At the time this is written, the ASP builder is still in development, so any issues stated here are only meant for helping with that.
Hey guys! I just wanted to make a new thread showing some glitches I've found in the ASP program, hoping they might help with development and could be ironed out. If this topic gets out of hand (people start bashing on the builder, complaining about it for no reason, etc.), I give any moderator permission to delete it in an effort to preserve order.
Information on the priority scale:
The priority system is on a scale from 1-10, with 10 being highest priority.
Anything either level 5 or higher is impossible to manually fix and breaks the builder until a refresh.
Lower level priorities are either hard to get to, or very minor.
Any level 10 priority is BOTH easy to get to and breaks the builder, but also must be difficult to fix (more than a refresh required)
First ___ (part, saber, blade, etc.) means the original ___, which is pre-built when the builder launches.
Now that that's out of the way, let's get to it!
Glitch (issue): 1, Priority:1
I just notice none of the switch sections have any switches, only holes. In this picture, you can see the blade plug through one of the holes.
Possible Solution: Add an option for switches, or edit the switch sections to already have switches (because I assume switches will be standard on any saber with light)
Glitch: 2, Priority: 6
After adding a coupler and creating a saber staff and adding both blades, removing the first blade makes it impossible to add it again. Trying to add a new blade mounts it on the second emitter, facing the direction of the first. It also makes it impossible to light the new blade and results in a noticeable length loss.
Possible solution: unknown
Glitch: 3, Priority: 8
After creating a staff and removing the parts of the original half, any added parts are mounted to the second emitter, not to the body.
Possible solution: Most likely fixed with glitch 2.
These are all I've found for now.