|
Walter Pinion
Registered User
Join date: 15 Feb 2007
Posts: 15
|
03-27-2007 08:06
After one of the recent updates, and I'm not sure which, as until recently the parcels to either side of my home were vacant, the effect of scripted objects, such as my security system, now reach outside my parcel.
This was brought to my attention after I logged in to find a total of 49 IM's had been sent to me stating that my new neighbor 'has been ejected trying to enter your home'.
As I stated, I'm not 100% sure, but I think it was the recent server-side update as right after that, sometimes when I log in I find my tintable windows on a different setting than I'd left them. Last night I discovered that another new neighbor, 2 parcels over, has bought the same model house I bought (therefore the same tintable windows).
I haven't caught him online to ask him to try changing his window tint, but after our testing of the security system last night, I'll bet his controller is talking to my windows too.
I saw the person I bought my security system online, and sent him a TP.
I turned my system on, and put one of those glowing green 10m yardsticks out from the system. This crossed about 5m into my neighbor's property.
I then had him approach the yardstick - sure enough, it gave the message and tried to boot him. On someone else's property.
I asked the support group for my security system, and noone had heard of this before now.
Anyone else noticed this?
Edit: I'd also like to say that I looked into this before I purchased the system, and was assured it couldn't reach outside my property. I've had it for over a month, and only had a couple of ejections before the other night. Glad my neighbor is such a good sport.
|
|
Sys Slade
Registered User
Join date: 15 Feb 2007
Posts: 626
|
03-27-2007 08:40
From: Walter Pinion I then had him approach the yardstick - sure enough, it gave the message and tried to boot him. On someone else's property. So presumably it's not actually having any effect outside your land or he would have been booted. Possibly the script doesn't use an llOverMyLand check after scanning, or llOverMyLand is broken. Either way, that would result in it trying to boot people who aren't actually on your land.
|
|
Walter Pinion
Registered User
Join date: 15 Feb 2007
Posts: 15
|
03-27-2007 08:51
Yes, it did indeed try to boot him off my neighbor's land - IIRC he said he cancelled the teleport request.
I don't know where my neighbor's home location is, but if he had set it within the radius of the security system, that would have resulted in a teleport loop, and could have been the cause of my ~49 'I booted an intruder' messages.
|
|
Sys Slade
Registered User
Join date: 15 Feb 2007
Posts: 626
|
03-27-2007 09:11
I would do some testing but I'm reluctant to start booting all my neighbours. I'm blocked in on all sides 
|
|
Walter Pinion
Registered User
Join date: 15 Feb 2007
Posts: 15
|
03-27-2007 10:34
I just logged in, and my windows were not on the tint I left them on. I pulled the camera back two lots over, to my neighbor's house, he was not home, but his windows were no longer tinted either (they were last night).
I switched mine to black, and pulled the camera back over his lot.
He's still not home, and now his are black too.
Edit: Just spoke with the author of my security system, and he says LL is aware of that particular problem, and that the window-tint thing is unrelated, the controller is shouting on the same channel for both houses, which are ~100m apart, so although they appear to be related problems, appearances can be deceiving.
|