Tribe Enforcer Ascended

Paid Tribe Enforcer Ascended 1.06

No permission to buy ($39.99)
This resource is paid, and requires to be purchased
First time purchasing one of my plugins?
Please read over this before purchasing https://www.lethalplugins.com/FAQ




TribeEnforcerAscended.png

Tribe Enforcer Ascended aims to provide consistent tribe members across a cluster including the same Tribe ID on all servers.
MaridaDB (recommended) or MySQL 8.0.26 or lower)

Features
  • Automatically removes Personal Ownership from structures and updates existing tribe governance if Personal Ownership was selected.
  • Works with Name Control Ascended to make sure the tribe name fits your server's naming standards (supports the "block" setting only)
  • A tribe created on a map will automatically be created on any other map when a tribe member joins the new map on the cluster.
  • A tribe member invited on Server A will be auto added to the Tribe on Server B upon joining the map. No, longer do tribes have to invite players on every map to be in the same tribe.
  • Kicking a player from the tribe will kick them cluster wide from the tribe.
  • Ability to Promote/Demote Tribe Admins across the cluster.
  • Renaming the tribe will happen cluster wide on any active map your tribe is currently logged into and inactive maps (no players online) once a tribe member logs into that server.
  • Handles merging tribes with structures on other maps even if invited on another map when the "owning" player joins back to that server and is added to the new tribe.
  • This will also handle enforcing tribe size cluster wide preventing having different players on different maps.
  • Tribe names are now reserved cluster wide upon tribe creation so it may not be used on another map by another tribe.
  • Tribe Size permissions assigned based on tribe members (Permissions 1.8 required to use the feature)
  • Discord logging for all auto managed tribe events.
  • Full Unicode support for tribe names.
  • Option to Kick and Teleport a player instead of trapping inside their old tribes base (also helps prevent griefing)
  • Additional features to help support adding to existing clusters seamlessly.
  • Force Tribe Membership (Tribe Logs Ascended force tribe will be ignored in favor of this one)
  • LFG System to allow tribes to invite players flagged as "Looking for group" anywhere on the cluster.

Rcon/Console Commands
* Force add players to a tribe using TribeEnforcerAscended.AddPlayer <tribeid> <playerid> <owner> (TribeEnforcerAscended.addplayer 44444444 12345567 0)
playerid is their character implant id not their EOSID
owner: 0 = member and 1 = owner
  • Give all dinos/structures from TribeA to TribeB using TribeEnforcerAscended.GiveToTribe <TribeB ID> <TribeA ID> (TribeEnforcerAscended.GiveToTribe 1234567890 9876543210) Someone from TribeB must be online on the map where the fix is needed and the command must be sent to that map as well.
  • Reload plugin config TribeEnforcerAscended.Reload

Rcon Only
* TribeEnforcerAscended.FixTribe <tribeid> (TribeEnforcerAscended.FixTribe 44444444)
FixTribe will remove all tribe members online on the server you run the command on.
This will remove the tribe files and instruct the players they can log back in as part of the kick message they receive.
Upon logging in the plugin will regenerate a new tribe file.
In general this should fix all issues 99% of the time.

Examples
* Lets say that "Lethal" created a tribe named "Lethal Tribe". Lethal invites Bill to join the tribe and decides he wants to travel to The Center map. Bill transfers to The Center where "Lethal Tribe" is immediately created and Bill is added as a tribe member. Both tribes will have the same Tribe ID for easy admin tracking and Lethal and Bill don't have to worry about tribing up at a later time.

* Later that day Lethal travels to The Center map for the first time. Upon joining the map Lethal is added to the tribe "Lethal Tribe" and set as the tribe owner automatically.

* While on The Center map Lethal meets another player to add to the tribe named Jim. Jim has already built some structures and tamed some dinos on Extinction. Lethal invites Jim to the tribe on The Center. When Jim transfers back to Extinction the system knows that Jim should be in "Lethal Tribe" but is currently tribe owner of "Tribe of Jimbo" so it automatically creates the "Lethal Tribe" for the first time on Extinction then merges "Tribe of Jimbo" into "Lethal Tribe" keeping all of Jim's structures and dinos even though he was invited on another map.
Author
Lethal
Views
516
First release
Last update
Rating
5.00 star(s) 2 ratings

More resources from Lethal

Latest updates

  1. 1.06

    Tribe Enforcer Ascended v1.06 Server API 1.15+ Required and Visual C++ 2022 Runtime Files...
  2. 1.05

    Tribe Enforcer Ascended v1.05 Server API 1.15+ Required and Visual C++ 2022 Runtime Files...
  3. 1.04

    Tribe Enforcer Ascended v1.04 Server API 1.15+ Required and Visual C++ 2022 Runtime Files...

Latest reviews

The mismatch of Tribes across a cluster is super annoying. This Plugin manages that well. The only thing this needs is Alliance syncing.
My last plugin, I think is very usefull to players around the cluster . Forget have different tribes or recruit/kick a player on each map
Back
Top