[Opensim-users] Thank you Mr Ubit.

[Han Held]

Just pulled the latest version from github. It's still there in bin/excuses

On 2/7/2019 12:56 PM, Teravus Ovares wrote:
> A side note, at least when I was working on OpenSimulator there /was/ a
> file named excuses.   It was used as a script to pick random things for bot
> avatar to say.    I suspect it may still be in the distribution.
>
> On Sun, Feb 3, 2019 at 6:03 AM Luisillo Contepomi <
> luisillocontepomi at gmail.com> wrote:
>
>> Yes Ethan,
>> But all we, users of opensim are advanced users.  Is not a easy
>> technology and for this i am thank to the developers all this years.
>>
>> This is not a big problem or bug because is easy verify the file If
>> all textures are "c228d1cf-4b5d-4ba8-84f4-899a0796aa97" file must go
>> to trash because is unusuable.
>>
>> You order the command when you see your avatar perfectly load. and
>> then you see perfect the npc by much time (weeks ) meanwhile you do
>> not clean your viewer cache. No alerts or errors when is doing the
>> xml. Is a perfect and unusable xml file for the future use.
>> But I understand is not a bug. It is as it is and I accept it. It is a
>> finished matter.
>> I remember when all prims must be ghost or you can not enter in a
>> house!, in a few years it will be solved and while it can be verified
>> manually or by script.
>> Please forget the matter, it's not worth being angry at something so
>> insignificant and easily resolved
>> --
>> Luisillo Contepomi
>>
>> El dom., 3 feb. 2019 a las 14:39, Ethan Gardener
>> (<eekee57 at fastmail.fm>) escribió:
>>>> "The avatar that is copied must be in region and fully baked.
>>> *sigh* I wasn't privy to the communication which caused the upset here,
>> but that one line is worthy of comment.  One consistent, long-standing
>> 'feature' of these SL-related virtual worlds is that you cannot be sure of
>> how you appear to others; you cannot be sure your avatar is fully baked.
>> If code is generating something incorrectly based on something the user
>> cannot easily or reasonably verify, isn't that a bug?  I understand it may
>> be impractical to fix the bug, and I understand some users may be all too
>> pushy, (it's because they're frustrated,) but the course of wisdom is very
>> much *not* for the devs to respond in a way that makes them seem right all
>> along.  A small apology for the difficulty would be appropriate, perhaps
>> along with an honest excuse that the bug is hard to fix.  (Often true!)  It
>> would also be sensible to place a warning into documentation for the code,
>> although that is harder with all the independently-produced tutorials.
>> Perhaps, if it's a console comm
>>>   and, it could respond with a brief warning to clear your cache to check
>> the results.
>>> _______________________________________________
>>> Opensim-users mailing list
>>> Opensim-users at opensimulator.org
>>> http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users
>> _______________________________________________
>> Opensim-users mailing list
>> Opensim-users at opensimulator.org
>> http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users
>>
> _______________________________________________
> Opensim-users mailing list
> Opensim-users at opensimulator.org
> http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-users