Merge pull request 'docs(bridge): bring EventsEnabled's comment to main' (#46) from edge into main
All checks were successful
Release plugin / release (push) Successful in 15s

Reviewed-on: #46
This commit is contained in:
2026-10-23 07:07:09 +00:00

View File

@@ -445,12 +445,20 @@ namespace Oxide.Plugins
public string ServerId = "main";
/// <summary>
/// Whether the website may borrow values on this server for events (protocol 8,
/// D76). <b>Off until an operator turns it on.</b> Letting staff moderate from a
/// screen they are looking at, and letting a schedule change the world at four in
/// the morning, are different consents, and one switch cannot honestly express
/// both. It gates taking a lease only: listing and giving back always work, so
/// turning it off never strands a value somebody already borrowed.
/// Whether the website may run events on this server at all (protocol 8, D76).
/// <b>Off until an operator turns it on.</b> Letting staff moderate from a screen
/// they are looking at, and letting a schedule change the world at four in the
/// morning, are different consents, and one switch cannot honestly express both.
/// <para>
/// It began as the lease switch and grew with the protocol. It now gates taking a
/// lease (protocol 8), every world write (protocol 9, D94: zones, placed crates and
/// NPCs, and from protocol 14 world calls, Dangerous Treasures, Guarded Crate,
/// raid bases and console commands — <see cref="WorldWritesAllowed"/>), opening a
/// tally and a run's chat line (protocol 10, D107), and paying coins (protocol 14).
/// Listing, giving back, reverting and every read always work, so turning it off
/// never strands anything an event already holds. An admin can set it from the
/// website's config editor, and it takes effect without a reload.
/// </para>
/// </summary>
public bool EventsEnabled = false;