I was wanting to know if it is up to the scenario designer to fix such an obvious inaccuracy in a scenario or if the devs can try and fix it in an update.
I just thought I would bring this up in case its possible for devs to fix and they don't know or have forgotten about it.
I've read an older post where someone seen this bug and i'll follow the help tips that he received for the editor (I've never used the editor before!)
