Jump to content

sprightlysprite

Resident
  • Posts

    4
  • Joined

  • Last visited

Reputation

6 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Bump. Still open to hiring event organizers and performers.
  2. Hello! I'm open to hiring people to run various events with a family or community theme and realistic vibe. Maybe you're a performer, or maybe you're more of an organizer. Your event would take place in a modern-day community, where a number of residents play SL as parents and children. Some things I'd be interested in are: Live music at various locations around town (perhaps in the park, at the roller skating rink, or at the county fair) Story nights at the campfire Scouts or some other kids club A community theater production Gaming tournaments - chess, checkers, scrabble, air hockey, bingo, you name it Recreational sports leagues Field day. I have some old scripts for a sack race, 3-legged race, tug of war, etc.) DJ events are a last resort; SL doesn't need its three thousandth DJ performing today just because. But if you've got a unique theme or spin, talk to me. The sky is the limit. Bring your own ideas! Details: Yes, I'm really paying you. This is not just an "RP job". I'm looking for people with experience running and promoting successful events. Can be one-off events or something recurring. Anyone participating would need to have an avatar and profile that's appropriate for a setting including child avatars. Contact me in-world via IM or notecard to discuss more.
  3. I am having trouble with JSON parsing in LSL, which seems to not actually be correct. While most of the syntax is right, LSL's JSON parser fails on unicode escape sequences, such as \u1234, which is parses as "u1234" instead of a unicode character. Is there a way around this? I managed this server-side workaround (Python/Flask) for now: from flask.json.provider import DefaultJSONProvider DefaultJSONProvider.ensure_ascii = False which prevents most unicode escape sequences, though it seems very likely this doesn't fix every case. But is this really the only way? We don't even have a working JSON parser in LSL?
  4. default { touch_start(integer n) { llRequestPermissions(llDetectedKey(0), PERMISSION_TRIGGER_ANIMATION); } run_time_permissions(key id, integer perms) { if (perms & PERMISSION_TRIGGER_ANIMATION) { integer n = llGetInventoryNumber(INVENTORY_ANIMATION); integer i = (integer) llFrand(n); llStartAnimation(id, llGetInventoryName(INVENTORY_ANIMATION, i); } } }
×
×
  • Create New...