Ethics of editing buggy BoE scenarios.

[Balladeer]

So, now that password checking has been removed from the editor, the question that comes to mind is: When is it Ok to edit a scenario and when should one be left alone?

 

I don't want to step on anyones toes or stray from what they were trying to make. There are two scenarios that I have always wanted 'fixed'. Kistar's Quest and, um, forget the name but one of Frahhamn's scenarios. Their stories intrigued me despite all the bugs and I think they are worth being told without the bugs.

[Lilith]

I'd say that as long as it's only fixing things that are unambiguously bugs and the edited version is clearly marked as an edited version, it should be okay. Of course, it's better to contact the designer first where possible.

[Slawbug]

Emphasis on CLEARLY MARKED AS AN EDITED VERSION. That goes for the description, file name, and readme, and it goes double for any site you upload it to.

[Balladeer]

Hm.. I changed one node's mismarked SDF in Parallel Dimensia so it would work. Changing the readme seems so invasive for such a tiny fix. I can see marking a scenario where text or major nodework has to be altered but... I have reservations for smaller fixes.

[Slawbug]

The problem is that then there is no way to identify which version has the bug and which doesn't except by opening up the scenario files and looking. If nothing else, I would increment the version number by 0.0.1 in a prominent place (or assign a new 1.0.1 number).

[Randomizer]

Fixing a bug so future users can better enjoy a scenario is a good idea. As long as it's identified it shouldn't make a difference.

 

You don't want too many versions floating out there so it might help to have a topic where people can post which scenarios are being revised.