Daybreak have published an article outlining the upcoming changes to base building.

We've had several competing (and sometimes confusing) systems implemented to combat cheaters, as well as to make construction in survival more robust and appealing.  I've spent the last several weeks ironing out some new systems, streamlining old ones, and working with our UI team to make some substantive improvements for our base building fans.

The current construction design on our live servers requires people wanting to share building tasks to join together in a group.  While in the group, players can build on each others’ structures, demolish them, and generally have full control over the bases of any player in their group.  One of the issues here is obvious: what if I don’t want player XXXX to have 100% control over everything I’ve built in the game?  Another issue is the simplistic way the permissions are being done, which means that anyone in the group has access to all items (due to being able to use a demo hammer) in short order.  The final issue is that groups are not persistent, and lead to frustration when players cannot build while the owners of structures are offline.

We were going to replace the group system with a persistent clan system, which would have solved the latter problem.  However, the other problems would still be unsolved.  Instead, we chose to implement a fully-fledged and extendable permission system.  This will allow a much more granular control of bases, and will protect the base owners from the majority of bad outcomes due to the “all or nothing” nature of either groups or clans.

The system we have in development is a per-foundation access list, with a set of three permissions: Container Access, Construction Access, and Demolition Access.  This gives the base owner a way to set persistent permissions on a per-player, per-foundation basis.  Base-building foremen, as owners, can set up (for example) a multi-foundation base, where one of the foundations is a “common” area, where players with construction access can place their own structures.

Under this architecture, one or two trusted players could be given demolition access for certain parts of the base, to be available to aid other players who misplace items on the base.  They also protect against a player with construction access griefing everyone who shares the base by building irritating or deadly areas into the base.

This also allows the base-building player to have their own base, secure in the knowledge that only the people they designate can alter it.  So, base owners can have their own private bases without having to worry that someone from another base-building project can come and wreck their work.

These access lists fit into our current system nicely, replacing the group-based access lists.  We still support the Secured Areas (such as large shelters) with their no-clip protection.  These new access levels apply to anything attached to the foundation.  The new rules for building apply at all times, but the new rules for destruction and container access only apply when the base is secured (i.e. fully enclosed by walls and/or gates).  This is to allow PvP to occur in bases on servers that support it.

To recap, the following are the rules of the new base system:

• Current Secured Areas function as normal.
• Destruction and container access control only on closed bases.
• Construction access control applies at all times.
• PvE servers only allow players to destroy base components if they have demolition access.

This system is currently in testing, and we look forward to getting it out onto our Test and Live servers as soon as possible.

Source: h1z1.com