mwest Wrote:Perhaps you don't understand the point I'm trying to make here? :chin:
Apparently not?
mwest Wrote:Yes, I understand that it was an "oversight." Yes, I understand that crap happens.
Excellent.
mwest Wrote:But why are you allowing it to continue? :chin: Rewarding the folks who are making unauthorized changes and not play testing the "modified" scenarios by allowing these altered scenarios to become "official" stock scenarios in the next release?
Official MCS scenarios have the ** infront of them. Did these?
mwest Wrote:What is to stop this practice from continuing?
Another QA.
mwest Wrote:What about other possible unauthorized "modifications" to existing scenarios?
Anyone is free to edit any scenario they choose.
Ultimately, they should have a scenario different file name as to not overwrite the original scenario, which according to the note above they were supposed to have. Why they ended up without the addition in the scenario file name, I am unsure of, but as I stated clearly above, I will ensure both versions are available.
As noted above, overwriting an original scenario is in poor form and would
NEVER BE INTENTIONALLY DONE.
mwest Wrote:Personally; as a scenario designer, I don't want individuals to have the ability to go into my designs, make modifications, and then upload the modified scenario into the database.
There's a flaw with allowing the scenario editor in the game then?
mwest Wrote:I don't believe that "allowing" two (or more? 
) modified versions of a scenario to exist in the Blitz Club scenario databases is the correct solution to this problem.
Yes, they should be allowed as they are two different scenarios that will play completely differently.
Modifying an existing scenario does not need the original scenario designers approval when it is
saved as a new scenario.
Modifying an existing scenario so it
overwrites the original would require scenario designer approval.
Jason Petho
Archived Forums
Help
Calendar
Member List
Search
){kind=link}
