a bot that can be told what to do

ukulele was in the client. the next thing i wanted was to see it actually run a bot — not a fixed one, but one i could script on the fly. if lua could reach through the fork and touch the world, a script could drive a bot the way lsl never let me

making the bot scriptable

i built a runner around the embedded runtime. it grew fast, in the loose way that kind of work does. a way to get a bot's own info. async coroutines, so a script could wait on the world without freezing. an objects library so it could rez and move things. each piece was just me wanting the next thing to be scriptable

by the end of that first run it was a proper bot surface. it could teleport, wear attachments, handle marketplaces and notecards and web calls. none of it planned up front. i kept finding one more thing a bot should be able to do, and adding it

what it was for

the point was control. a script that can ask a bot to do something and wait for the answer — that's not a fixed puppet anymore, it's a thing you can direct. the same impulse as the terminal cli and the in-world chat: put the control where the work is, and let a script hold it

能 is ability. the bot had gone from a scripted puppet to something i could tell what to do. and the more it could do, the more i wanted it to do