Friday, October 23, 2009

Catching Up...

Well... here we are again. As of late I've had myself a fight with a cold so have not been feeling to up to snuf or really enthused about getting around to programming anything substantial. After some time and a surprise visit from my father my cold is on it's way out and I'm back at it.

With that comes news of a major project I've started; it's been a concept for a long time now collaborated with my friend Dirk, owner of Stonehaven Island, as a special feature for his sim. With that I announce C.A.G.E. my massive project.

Why is it massive? Because it's not a cage, it's a game! Full with in world and and off world server to store tons of data like scores, awards, achievements, ranks etc; a HUD to track room by room games between friends or strangers and a unique gun that follows the rules of the game.

Now then. Details details, the ever important information that may just get someone excited.
  • The game will allow multiple "rooms"
  • Rooms can be password locked or public access
  • Guns will only fire on people in the same room as you (no shooting people in another room or strangers not playing the game
  • Room "Wardens" can change multiple settings of a room including maximum players, password and score limit; they can also eject people
  • Wardens are shown as green names in the room display on HUDs
  • Designated "Safe Zones" prevent all guns in all rooms to cease function
  • Shooting someone cages them (and deactivates their gun in case they escape the cage those poor sports!) for 1 minute and grants a point to you
  • You will be able to join, leave and create rooms straight from the HUD; no need to go to the central Server to do so
  • Guns can be gotten from the HUD or Server, HUD is gotten from the Server
  • Web enabled Update
  • Sever based Admins (shown as red in HUDs room display) can configure multiple Server settings including things like a ban list, safe zones, max number of rooms; as well as enter as change room passwords and eject people from rooms (including Wardens)
  • Multiple sort orders for room display, the HUD is able to sort the display by Score or Alphabetical in both ascending (highest to lowest score, a to z) and descending (lowest to highest score, z to a)
  • Special HUD for those using the GreenLife Emerald Viewer taking advantage of the llTextBox() function (not yet supported by SLV cause LL is lazy, once it's supported just use the emerald HUD instead of the SLV HUD)
  • Easy and simple HUD layout, navigation through the pages of players in a room are done by HUD buttons not llDialog buttons (5 people per page, unlimited pages)
  • Unique Room IDs so that two rooms can be named the same thing while the server, HUD and gun can tell the difference
  • Use the HUD to search through open Rooms, no dialog or chatting (unless it's password locked) just surf through the list like you do players (Next/Previous buttons on the HUD) and select the one you want to join
That's about all I have so far, I'll update when once I have more and of course down the line as beta comes along for open testing.

As always not all listed features are guaranteed to be in game, some may get dropped or altered as the programming moves on. If you wish to beta test with me please drop me an IM in world in a little bit (once I hopefully have something to test) and we'll see what we can set up.

Have fun out there.

Wednesday, October 14, 2009

Peevish

Here's what I don't get. As a content creator I make things and more specifically as a BDSM content creator I make things restrictive. With the help of RLV of course.

The thing is, for each new feature Marine adds to RLV or I add to my products (and others to their products of course) there seems to be someone else making a counter product.

Raise your hand if you have an item that listens to channel 1. It'd take me all day to count those that are honest and admitted to it. Why so many? What is the point in us making something like a gag and Marine making RLV if we're (I'm guilty of it to in the past I admit) just going to cheat around it? Why buy a product, wear it, let someone (or do it yourself) lock it to block us from chatting or whatever and then just bypass it with something?

Block local, people go to IMs, block IMs and they use notecards, block cards.. then I've seen one girl use group notices to talk. Come on! Don't wear a gag if you're that desperate to talk still, don't wear a gag if you have to use another item to allow IMs to all your friends, or allow teleporting or whatever just because you don't want to be restricted.

Why use RLV or play in BDSM sims to begin with then? It's obvious that you're interested more in cheating out and being free then you are being kidnapped and captured so don't start to begin with and stay free.

Now don't confuse this with something like I don't care for safety. Safety is a big concern of mine and I put Safewords in my products (or equivalent functions) for just such a case, including (if blocked) IMs always being open to the person who locked. But safety isn't IMing all your friends while gagged or teleporting out of a cage cause you're bored or removing a locked item because you're tired of it. Safety is getting free when someone has been irresponsible with your stuff and ran away etc.

Basically, if you don't want to be restricted, don't buy/wear/use items that can restrict you. Sit there and chat with all your friends instead of wasting my time and the time of all us creators by making it look like there's a market for people interested in something like a gag just so that you can cheat out of its restrictions.

I'm sure I'm not the only one a bit ticked off at others making light of our work. Many of us put a lot of effort into making SL enjoyable for the BDSM crowd and frankly it's a kick in the teeth that we try so hard just so that someone can cheat and act as if our stuff is just jewelry instead of bondage equipment.

Thursday, October 8, 2009

Baffled

Two posts in one night, wee.

I was looking at some scripts (written by others) after my own crusade into typos and I'm just dumbfounded by what people do. Now, I know I'm a talented scripter I've had many people tell me that but that doesn't change how it amazes me that people are doing things with 150+ lines in a stand alone script that I'm doing with a 30 line function.

I mean really, is that the standard or did I just find a really poor quality script that it has to take a stand alone script to change some variables and lists and do some rlv?

I guess it could come down to style or something but I've seen a few products out there that just have so many scripts in them and it makes me wonder why they're all needed. I'm all for being modular I've got some of that myself; have myself a plug and go RLV script etc but that's a bunch of functions that sort and store large amounts of rlv commands along with auto correcting spelling mistakes and swapping y/rem/n/add where needed (allows me to say @detach=n, add it to the list, then say @detach=y and remove the n from the list) so it isn't something simple that you can just put in a generic control script.

*shurgs* I don't know. To each their own I guess.

Blah

Scripting sure can piss me off at times, bewilder me too. Here I am trying to work on an inter prim communication that I know damn well should work and it wasn't!! Grr.

In trying to update my Simplicity Cuffs to match my Chastity Belt I changed the prim work of them, starting from scratch and then just plop the scripts in and go right? Wrong!

The two elbow cuffs just refused to talk, they'd listen and respond to commands but they wouldn't talk which meant that the main script couldn't get their keys in order to properly chain when doing poses. What was more confusing and annoying was that the wrists cuffs were talking fine and the scripts were a direct copy/paste to the elbows!! Why then weren't they working?!

So I sat here and tested and ranted and stumped every scritpter out there with this weird problem. The channel is within limit, the listen is open, nothing is being said before the channel is made, the channel is the same on all four cuffs, the commands are all right, the wording is perfect, I reset the scripts 50 times, copied and pasted again, I recompiled, I rerezzed, I logged in and out, danced on my head and nothing worked!

Time and time again they'd listen to commands, responding by trying to chain together but not having the proper keys the chain just hung there. The wrists worked they chained as they should on all the poses they should and the elbows sat there refusing to take part in the party. Even my listener that I set up wasn't hearing them talk.

Of course I realize now if I'd had my head on straight when I made the listener in frustration that I heard them talk before I added the name filter on it (to block chatter on the channel to just my cuffs) but 20/20 hindsight.

So anyway, I was stumped every scripter I could talk to was stumped. And then I saw it. The damn name was wrong! Gah, how can I be so stupid? There was an extra t in the "Simplicity" on both the elbow cuffs that I missed. I remove it, all works. I bang head against wall; stop scripting for the night.

The power and frustration of a little typo. *sighs*

Tuesday, October 6, 2009

Ops...

Seems there was a bit of a slip up with permissions on the Anthemion Pony Bridle that caught a few people.

Now it's nothing serious or that require updates or anything just contact me, Lylani Bellic, in world and we'll fix it. The *Feedback notecard found in the Bridle's inventory that is used to set spoken feedback messages is unintentionally set to NoMod; kinda makes it hard to change it to what you want like that. /me looks sheepish

Anyway, the stores have been update with the proper permissions so purchasing one here after should do alright, if you did buy one that has NoMod notecard just let me know and I'll send you one with proper permissions.

Thursday, October 1, 2009

Do a little dance...

Just letting you peoples know I'm still around, settled into my new house and populating it with all sorts of little toys and misc boxes of doom.

Work continues on my projects (small delays here and there programing stuff for my house and being locked up mmm) and one that I'm sure a few people have been waiting a long time for is getting close.

The Chastity Belt that I've been so cruelly teasing people with is actually not vaporware. I know, it's shocking maybe I should have advised a seat before springing the news. Anyway, it's down to its last few functions and many many tests after only a month (today being October 1st and V2.0 of the belt was started on September 1st) of work. I'm pretty pleased with it so far, its far smoother and less laggy then its previous version and the accompanied Chastity Bra has had a total prim rework along with a few features of its own.

With it will be a couple features that may not work right away:

1) Vibrators. I need to get in touch with Xcite again and get their partnership scripts again in order to get this operational. If this doesn't happen before I feel the belt should be released it will be released in an update asap.

2) Cuffs. A new plugin feature (not found in V 1.0 of the scripts) that requires me to update my Simplicity Cuffs and write a plugin for RR. This function wont need any new cuffs and I will release an API so that you can write a plugin for your own cuffs if you can/want to. It will use animations stored in the belt for unique poses and the plugin to the cuffs is there to lock/take keys so that your cuffs are "locked to the belt". This may be a little bit in coming as I have yet to look over the API Marine released for her cuffs and I have some plans to update my Simplicity Cuffs with more then just support for the belt.

Hopefully it doesn't take to much longer to code, I predict at least a couple more weeks though to finish and do a lot of testing.