Category:LSL Group - Revision history

Myggen Resident: /* Group Membership */ text about premium plus

2022-09-20T01:06:24Z

Group Membership: text about premium plus

← Older revision		Revision as of 18:06, 19 September 2022
Line 14:		Line 14:
	===Group Membership===		===Group Membership===

	A user with a Basic account my join a limit of 42 groups (updated January 2011), and a user with a Premium account my join up to 60 groups ~~(updated~~ May 2015~~). The original limit was 10;~~ this was ~~raised~~ to ~~15 in SL 1~~.~~4.0, and again~~ in ~~SL 1.12.0 to 25. Calls for~~ the ~~maximum~~ to ~~be increased even further began almost immediately after it was raised~~ to 25.		A user with a Basic account my join a limit of 42 groups (updated January 2011), and a user with a Premium account could join up to 60 groups from May 2015 until in 2022 when this number was increased to 70 groups. A Premium Plus account was introduced in 2022 which allows the account to join up to 140 groups.

	If ~~a user with a Premium account is a member~~ of more than ~~42 groups and downgrades to a Basic~~ account, no memberships are lost, but they are not able to join any new groups until they ~~belong to fewer than 42 groups~~.		The original limit was 10; this was raised to 15 in SL 1.4.0, and again in SL 1.12.0 to 25. Calls for the maximum to be increased even further began almost immediately after it was raised to 25.

			If users lower their subscription level and are members of more groups than the new account type supports, no memberships are lost, but they are not able to join any new groups until they get below the group limit for their account.

	===Joining a Group===		===Joining a Group===

Diriel Novo: /* Scripting and Groups */

2016-01-23T01:21:14Z

Scripting and Groups

← Older revision		Revision as of 18:21, 22 January 2016
Line 47:		Line 47:
	#<span id="sag_1"></span>Identifying someone's group(s) through scripting		#<span id="sag_1"></span>Identifying someone's group(s) through scripting
	#:There is as of yet (July 2008) no way of telling what groups someone belongs to, or of knowing what is the name of the group that they currently have active. The best you can do is compare the group they have active with the group that an object is set to, and get an answer as to whether they match or not. You do this using either [[llDetectedGroup]]() or [[llSameGroup]](). (To be clear: all you get back is an answer as to whether there is a match between the object's group, and the person's active group, or not. You get no other information.)		#:There is as of yet (July 2008) no way of telling what groups someone belongs to, or of knowing what is the name of the group that they currently have active. The best you can do is compare the group they have active with the group that an object is set to, and get an answer as to whether they match or not. You do this using either [[llDetectedGroup]]() or [[llSameGroup]](). (To be clear: all you get back is an answer as to whether there is a match between the object's group, and the person's active group, or not. You get no other information.)
	#::This is no longer entirely correct. Using [[llGetObjectDetails]]([[llGetKey]](), OBJECT_GROUP) on an attachment will return the key of the avatar's currently active group. However, there is still no obvious way to retrieve a list of groups an avatar belongs to.		#::This is no longer entirely correct. Using [[llGetObjectDetails]]([[llGetKey]](), [OBJECT_GROUP]) on an attachment will return the key of the avatar's currently active group. However, there is still no obvious way to retrieve a list of groups an avatar belongs to.
	#You cannot use [[llGiveMoney]] to give money to a group;		#You cannot use [[llGiveMoney]] to give money to a group;
	#If your scripts draw on functions that can only work if same entity (person or group) owns both the scripted object and the land it is rezzed on, then you need to either release the object with transfer privileges so that it can be deeded to group and therefore work on group-owned land, or warn the customer in advance of purchase that the item won't work on group-owned land;		#If your scripts draw on functions that can only work if same entity (person or group) owns both the scripted object and the land it is rezzed on, then you need to either release the object with transfer privileges so that it can be deeded to group and therefore work on group-owned land, or warn the customer in advance of purchase that the item won't work on group-owned land;

Diriel Novo: /* Scripting and Groups */

2016-01-23T00:32:13Z

Scripting and Groups

← Older revision		Revision as of 17:32, 22 January 2016
Line 48:		Line 48:
	#:There is as of yet (July 2008) no way of telling what groups someone belongs to, or of knowing what is the name of the group that they currently have active. The best you can do is compare the group they have active with the group that an object is set to, and get an answer as to whether they match or not. You do this using either [[llDetectedGroup]]() or [[llSameGroup]](). (To be clear: all you get back is an answer as to whether there is a match between the object's group, and the person's active group, or not. You get no other information.)		#:There is as of yet (July 2008) no way of telling what groups someone belongs to, or of knowing what is the name of the group that they currently have active. The best you can do is compare the group they have active with the group that an object is set to, and get an answer as to whether they match or not. You do this using either [[llDetectedGroup]]() or [[llSameGroup]](). (To be clear: all you get back is an answer as to whether there is a match between the object's group, and the person's active group, or not. You get no other information.)
	#::This is no longer entirely correct. Using [[llGetObjectDetails]]([[llGetKey]](), OBJECT_GROUP) on an attachment will return the key of the avatar's currently active group. However, there is still no obvious way to retrieve a list of groups an avatar belongs to.		#::This is no longer entirely correct. Using [[llGetObjectDetails]]([[llGetKey]](), OBJECT_GROUP) on an attachment will return the key of the avatar's currently active group. However, there is still no obvious way to retrieve a list of groups an avatar belongs to.

	#You cannot use [[llGiveMoney]] to give money to a group;		#You cannot use [[llGiveMoney]] to give money to a group;
	#If your scripts draw on functions that can only work if same entity (person or group) owns both the scripted object and the land it is rezzed on, then you need to either release the object with transfer privileges so that it can be deeded to group and therefore work on group-owned land, or warn the customer in advance of purchase that the item won't work on group-owned land;		#If your scripts draw on functions that can only work if same entity (person or group) owns both the scripted object and the land it is rezzed on, then you need to either release the object with transfer privileges so that it can be deeded to group and therefore work on group-owned land, or warn the customer in advance of purchase that the item won't work on group-owned land;

Diriel Novo: /* Scripting and Groups */

2016-01-23T00:31:00Z

Scripting and Groups

← Older revision		Revision as of 17:31, 22 January 2016
Line 47:		Line 47:
	#<span id="sag_1"></span>Identifying someone's group(s) through scripting		#<span id="sag_1"></span>Identifying someone's group(s) through scripting
	#:There is as of yet (July 2008) no way of telling what groups someone belongs to, or of knowing what is the name of the group that they currently have active. The best you can do is compare the group they have active with the group that an object is set to, and get an answer as to whether they match or not. You do this using either [[llDetectedGroup]]() or [[llSameGroup]](). (To be clear: all you get back is an answer as to whether there is a match between the object's group, and the person's active group, or not. You get no other information.)		#:There is as of yet (July 2008) no way of telling what groups someone belongs to, or of knowing what is the name of the group that they currently have active. The best you can do is compare the group they have active with the group that an object is set to, and get an answer as to whether they match or not. You do this using either [[llDetectedGroup]]() or [[llSameGroup]](). (To be clear: all you get back is an answer as to whether there is a match between the object's group, and the person's active group, or not. You get no other information.)
			#::This is no longer entirely correct. Using [[llGetObjectDetails]]([[llGetKey]](), OBJECT_GROUP) on an attachment will return the key of the avatar's currently active group. However, there is still no obvious way to retrieve a list of groups an avatar belongs to.

	#You cannot use [[llGiveMoney]] to give money to a group;		#You cannot use [[llGiveMoney]] to give money to a group;
	#If your scripts draw on functions that can only work if same entity (person or group) owns both the scripted object and the land it is rezzed on, then you need to either release the object with transfer privileges so that it can be deeded to group and therefore work on group-owned land, or warn the customer in advance of purchase that the item won't work on group-owned land;		#If your scripts draw on functions that can only work if same entity (person or group) owns both the scripted object and the land it is rezzed on, then you need to either release the object with transfer privileges so that it can be deeded to group and therefore work on group-owned land, or warn the customer in advance of purchase that the item won't work on group-owned land;

Jeremy Linden: /* Group Membership */

2015-05-29T17:48:28Z

Group Membership

← Older revision		Revision as of 10:48, 29 May 2015
Line 14:		Line 14:
	===Group Membership===		===Group Membership===

	~~There is~~ a limit of 42 groups ~~that~~ a ~~person may belong~~ to (updated ~~January 2011~~.) The original limit was 10; this was raised to 15 in SL 1.4.0, and again in SL 1.12.0 to 25. Calls for the maximum to be increased even further began almost immediately after it was raised to 25.		A user with a Basic account my join a limit of 42 groups (updated January 2011), and a user with a Premium account my join up to 60 groups (updated May 2015). The original limit was 10; this was raised to 15 in SL 1.4.0, and again in SL 1.12.0 to 25. Calls for the maximum to be increased even further began almost immediately after it was raised to 25.

			If a user with a Premium account is a member of more than 42 groups and downgrades to a Basic account, no memberships are lost, but they are not able to join any new groups until they belong to fewer than 42 groups.

	===Joining a Group===		===Joining a Group===

ObviousAltIsObvious Resident: language tags to

2015-01-25T21:20:41Z

language tags to <source>

← Older revision		Revision as of 14:20, 25 January 2015
Line 51:		Line 51:
	#You can use the [[World API]] in order to obtain group information by UUID key.		#You can use the [[World API]] in order to obtain group information by UUID key.
	#There is no LSL function that returns a group's name as a string. However, if you know a group key (as a result of calling [[llGetObjectDetails]] with [[OBJECT_GROUP]], or calling [[llGetParcelDetails]] with [[PARCEL_DETAILS_GROUP]]), you can display the group's name in the viewer and chat history using the [[Viewer URI Name Space]]:		#There is no LSL function that returns a group's name as a string. However, if you know a group key (as a result of calling [[llGetObjectDetails]] with [[OBJECT_GROUP]], or calling [[llGetParcelDetails]] with [[PARCEL_DETAILS_GROUP]]), you can display the group's name in the viewer and chat history using the [[Viewer URI Name Space]]:
	<~~lsl~~>llOwnerSay("secondlife:///app/group/" + (string)group_key + "/about");</~~lsl~~>		<source lang="lsl2">llOwnerSay("secondlife:///app/group/" + (string)group_key + "/about");</source>

	===Footnotes===		===Footnotes===
	{{Footnotes}}		{{Footnotes}}

JetZep Zabelin: /* Scripting and Groups */ Viewer URI Name Space

2012-07-11T04:45:19Z

Scripting and Groups: Viewer URI Name Space

← Older revision		Revision as of 21:45, 10 July 2012
Line 50:		Line 50:
	#Note to teams working on shared scripting projects: membership in a common group is one of the pre-requisites to [[Editing someone else's scripts and notecards\|shared editing access to scripts]].		#Note to teams working on shared scripting projects: membership in a common group is one of the pre-requisites to [[Editing someone else's scripts and notecards\|shared editing access to scripts]].
	#You can use the [[World API]] in order to obtain group information by UUID key.		#You can use the [[World API]] in order to obtain group information by UUID key.
	#There is no LSL function that returns a group's name as a string. However, if you know a group key (as a result of calling [[llGetObjectDetails]] with [[OBJECT_GROUP]], or calling [[llGetParcelDetails]] with [[PARCEL_DETAILS_GROUP]]), you can display the group's name in the viewer and chat history ~~with~~ the ~~following special URL~~:		#There is no LSL function that returns a group's name as a string. However, if you know a group key (as a result of calling [[llGetObjectDetails]] with [[OBJECT_GROUP]], or calling [[llGetParcelDetails]] with [[PARCEL_DETAILS_GROUP]]), you can display the group's name in the viewer and chat history using the [[Viewer URI Name Space]]:
	<lsl>llOwnerSay("secondlife:///app/group/" + (string)group_key + "/about");</lsl>		<lsl>llOwnerSay("secondlife:///app/group/" + (string)group_key + "/about");</lsl>

	===Footnotes===		===Footnotes===
	{{Footnotes}}		{{Footnotes}}

Zidonuke Ghost: /* Scripting and Groups */

2011-03-04T13:24:34Z

Scripting and Groups

← Older revision		Revision as of 06:24, 4 March 2011
Line 49:		Line 49:
	#Communications such as [[LlInstantMessage\|instant messages]] cannot be sent to a group per se. Instead, what you have to do is create a list of the UUIDs of the people in that group, and loop through the list sending an instant message to each person separately;		#Communications such as [[LlInstantMessage\|instant messages]] cannot be sent to a group per se. Instead, what you have to do is create a list of the UUIDs of the people in that group, and loop through the list sending an instant message to each person separately;
	#Note to teams working on shared scripting projects: membership in a common group is one of the pre-requisites to [[Editing someone else's scripts and notecards\|shared editing access to scripts]].		#Note to teams working on shared scripting projects: membership in a common group is one of the pre-requisites to [[Editing someone else's scripts and notecards\|shared editing access to scripts]].
			#You can use the [[World API]] in order to obtain group information by UUID key.
	#There is no LSL function that returns a group's name as a string. However, if you know a group key (as a result of calling [[llGetObjectDetails]] with [[OBJECT_GROUP]], or calling [[llGetParcelDetails]] with [[PARCEL_DETAILS_GROUP]]), you can display the group's name in the viewer and chat history with the following special URL:		#There is no LSL function that returns a group's name as a string. However, if you know a group key (as a result of calling [[llGetObjectDetails]] with [[OBJECT_GROUP]], or calling [[llGetParcelDetails]] with [[PARCEL_DETAILS_GROUP]]), you can display the group's name in the viewer and chat history with the following special URL:
	<lsl>llOwnerSay("secondlife:///app/group/" + (string)group_key + "/about");</lsl>		<lsl>llOwnerSay("secondlife:///app/group/" + (string)group_key + "/about");</lsl>
	~~#You can use the [[World API]] in order to obtain group information by UUID key.~~

	===Footnotes===		===Footnotes===
	{{Footnotes}}		{{Footnotes}}

Zidonuke Ghost at 13:24, 4 March 2011

2011-03-04T13:24:14Z

← Older revision		Revision as of 06:24, 4 March 2011
Line 51:		Line 51:
	#There is no LSL function that returns a group's name as a string. However, if you know a group key (as a result of calling [[llGetObjectDetails]] with [[OBJECT_GROUP]], or calling [[llGetParcelDetails]] with [[PARCEL_DETAILS_GROUP]]), you can display the group's name in the viewer and chat history with the following special URL:		#There is no LSL function that returns a group's name as a string. However, if you know a group key (as a result of calling [[llGetObjectDetails]] with [[OBJECT_GROUP]], or calling [[llGetParcelDetails]] with [[PARCEL_DETAILS_GROUP]]), you can display the group's name in the viewer and chat history with the following special URL:
	<lsl>llOwnerSay("secondlife:///app/group/" + (string)group_key + "/about");</lsl>		<lsl>llOwnerSay("secondlife:///app/group/" + (string)group_key + "/about");</lsl>
			#You can use the [[World API]] in order to obtain group information by UUID key.

	===Footnotes===		===Footnotes===
	{{Footnotes}}		{{Footnotes}}

Jeremy Linden at 17:47, 18 January 2011

2011-01-18T17:47:50Z

← Older revision		Revision as of 10:47, 18 January 2011
Line 14:		Line 14:
	===Group Membership===		===Group Membership===

	There is a limit of 25 groups that a person may belong to (~~still current as of July 2008~~.) The original limit was 10; this was raised to 15 in SL 1.4.0, and again in SL 1.12.0 to 25. Calls for the maximum to be increased even further began almost immediately after it was raised to 25.		There is a limit of 42 groups that a person may belong to (updated January 2011.) The original limit was 10; this was raised to 15 in SL 1.4.0, and again in SL 1.12.0 to 25. Calls for the maximum to be increased even further began almost immediately after it was raised to 25.

	===Joining a Group===		===Joining a Group===