[citation][nom]ko888[/nom]If you don't have access to the code how would you know if an oddity is a bug or if it's a feature?[/citation]
[citation][nom]holyknight1121[/nom]How are you supposed to know if a bug/glitch/runtime error is a problem or whether it was intended to be a new feature?[/citation]
"This program has closed unexpectedly."
Bug, or cool new feature?
I've been in a fair number of betas. Generally, you can tell something's supposed to be a bug vs a feature. ("Hey, I activated that power and I can walk through walls - look at this cool, yet unfinished at this point, architecture!" versus "Hey, I did nothing and can walk through walls at that point, nothing's back here, look, I'm falling to my death in a complete void!" for instance.)
Generally, if you pay attention to notes/the beta forum, you'll see features listed they want you to test.
And, in general, if you're not sure if it's a bug or a feature, either (A) ask or (B) report it anyway. Because it could very well be a new feature that isn't supposed to do that.