* Script Legacy - This is *my* main problem which makes me unlike most members of the Guild. Its very important that as SL grows they don't suddenly make a thousands of sold scripts suddenly no longer function. Resulting in days of swapping old for new replacements. When SL becomes hard work less content will be made. (Yes I know about self updating scripts, but thats not the point)
Not unlike me. Random, undocumented changes waste my time, break my stuff and test my patience.
There isn't anything we can do to fix that. We can ameliorate transitions with updaters etc, sometimes changes do need to be made to existing functionality, but we need clear and detailed changelogs on EVERY change to how LSL behaves, not the jokes that we have at the moment. When the best documentation available is a user-run wiki you know you're in trouble.
There isn't anything we can do to fix that. We can ameliorate transitions with updaters etc, sometimes changes do need to be made to existing functionality, but we need clear and detailed changelogs on EVERY change to how LSL behaves, not the jokes that we have at the moment. When the best documentation available is a user-run wiki you know you're in trouble.
What we need is a warning so we can prepare. Over time there is going to be a lot of sophisticated scripts out there doing things that are importiant to their owners. Say a 1 month notice of changes to functionality so we can swap over new scripts in a less chaotic, rushed, after-the-fact manner. Better yet don't change old functions at all make replacements and depreciate the old functions in X months time.
, that fixes a flaw introduced in Second Life 1.9.0(15).