Jump to content

Lucia Nightfire

Resident
 View Profile  See their activity

  • Posts

    3,471

  • Joined

 Content Type 

Posts posted by Lucia Nightfire

    If LL prevented you from saving scripts in LSO format(non-Mono), would it impact you?

    in LSL Scripting

    Posted

    In the last Server meeting, LL hinted they had interest in sunsetting the ability to save LSO(non-Mono) scripts.

    They would leave the interpreter running so existing LSO(non-Mono) scripts could still function, but you will only be able to save scripts as Mono going forward after the change.

    There would be no Mono flag in the editor and/or no functionality unchecking Mono and saving.

    How would this impact any of you?

     

    • Thanks 1

    "Linkset Data" is coming.

    in LSL Scripting

    Posted · Edited by Lucia Nightfire

    1 hour ago, Rider Linden said:

    (*this is why we never change functions in production.)

    Except when Oz ordered llSetPrimMediaParams() & llSetLinkMedia() changed to add url schema enforcement. 😉

    • Sad 1

    LinksetData fuction testing

    in LSL Scripting

    Posted · Edited by Lucia Nightfire

    10 hours ago, Xiija said:

    @Wulfie Reanimator 

    default
{
    state_entry()
    {      
    }
    touch_start(integer total_number)
    {   integer dataAmt = llLinksetDataAvailable(); //  not defined within scope
        llOwnerSay("Data available: " + (string)dataAmt );
    }
}

     

    You must not be in one of the regions that support linkset data mentioned here:

    Your script compiled for me in the region, Mauve.

    Using The Greatest Dane mesh doesnt sork

    in Your Avatar

    Posted

    3 hours ago, Slade Demina said:

    Hello,

     

    I am having problems getting a clean greatest dane avatar. The human body remains covering the dog body and I cannot get rid of it

    The Greatest Dane folder contains the "Full Body Alpha" alpha mask wearable.

    Use this to make your system avatar invisible.

    Welcome to the world of mesh avatars.

    • Like 1

    "Linkset Data" is coming.

    in LSL Scripting

    Posted

    4 hours ago, Kyrah Abattoir said:

    I'm still not sure on having delete protection on key value pairs, If my scripts are trying to clear datastore space by removing crud that it can't identify, it shouldn't require wiping its own records in the process.

    I think the argument is too one-sided.

    Would you, in-turn, want other creator scripts you chose to leave intact in your objects or were unaware that existed in your objects to also delete your own protected keys as well?

    There are two scenarios where this will typically be an issue:

    1. Other-creator objects already containing other-creator scripts being linked together and said scripts being maintained for the sake of functionality/convenience or because the object owner lacks the skill/knowledge to achieve the same functionality with their own scripts.
    2. Users directly placing other-creator, no-mod scripts in their content for the sake of functionality/convenience or because the object owner lacks the skill/knowledge to achieve the same functionality with their own scripts.

    Without including delete protection, the protected keys feature is incomplete and would only lead to an increase in no-mod content, in-turn, making protected keys redundant.

    There is no 100% best way to deal with it. The nuclear option of wiping all data is a "hopeful" deterrent to allow for good actors to work together in the same environment.

    • Like 1
    • Thanks 1

    Black Dragon spinning uncontrollably

    in Viewers

    Posted

    On 10/18/2022 at 12:30 PM, NiranV Dean said:

    You are spinning uncontrollably because you have a controller plugged in. PS4/Xbox360/XBoxOne Controllers all tend to report very tiny values while the joysticks are in their idle position, commonly called stickdrift. Stickdrift should be very minimal and in the latest versions of Black Dragon this should not happen anymore due to the increased deadzones. If its still happen make sure that your controller joysticks are indeed idle (touch them and move them manually into a centered position if you have to). If that doesn't help go into Preferences - Camera - Flycam Configuration and adjust the Pitch/Yaw deadzones. Alternatively you could also simply turn off avatar movement for controllers, or select None in the Controller selection dropdown, or simply unplug your controller(s).

    Is controller movement on by default in BD?

    "Linkset Data" is coming.

    in LSL Scripting

    Posted · Edited by Lucia Nightfire

    1 hour ago, Kyrah Abattoir said:

    Then what's the point of a protected delete function?

    This allows a mod product's end-user to add their own links/scripts/functionality with their own storage with their own passwords and keep existing scripts "happy" while also preventing existing scripts from accidentally/intentionally breaking things without having to go "all-in" and reset data.

    Granted, an application's protocol could have still been set up to wipe all data naturally/occasionally and without being nefarious or to satisfy a previous owner's control.

    It's like multiple people living in a dorm, respecting each other's space and property and not kicking each other or their property out. Coexistence.

    It's also like the "Good fences make good neighbors." proverb.

    • Like 1

    "Linkset Data" is coming.

    in LSL Scripting

    Posted · Edited by Lucia Nightfire

    2 hours ago, Kadah Coba said:

    Except that whole "crashes the region on key doesn't exist" thing. :P

    That "should" have been fixed Sunday.

    I wasn't able to crash Mauve again with my testing.

    I encourage everyone to try, though, heh.

    • Thanks 1

    "Linkset Data" is coming.

    in LSL Scripting

    Posted

    1 hour ago, Jym Nova said:

    I agree with this 100%, however; let's say I want an object to be modify for something like resizing "without" a resizer script or resizer functions plugged in to the existing script. 

    Why should "my" script suffer at the expense of someone experimenting with scripts and wiping protected data "my" script needs to effectively operate in the object?

    I'd have no objections to including a standalone script in the same package as the product to use something like: "llLinksetDataResetProtected(string pass);" (if its implemented) if the end-user decides they don't want my script in it, so they can recover the full 64KiB of LSD.

    I'd also have no objections to including a copy that doesn't have a script in it all, depending on what it is.

    I'm sorry Jym, but llLinksetDataReset() is intentionally designed to remove all data, protected or not.

    It was decided that in a modify environment, the end-user will always have the right to remove all data if they wish and not be burdened with the will/control of the previous owner.

    I can only suggest that you use no-mod permissions to prevent this.

    • Like 3

    "Linkset Data" is coming.

    in LSL Scripting

    Posted

    1 hour ago, Tapple Gao said:

    I haven't seen it mentioned in the thread already. But, if I have a lot of keys, script reset seems like it would DEFINITELY overflow the 64-buffered event queue with the linkset_data event. I plan to have scripts that sets around 200 keys during a single script time slice, either on reset, or on finishing a notecard read. I ran into this problem with update-notification linked messages already, until I reworked them to support batches of updates in one message.

    This would lead to some desync issues when another script needed to react to a value change, but, the queue started dropping events. It could be alleviated with 1 or 2 functions, and 1 new action type to linkset_data:

    • llLinksetDataBatchBegin()
    • llLinksetDataBatchEnd()

    or

    • llLinksetDataBatch(integer bool)

    this would start/stop supressing linkset_data events. Turning batch mode off would trigger linkset_data(LINKSETDATA_BATCH_UPDATE) in all scripts, that signals them to rescan what keys they must react to

    For safety, batch mode should maybe end automatically if it's still active when a script finishes it's time slice. Ending batch mode when it's already over should probably be a no-op

    FWIW, usage of the linkset_data() event is not required.

    "Linkset Data" is coming.

    in LSL Scripting

    Posted · Edited by Lucia Nightfire

    2 hours ago, Rider Linden said:

    Writing a zero length string as the value actually deletes the key from the store.  

    llLinksetDataWrite(key, "");

    is equivalent to 

    llLinksetDataDelete(key);

     

    What I get for not having verbose on for linkset_data() when doing that test.

    1 hour ago, Qie Niangao said:

    There's up to 64KB of the stuff so let's not dump it to chat. Maybe a web/javascript app, with search and edit functions? (which itself could be a script; in fact, not sure exactly why it would be better not being a script.)

    I'd bet it has to do with wanting to do everything via viewer UI, similar to how it's been requested to update other prim properties via viewer UI such as particles, hover text and animated textures.

    • Thanks 1

    "Linkset Data" is coming.

    in LSL Scripting

    Posted

    2 hours ago, Love Zhaoying said:

    Awesome!

    Does the dropdown list in the Script Editor of LSL functions, with the "parameter hints" also get updated to include the new functions and/or any parameter changes?

    IDK which dropdown list you're refering to.

    Your viewer will reference the keyword file downloaded for the list shown in Help > Keyword Help and for any data in function/constant/event hover-over popups.

×
×
  • Create New...