Group bans: an overview

On Tuesday June 17th, Linden Lab released the Group Ban project viewer (version 3.7.8.290887) which, as the name suggests, allows group owners (and those they nominate by role) to ban individuals from their group.

Group bans, which are enforced server-side, like parcel and estate bans, are intended to remove troublemakers from a group / prevent them from joining the group. This article will hopefully provide an overview of the group ban tools within the project viewer (and which will eventually progress to the release viewer).

The following general points with group bans should be noted:

  • By default, only a group’s Owners role has the Manage Ban List ability for banning other avatars from a group /removing avatars from the ban list
  • The ability can be granted to other roles, if required
  • Roles which are granted this ability are also granted the Eject Members from this Group and Remove Members from Roles abilities
  • The ban list for a group can store a maximum of 500 entries. When this limit is reached, some avatars must be removed before others can be added
  • Group Owners cannot be banned from a group (just as they cannot be ejected)
  • When a group member is banned from the group, they are automatically ejected and will receive the usual ejection notification, but will not receive any notice that they have also been banned
  • A user who is banned from a group cannot join it either directly or through an invitation
  • If a group member is banned while using group chat, they may be able to continue using it until they close the group chat window (this problem also exists when ejecting someone from a group when they have the group chat window open)
  • Any attempt to invite one or more banned avatars into a group, whether individually or as a part of a list, will generate the message:  Some residents have not been sent an invite due to being banned from the group.

The viewer itself includes the necessary options to allow a group owner (and those they nominate by role) to:

  • Add or remove avatars from the group ban list
  • View the group ban list
  • Add the ability to ban avatars from a group to any other roles within the group, if required.

Applying Group Bans

Avatars can be banned from a group in one of two ways:

  • By selecting them in the group members list if they are already a member of the group
  • By using the Group Ban Picker to ban one or more avatars from a group, whether or not they are already members.

Banning via the Members List

  • Display your groups list (CTRL-SHIFT-G), select the required group and open its profile
  • Click on Roles & Members to open it, and then click on the Members tab
  • Locate the first avatar you wish to ban and left-click on their name
  • If there is more than one avatar you wish to ban, press CTRL and left-click on each of the remaining names
  • Click on the Ban Member(s) button
  • The highlighted avatars will be ejected and banned from the group, and you should see the normal confirmatory notification(s) that they have been ejected.
Banning someone from a public droup via the Members tab (l), and confirming they are listed as banned on the Banned Residents tab (r)
Banning someone from a public group via the Members tab (l), and confirming they are listed as banned on the Banned Residents tab (r)

To confirm the selected individuals have been ejected and banned, click the right scroll buttons at the top of the panel to scroll / jump to the Banned Residents tab. This should display the name of all avatars banned from the group. If the name(s) of the avatar(s) just banned do not appear to be listed, wait a minute or two and click the refresh button in the lower left corner of the panel. Continue reading “Group bans: an overview”

Advertisements

SL projects update 25/1: server, viewer, pathfinding and surprise guest

The Simulator User Group meeting on Tuesday June 17th was busy even before the unannounced guest dropped in (see below)
The Simulator User Group meeting on Tuesday June 17th was getting busy even before the unannounced guest dropped in (see below)

Server Deploys, Week 24

As usual, please refer to the server deployment thread for the latest information.

Main (SLS) Channel

On Tuesday June 17th, the Main channel was updated with the Group Ban project, which was previously on the LeTigre RC.  As the name implies, this project adds the ability to ban users from groups (see also SL Viewer Updates, below) – release notes.

Release Candidate Channels

On Wednesday June 18th the three RC channels should be updated as follows:

  • LeTigre should receive a new server maintenance project this week, which comprises an anti-griefing measure – release notes
  • BlueSteel should remain on the Sunshine / AIS v3 project, the viewer for which was promoted to the de facto release viewer (version 3.7.9.290582) on Monday June 16th. In addition, BlueSteel should receive the Main channel update with the Group Ban project and the anti-griefing update deployed to LeTigre – release notes
  • Magnum should remain on the Experience Tools project. In addition, Magnum should will receive the Main channel update with the Group Ban project and the anti-griefing update deployed to LeTigre – release notes.

SL Viewer Updates

Release Viewer

On Monday June 16th, the MemShine release candidate viewer, (version 3.7.9.290582, was promoted to the de facto release viewer. This viewer includes the final Sunshine AIS v3 updates (promoting the Lab to issue a blog post announcing the long-running project Shining is now complete), and also a series of memory leak fixes to help stabilise the viewer and hopefully reduce the number of memory related crashes.

Group Ban project Viewer

As noted above server-side support for the Group Ban project is being deployed to the main grid. To coincide with this, the Lab issued the Group Ban project viewer (version 3.7.8.290887) on Tuesday June 17th, which provides the necessary viewer-side support for accessing group ban functions. Initial instructions for using the viewer can be found in the release notes, and I’ve provided an overview as well.

Group Chat

Simon Linden recently completed an initial amount of work on group chat, implementing some small-scale optimisations which, while not expected to have “fixed” group chat, should have improved some aspects of using it, reliability-wise. He’s more recently had to work on what have been viewed higher priority items, but is hoping to make a return to group chat in the very near future and dig into it some more. “I learned a lot on the first pass,” he said on the matter during the Simulator User Group meeting on Tuesday June 17th, “we got a lot more information on where the load is.  Thus I have hopes the next round will be better.”

Other Items

Pathfinding and Terrain Editing

BUG-772 “Simulator refusing to rez objects after 10 hour timeframe” was raised at the Simulator User Group meeting on Tuesday June 17th. This is an issue where if you are carrying out terraforming work on a region with pathfinding enabled, and are also making frequent Pathfinding navmesh updates, your region will rapidly run out of memory. the way to avoid this is to complete the terraforming activity, then rebake the navmesh and restart the region.

LSL Enhancements

Ideas were tossed around the Simulator User Group meeting on the limitations of LSL, many of which may only be resolved through a complete re-build of LSL, something which is unlikely to happen, as Simon Linden indicated in the meeting, “I don’t think we’re going to touch the internal design of LSL if we can help it.” Which doesn’t mean there will not continue to be enhancements to LSL functions etc.

One suggestion made to get around some of the issues was for the development of a viewer-side scripting language which might handle certain local functions and abilities. Responding to this, Simon would only say, “That would be a wonderfully big project :).”

Continue reading “SL projects update 25/1: server, viewer, pathfinding and surprise guest”