Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About vexacion

  • Rank

Recent Profile Visitors

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

  1. http://wiki.secondlife.com/wiki/Linden_Lab_Official:Value_Added_Tax_(VAT)_Frequently_Asked_Questions#Linden_Lab_is_based_in_the_United_States._Why_are_you_charging_VAT_for_European_Residents.3F
  2. re: the USA -- Depending on how you set up your tax situation in the USA (S Corp, etc) the taxes are generally quite minimal. If you're doing it all personal, then it's all just ordinary income for federal (For the average person this is gonna run in the 15-20% range), and state is whatever rules the state has. I'm in an income tax free state, and am setup as an S Corp for all my SL things, so the overall tax burden is less than what you pay in just VAT and all the tools I use to create content (Software purchases, computer cost, etc) are all expenses and thus not income that is taxed. You can get around the VAT problem with your region if you'd rent it from someone else. You'll pay more in rent than the region cost, but you'll pay less when you factor in VAT. I rent out several regions to people for this very purpose (but I'm not a land baron, I only rent to friends!). I am very sympathetic to you in general here since I'm a content creator myself have paid well into 5 figures of "fees" to the lab and feel the lab isn't really thinking this change through, but just being blunt here, your personal tax burden (35% income rate, and also the VAT rate) really isn't the fault of the lab. I mean, all us creators pay taxes (Assuming everyone is doing the right thing and reporting/declaring your income), some are going to pay more than others. For VAT, they have to follow the rules of your country, so the path to changing it starts with the people who legislate where you live. Anything that impedes further content in Second Life from being created is a stupid move on the part of the lab.
  3. I have acquired a sim. Thanks to all who responded.
  4. I am still looking for a sim, preferably from someone who isn't going to sell me one for $300 with tier due the next day.
  5. Looking to buy a full sim, please message me in world.
  6. I've emailed you and messaged you in world a bit ago.
  7. Just ask owners to ban you from the skill gaming regions. Unlike the previous post mentioned, nearly every owner today will, so long as they are able to (eg: regions we own). The owners today are much more professional than when it was wild wild west days. I've gone ahead and proactively banned you from my two skill gaming regions.
  8. 1 on 1 mentoring is indeed hard, but if you need help feel free to message me in world i'm always happy to help fellow scripters (for free)
  9. Yes, she does have an agenda, Freya - you are perfectly correct. And as usual those with that agenda exist to tell others what they can and cannot do. Many women, myself included, love a lot of those fantasies the OP is railing against. So yes, Carlotta, Freya is correct: We're not interested in your silly senses of morality and out-dated shaming behavior, especially when you do it against other women. You don't get to choose how we enjoy SL. Go take your fight elsewhere, you'll find few on your side here.
  10. In my mind, I think these are some of the causes: 1. The exchanges selling off their excess L$ inventory. This would cause a massive influx of L$ into the market, easily eating up all the 257 buy orders wiping them out. I suspect this still isn't done and there is still a lot of L$ to sell. 2. The way Linden Lab has been treating the skill gaming program is absolutely atrocious and many operators whom in the past would keep large L$ balances on hand are now cutting their balances and holdings, putting many more sell orders in than in the past. 3. A lot of people, in general, have been losing confidence in the Lab (myself included, sadly) and simply do not invest anymore here. Between the false DMCA garbage a lot of creators deal with, to their treatment of the Skill Gaming program, to the lack of common decency many large land owners get.. people are quite frankly just tired of Linden Lab -- and Sansar just adds to that. Also, the lindex exchange as been borked for awhile, actually -- ever since they announced the end of the 3rd party exchanges. I watch the lindex a lot, and the 257 buy orders had been teetering between 5 million and 25million for months and the sell orders have been over a hundred million for awhile. It just finally gave way and looks like it's here to stay.
  11. I have found what I needed, thanks to all that responded to me for this
  12. Please contact me in world (vexacion resident), I have a lot of work for you! I can give you much more detail there. (If I don't reply to you immediately I will - sometimes RL creeps up)
  13. I know how all this went down. On 8/27 someone asked LL the question specifically about playing games "across sim borders", and they said in response on 8/28 "No, it's against the policy to do that". Except, there was no policy that said that. The next day, it mysteriously shows up in the FAQ as a "Note:" section, and SGR regions that were connected to non-SGR were suddenly converted back or forced to be moved. The facts point to one thing, that Linden Lab so haphazardly thought through the Skill Game Policy in general, that this is yet another instance where the were oblivious to one of the most obvious things concerning land ownership. They aren't "just now getting around to setting that rule". They had no idea to begin with until another resident asked the question. I'm quite sure had this person not asked the question, this would be no "policy", and would probably be an exploit that would have been used for awhile. It's good they did, it saves the headaches later, but it doesn't hide the facts. It's no different than the ridiculous part of the FAQ that discusses sharing ownership of a skill game with a group. Everyone who has ever created anything concerning debit permissions in SL knows that you cannot request debit permissions on a group owned object. The FAQ entry is completely extraneous to the skill gaming policy as a whole as the only objects it applies to are ones that don't pay out - and is another example that really just shows us that Linden Lab, with all due respect, are not completely clear how their own platform functions.
  14. What I would do is if you want the hud to dynamically change the object its controlling based on your distance, then you're really best using llSensorRepeat in your HUD, narrow it down as best you can for your objects (sadly, sensors are a little bit limited...), and track the closest one, and issue llRegionSayTo commands to that UUID. The critical part is narrowing down your Sensors to your specific objects. Say you repeated the sensor every 3 seconds, then as you walk around your objects, every 3 seconds if a different one is closer, just have a variable change in your script to the closest objects UUID.
  15. You should approach this in a slightly different manner. The main terminal should start with a blank list of fuses. Let all the fuses to the work. The main terminal doesn't really need to do anything but rez a fuse. It doesn't need to check in. Let the fuses do that. When a fuse is rezzed, have it blast out its prim uuid with a command (i.e. FUSE_REZZED|llGetKey()) which the main terminal can put in a list. When a fuse runs out, have it blast out its prim uuid with a command (i.e. FUSE_DIED|llGetKey()) which the main terminal can then remove from the list. You could, if you want, add a FUSE_STATUS command, that the main terminal can blast out, and the fuses that are active can response with their llGetKey(). You could put that in a timer, every few minutes or so, to make sure that lag doesn't muck anything up. Also, you dont have to include the key in the message, but I personally like to do it that way, you could just use the id from the listen when your fuse talks back. Also I'd recommend if you are the creator of the items, you add your extra security measures if needed (i.e. checking fuse creator, etc).
  • Create New...