s8n/auth-limbo-v2
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

bootstrap: AuthLimbo v2 0.1.0-SNAPSHOT (design phase)

Browse source 
Successor to s8n/auth-limbo following 2026-05-07 void-death incident.
Production-grade auth/login gatekeeper aspiring to 2b2t queue robustness
while explicitly avoiding pay-to-play / opaque-tier drama.

AGPL-3.0. Java 21. Paper 1.21.x.

Status: 0.1.0-SNAPSHOT, design phase. Architecture + roadmap docs land
from parallel research agents in subsequent commits.
This commit is contained in:
s8n 2026-05-07 19:30:40 +01:00
commit 226bebadbd
13 changed files with 1359 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

50
.gitignore vendored Normal file
View file

@ -0,0 +1,50 @@
# Maven build output
target/
*.jar
*.war
*.class
dependency-reduced-pom.xml
# IntelliJ IDEA
.idea/
*.iml
*.iws
*.ipr
out/
# Eclipse / VS Code
.classpath
.project
.settings/
.factorypath
.vscode/
bin/
# NetBeans
nbproject/private/
nbbuild/
dist/
nbdist/
.nb-gradle/
# OS junk
.DS_Store
Thumbs.db
desktop.ini
# Logs / runtime
*.log
hs_err_pid*.log
replay_pid*.log
# Local test server (don't commit a Paper jar or world)
test-server/
run/
*.lck
# Editor backups
*~
*.swp
*.swo
.\#*
\#*\#

30
CHANGELOG.md Normal file
View file

@ -0,0 +1,30 @@
# Changelog
All notable changes to AuthLimbo v2 are recorded here.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
This is a clean-slate successor to AuthLimbo v1, **not** v2.0.0 of v1.
Versioning restarts at 0.1.0-SNAPSHOT. The v1 history (0.1.0 → 1.1.0)
lives in <https://git.s8n.ru/s8n/auth-limbo/blob/main/CHANGELOG.md>
and is referenced here for context only.
## [Unreleased]
### Notes
- Project bootstrapped 2026-05-07 following the racked.ru void-death
incident. v1 received hot-fixes (F1 + F2 + F4); v2 is the proper
redesign.
- Architecture and roadmap docs land from parallel research agents in
subsequent commits.
### Added
- Repository scaffold (Maven, Java 21, Paper 1.21.x).
- Stub plugin main class (`AuthLimboV2`) — logs design-phase banner.
- `docs/MISSION.md`, `docs/DRAMA-AVOIDANCE.md` defining invariants.
- AGPL-3.0 license, baseline `.gitignore`, `CONTRIBUTING.md`.
[Unreleased]: https://git.s8n.ru/s8n/auth-limbo-v2/compare/HEAD...main

88
CONTRIBUTING.md Normal file
View file

@ -0,0 +1,88 @@
# Contributing to AuthLimbo v2
Thanks for considering a contribution. v2 is currently in design phase
(0.1.0-SNAPSHOT) — most of the value right now is in architecture
review, not code.
## Toolchain
- **JDK:** Eclipse Temurin (or any) 21+
- **Maven:** 3.9+
- **Paper:** 1.21.x (1.21.4 API target)
- **OS:** Linux preferred; Windows/macOS fine via standard JDK
## Build
```sh
mvn -B clean package
```
Artifact lands at `target/auth-limbo-v2-0.1.0-SNAPSHOT.jar`.
## Test server setup
A throwaway local Paper server is the easiest way to smoke-test
changes:
```sh
mkdir -p test-server && cd test-server
# fetch latest Paper 1.21.x build from https://papermc.io
java -Xms1G -Xmx2G -jar paper.jar nogui
# accept eula.txt
# stop, copy target/auth-limbo-v2-*.jar into plugins/, restart
```
`test-server/` is in `.gitignore` — never commit world data or a Paper jar.
For AuthMe-integration testing, drop the AuthMe-ReReloaded fork jar in
the same `plugins/` folder. The v1 repo carries a vendored copy under
`lib/` for reference.
## Branch / PR policy
- `main` is protected. All work goes via feature branch + PR.
- Branch names: `feat/<thing>`, `fix/<thing>`, `docs/<thing>`.
- One logical change per PR. Squash on merge if the history is messy.
- Every PR must update `CHANGELOG.md` under `[Unreleased]`.
## Commit identity
This repo uses:
```
Author: s8n <admin@s8n.ru>
```
**Strip `Co-Authored-By:` trailers before committing.** This is repo
convention — see ai-lab memory `user_git_identity.md` for the full
rationale (post-2026-05-07 Forgejo rename + identity tightening).
```sh
git -c user.name="s8n" \
-c user.email="admin@s8n.ru" \
-c commit.gpgsign=false \
commit -m "scope: subject"
```
## Code style
- 4-space indent, no tabs.
- Java 21 idioms (records, pattern matching, switch expressions where they help).
- No unused imports, no wildcard imports.
- `@Nullable` / `@NotNull` annotations on public method boundaries.
- Logging via `getLogger()`, not `System.out`.
## Reporting issues
File issues at <https://git.s8n.ru/s8n/auth-limbo-v2/issues>. Include:
- Paper version (`/version`)
- AuthMe version
- Plugin version (`/plugins`)
- Log excerpt — at least 50 lines around the failure
- Repro steps
## License
By contributing, you agree your contribution is licensed under
[AGPL-3.0-or-later](LICENSE).

661
LICENSE Normal file
View file

@ -0,0 +1,661 @@
GNU AFFERO GENERAL PUBLIC LICENSE
Version 3, 19 November 2007
Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The GNU Affero General Public License is a free, copyleft license for
software and other kinds of works, specifically designed to ensure
cooperation with the community in the case of network server software.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
our General Public Licenses are intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
Developers that use our General Public Licenses protect your rights
with two steps: (1) assert copyright on the software, and (2) offer
you this License which gives you legal permission to copy, distribute
and/or modify the software.
A secondary benefit of defending all users' freedom is that
improvements made in alternate versions of the program, if they
receive widespread use, become available for other developers to
incorporate. Many developers of free software are heartened and
encouraged by the resulting cooperation. However, in the case of
software used on network servers, this result may fail to come about.
The GNU General Public License permits making a modified version and
letting the public access it on a server without ever releasing its
source code to the public.
The GNU Affero General Public License is designed specifically to
ensure that, in such cases, the modified source code becomes available
to the community. It requires the operator of a network server to
provide the source code of the modified version running there to the
users of that server. Therefore, public use of a modified version, on
a publicly accessible server, gives the public access to the source
code of the modified version.
An older license, called the Affero General Public License and
published by Affero, was designed to accomplish similar goals. This is
a different license, not a version of the Affero GPL, but Affero has
released a new version of the Affero GPL which permits relicensing under
this license.
The precise terms and conditions for copying, distribution and
modification follow.
TERMS AND CONDITIONS
0. Definitions.
"This License" refers to version 3 of the GNU Affero General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy. The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based
on the Program.
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work
for making modifications to it. "Object code" means any non-source
form of a work.
A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.
The Corresponding Source for a work in source code form is that
same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force. You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright. Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section 10
makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.
b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7. This requirement modifies the requirement in section 4 to
"keep intact all notices".
c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:
a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.
d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.
A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling. In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage. For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product. A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.
"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source. The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed. Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:
a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or
e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or
run a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.
A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License. You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.
13. Remote Network Interaction; Use with the GNU General Public License.
Notwithstanding any other provision of this License, if you modify the
Program, your modified version must prominently offer all users
interacting with it remotely through a computer network (if your version
supports such interaction) an opportunity to receive the Corresponding
Source of your version by providing access to the Corresponding Source
from a network server at no charge, through some standard or customary
means of facilitating copying of software. This Corresponding Source
shall include the Corresponding Source for any work covered by version 3
of the GNU General Public License that is incorporated pursuant to the
following paragraph.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the work with which it is combined will remain governed by version
3 of the GNU General Public License.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of
the GNU Affero General Public License from time to time. Such new versions
will be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU Affero General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU Affero General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU Affero General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU Affero General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU Affero General Public License for more details.
You should have received a copy of the GNU Affero General Public License
along with this program. If not, see <https://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
If your software can interact with users remotely through a computer
network, you should also make sure that it provides a way for users to
get its source. For example, if your program is a web application, its
interface could display a "Source" link that leads users to an archive
of the code. There are many ways you could offer source, and different
solutions will be better for different programs; see section 13 for the
specific requirements.
You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU AGPL, see
<https://www.gnu.org/licenses/>.

61
README.md Normal file
View file

@ -0,0 +1,61 @@
# AuthLimbo v2
> 🚧 **Status: 0.1.0-SNAPSHOT — design phase. Not for production.**
Production-grade Minecraft auth/login gatekeeper. Successor to
[`s8n/auth-limbo`](https://git.s8n.ru/s8n/auth-limbo) (v1).
## Why this exists
V1 (`auth-limbo` 0.1.0–1.1.0) was a pragmatic rescue plugin written to
patch the AuthMe post-login void-death bug observed on the racked.ru
server. The 2026-05-07 incident exposed deeper failure modes that the v1
codebase wasn't structured to address cleanly. F1 + F2 + F4 hot-fixes
landed in v1 — v2 is the proper redesign as a successor.
## Goals
- **Production-grade.** Tight failure modes, observable, no silent drops.
- **2b2t-tight queue robustness.** Survives storms, slow logins,
bad clients, and AuthMe quirks without losing players.
- **Privacy-first.** No telemetry. Local data stays local.
- **No drama.** See [`docs/DRAMA-AVOIDANCE.md`](docs/DRAMA-AVOIDANCE.md).
## Non-goals
- ❌ Paid priority queue. Ever.
- ❌ Opaque "veteran tier" systems.
- ❌ Vanity feature creep. The plugin gates auth — that's the whole job.
## Architecture
See [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md) once written
(currently a placeholder pointing at v1's `V2-ARCHITECTURE.md` research).
## Roadmap
See [`docs/ROADMAP.md`](docs/ROADMAP.md) (placeholder pointing at v1's
`V2-ROADMAP.md`). Living doc — items move as research agents land work.
## License
[AGPL-3.0-or-later](LICENSE). All forks must remain copyleft.
## Dev quickstart
```sh
git clone ssh://git@git.s8n.ru:222/s8n/auth-limbo-v2.git
cd auth-limbo-v2
mvn -B clean package
# artifact: target/auth-limbo-v2-0.1.0-SNAPSHOT.jar
```
Java 21, Maven 3.9+, Paper 1.21.x. See [`CONTRIBUTING.md`](CONTRIBUTING.md).
## Links
- Repo: <https://git.s8n.ru/s8n/auth-limbo-v2>
- v1 (predecessor): <https://git.s8n.ru/s8n/auth-limbo>
- Mission: [`docs/MISSION.md`](docs/MISSION.md)
- Drama avoidance: [`docs/DRAMA-AVOIDANCE.md`](docs/DRAMA-AVOIDANCE.md)
- Changelog: [`CHANGELOG.md`](CHANGELOG.md)

31
docs/ARCHITECTURE.md Normal file
View file

@ -0,0 +1,31 @@
# ARCHITECTURE
> **Placeholder.** Full architecture doc lands from a parallel research
> agent in a subsequent commit. Until then, the closest existing
> reference is the v1 design note:
>
> <https://git.s8n.ru/s8n/auth-limbo/blob/main/docs/V2-ARCHITECTURE.md>
>
> That document was written *during v1's lifecycle* as the design
> sketch for what would become v2. Treat it as the starting point —
> not the final architecture.
## Planned scope of this document (when written)
- **State machine.** Every login state, every transition, every
timeout. Diagram + prose.
- **Threading model.** Which work runs on the main thread, which on
async pools, where the synchronisation boundaries are.
- **Persistence.** What state is stored, where, in what format.
Restart-safety semantics.
- **AuthMe integration.** How v2 reads `authme.db`, how it observes
AuthMe's lifecycle events, how it decouples from AuthMe quirks.
- **Failure modes.** Backend-down, chunk-not-loaded, player-disconnect-
mid-flow, server-restart-mid-flow. One paragraph per mode.
- **Observability.** Logging schema, metrics surface (if any — opt-in
only), how an operator debugs a stuck player.
- **Security model.** Threat model, trust boundaries, what a hostile
client can and cannot do.
Until the agent lands the real doc, design discussion happens in
PRs and the v1 reference above.

86
docs/DRAMA-AVOIDANCE.md Normal file
View file

@ -0,0 +1,86 @@
# DRAMA-AVOIDANCE
Explicit ethics statement for AuthLimbo v2 and any server using it.
The Minecraft public-server space is full of failure modes that aren't
technical — they're social. This document pins down what this project
will and won't do, so that future operators (including me, six months
from now, tired) don't drift.
## Hard rules
### NO paid priority queue. Ever.
- No "skip the queue for $5/month."
- No "VIP slot reservation" tier.
- No "donor instant join."
- The queue is FIFO. Period.
If the server is full, everyone waits the same way. Operators may
reserve slots **only** for documented administrative purposes
(moderation, emergency response) and those slots are listed in the
repo with named holders.
### NO opaque veteran tiers
- No hidden "respected player" perks.
- No mod-discretion permission grants without a written rule.
- If the server has trust levels (e.g. build access, /tp privileges),
the criteria are:
1. Documented in the repo (e.g. `docs/TRUST-TIERS.md` if/when it
exists).
2. Earned via measurable, public criteria (hours played, no warns
in N days, etc.).
3. Auditable — anyone can ask "why does X have rank Y?" and the
answer is in the data, not a vibe.
### All exploits / known-bugs in CHANGELOG
- Every CVE-class issue gets a `### Security` block with the date
it was discovered, the date it was fixed, and the commit hash.
- We don't memory-hole bugs. Drama feeds on hidden history.
### All policy changes via PR
- Operator-side rule changes (whitelist policy, kick rules, etc.)
that touch the plugin's behaviour go through a PR with a written
reason in the commit message.
- "Why was this added?" must always have an answer in the git log.
### Reproducible builds
- `mvn -B clean package` from a tagged commit must produce a jar
that matches the published artifact's `sha256`.
- Tags carry a release note in `CHANGELOG.md` with the expected hash.
- No "trust-me-bro" jars. If you can't reproduce it, you can't audit it.
## Soft rules (norms, not constraints)
- **No callouts.** When a player misbehaves, log + ban. No public
shaming threads.
- **No "exec lounge" channels.** Mod chat exists for moderation, not
for a clique. Anything that smells like an in-group should be
questioned.
- **Operators are accountable, not entitled.** Running the server is
a job. The community doesn't owe them deference.
## What this means in code
- The plugin will never expose a permission node like
`authlimbo.priority` or `authlimbo.skipqueue`.
- The plugin will never read a "donor" flag from any external service.
- The plugin's queue ordering is purely arrival-time + admin-reserved.
No other inputs.
If you find yourself adding a feature that violates one of these,
stop, write up the use-case in an issue, and let the community
push back before merging. The drama-avoidance invariant is more
important than any single feature.
## Why this document exists
Because every Minecraft community that fell apart did so because
*nobody wrote down what the project would not do.* This is that
document. It is binding on this codebase. Forks may diverge — and
because the project is AGPL-3.0, those forks must publish their
divergence and the reasons.

73
docs/MISSION.md Normal file
View file

@ -0,0 +1,73 @@
# MISSION
AuthLimbo v2 exists to gate Minecraft logins on a hardened, AuthMe-backed
public server (racked.ru) without losing players, leaking metadata, or
introducing pay-to-play drama.
Three invariants are non-negotiable.
## 1. Privacy invariant
- **No outbound telemetry.** The plugin never phones home.
- **No third-party SDKs.** Stats, analytics, crash-reporting — all out.
- **Local data stays local.** Auth records, session tokens, and state
files live on the operator's disk. The plugin never replicates them
off-host.
- **Logs are minimum-necessary.** UUID + event class. No IPs in normal
logs (debug-only). No chat content. No coords beyond what the bug
report needs.
## 2. Reliability invariant
- **No void deaths.** A player who authenticates correctly must not die
to gravity, void, or chunk-load races during the auth → spawn handoff.
This is the bug v1 was written to patch (2026-05-07).
- **Login is a serialised state machine.** No racing tasks. Every
transition is logged with timestamp + UUID + state.
- **Failure modes are bounded.** If the auth backend is down, players
hold in limbo with a clear message — never get dumped into the live
world half-authenticated.
- **Restart-safe.** A mid-login player when the server stops must
re-enter the same flow on next join, not be stuck in a half-state.
## 3. No-drama invariant
- **No paid priority. Ever.** No queue-skip for money. See
[DRAMA-AVOIDANCE.md](DRAMA-AVOIDANCE.md).
- **No opaque tiers.** If the server has trust levels, the criteria are
in the repo, in plain English, and earned not bought.
- **All policy changes via PR.** Even operator-side. Anyone can read the
history and see *why* a rule changed and *when*.
## Operator
- **Operator:** s8n (`admin@s8n.ru`)
- **Server:** racked.ru (Minecraft Java, Paper 1.21.x, AuthMe-backed)
- **Brand:** racked.ru is the gameplay brand; `veilor` is a separate
security-company brand. Do not conflate. (See ai-lab memory
`project_brand_separation.md`.)
## Origin context
- **2026-05-07:** racked.ru void-death incident. AuthMe post-login
teleport raced against chunk load → players spawned into unloaded
chunks → fell into void.
- **v1 patch:** F1 + F2 + F4 fixes landed in `s8n/auth-limbo` 1.1.0
(chunk-preload + delayed teleport + spawn-anchor verification).
- **v2 redesign:** v1 worked, but the codebase was a rescue patch. v2
is the proper successor — reliability invariant baked into the
architecture from line 1, not bolted on.
## What "done" looks like for v2
A 1.0.0 release that:
1. Has zero open void-death bugs and a regression test for each historical one.
2. Survives a 200-concurrent-login storm test without dropping or dying.
3. Carries a written security review of the auth path.
4. Has an architecture doc that a new contributor can read in 30 minutes
and understand the full state machine.
5. Holds the no-drama invariant — no paid priority, no opaque tiers,
policy changes via PR with reasoned commit messages.
When all five hold, we tag v1.0.0 and the design phase is over.

48
docs/ROADMAP.md Normal file
View file

@ -0,0 +1,48 @@
# ROADMAP
> **Placeholder.** Full roadmap lands from a parallel research agent in
> a subsequent commit. Until then, the closest existing reference is
> v1's roadmap note:
>
> <https://git.s8n.ru/s8n/auth-limbo/blob/main/docs/V2-ROADMAP.md>
>
> That document sketches the milestones identified during the v1
> lifecycle. Treat it as the starting point — items will be re-scoped
> and re-prioritised as v2 design firms up.
## High-level phases (sketch)
### Phase 0 — bootstrap (current)
- Repo scaffold ✅
- Mission, drama-avoidance docs ✅
- Stub plugin compiles ✅
- Architecture + roadmap docs (this commit and the next) ⏳
### Phase 1 — design
- Architecture doc landed.
- State machine fully diagrammed.
- Failure-mode catalogue complete.
- Test plan written.
### Phase 2 — implementation
- State machine implemented.
- AuthMe integration ported / rewritten from v1.
- Persistence layer.
- Observability surface.
### Phase 3 — hardening
- Storm test (200-concurrent-login).
- Security review.
- Regression test for every historical v1 bug.
### Phase 4 — 1.0.0
- All five "done" criteria from MISSION.md hold.
- Tag, release notes, reproducible-build hash published.
- v1 deprecated.
Detailed task list and milestones land with the real ROADMAP.md.

142
pom.xml Normal file
View file

@ -0,0 +1,142 @@
<?xml version="1.0" encoding="UTF-8"?>
<!--
AuthLimbo v2 — Minecraft auth/login gatekeeper, successor to AuthLimbo v1.
Copyright (C) 2026 s8n <admin@s8n.ru>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU Affero General Public License as
published by the Free Software Foundation, either version 3 of the
License, or (at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU Affero General Public License for more details.
You should have received a copy of the GNU Affero General Public License
along with this program. If not, see <https://www.gnu.org/licenses/>.
-->
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>ru.s8n</groupId>
<artifactId>auth-limbo-v2</artifactId>
<version>0.1.0-SNAPSHOT</version>
<packaging>jar</packaging>
<name>AuthLimbo v2</name>
<description>Production-grade Minecraft auth/login gatekeeper. Successor to AuthLimbo v1.</description>
<url>https://git.s8n.ru/s8n/auth-limbo-v2</url>
<licenses>
<license>
<name>GNU Affero General Public License v3.0 or later</name>
<url>https://www.gnu.org/licenses/agpl-3.0.txt</url>
<distribution>repo</distribution>
</license>
</licenses>
<scm>
<connection>scm:git:ssh://git@git.s8n.ru:222/s8n/auth-limbo-v2.git</connection>
<developerConnection>scm:git:ssh://git@git.s8n.ru:222/s8n/auth-limbo-v2.git</developerConnection>
<url>https://git.s8n.ru/s8n/auth-limbo-v2</url>
</scm>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<maven.compiler.source>21</maven.compiler.source>
<maven.compiler.target>21</maven.compiler.target>
<maven.compiler.release>21</maven.compiler.release>
<paper.api.version>1.21.4-R0.1-SNAPSHOT</paper.api.version>
<adventure.version>4.17.0</adventure.version>
</properties>
<repositories>
<repository>
<id>papermc</id>
<url>https://repo.papermc.io/repository/maven-public/</url>
</repository>
<repository>
<id>sonatype</id>
<url>https://oss.sonatype.org/content/groups/public/</url>
</repository>
</repositories>
<dependencies>
<!-- Paper API (provided by the server runtime). Adventure is
bundled with Paper, so we don't shade it. -->
<dependency>
<groupId>io.papermc.paper</groupId>
<artifactId>paper-api</artifactId>
<version>${paper.api.version}</version>
<scope>provided</scope>
</dependency>
<!-- Adventure API for explicit text components in plugin code.
Paper re-exports this; declared here for clarity. -->
<dependency>
<groupId>net.kyori</groupId>
<artifactId>adventure-api</artifactId>
<version>${adventure.version}</version>
<scope>provided</scope>
</dependency>
<!-- AuthMe will be re-introduced as a system-scope dep when the
integration layer is implemented. v1 vendored the jar in
lib/ — v2 will follow the same pattern in a later commit. -->
</dependencies>
<build>
<finalName>${project.artifactId}-${project.version}</finalName>
<resources>
<resource>
<directory>src/main/resources</directory>
<filtering>true</filtering>
</resource>
</resources>
<plugins>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.13.0</version>
<configuration>
<release>21</release>
</configuration>
</plugin>
<!-- Shade plugin wired in but with no relocations until
we have shaded deps (e.g. SQLite for AuthMe DB reads). -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-shade-plugin</artifactId>
<version>3.5.3</version>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>shade</goal>
</goals>
<configuration>
<createDependencyReducedPom>false</createDependencyReducedPom>
<minimizeJar>false</minimizeJar>
<filters>
<filter>
<artifact>*:*</artifact>
<excludes>
<exclude>META-INF/*.SF</exclude>
<exclude>META-INF/*.DSA</exclude>
<exclude>META-INF/*.RSA</exclude>
<exclude>META-INF/MANIFEST.MF</exclude>
</excludes>
</filter>
</filters>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</project>

47
src/main/java/ru/authlimbov2/AuthLimboV2.java Normal file
View file

@ -0,0 +1,47 @@
/*
* AuthLimbo v2 — Minecraft auth/login gatekeeper, successor to AuthLimbo v1.
* Copyright (C) 2026 s8n <admin@s8n.ru>
*
* This program is free software: you can redistribute it and/or modify
* it under the terms of the GNU Affero General Public License as
* published by the Free Software Foundation, either version 3 of the
* License, or (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU Affero General Public License for more details.
*
* You should have received a copy of the GNU Affero General Public License
* along with this program. If not, see <https://www.gnu.org/licenses/>.
*/
package ru.authlimbov2;
import org.bukkit.plugin.java.JavaPlugin;
/**
* AuthLimbo v2 plugin entry point.
*
* <p>0.1.0-SNAPSHOT — design phase. This class is intentionally a stub:
* it logs a banner on enable and disable so operators can verify the
* jar loads, then does nothing else. Real auth-gating logic lands in
* subsequent commits per {@code docs/ROADMAP.md}.</p>
*
* <p>This stub does <strong>not</strong> register listeners, commands,
* or scheduled tasks — installing this jar on a production server has
* no effect beyond startup logs.</p>
*/
public final class AuthLimboV2 extends JavaPlugin {
@Override
public void onEnable() {
getLogger().info("AuthLimbo v2 0.1.0-SNAPSHOT loaded — design phase, not for production yet.");
getLogger().info("Source: https://git.s8n.ru/s8n/auth-limbo-v2");
getLogger().info("Mission: privacy + reliability + no drama. See docs/MISSION.md.");
}
@Override
public void onDisable() {
getLogger().info("AuthLimbo v2 disabled.");
}
}

34
src/main/resources/config.yml Normal file
View file

@ -0,0 +1,34 @@
# AuthLimbo v2 — config.yml
#
# 0.1.0-SNAPSHOT (design phase) — this file is a placeholder.
# Real options land as the state machine is implemented.
#
# Conventions:
# - All keys lowercase-kebab-case.
# - Time values are durations in seconds unless otherwise noted.
# - Defaults are the safe operator choice.
# Plugin-level toggles. Off = plugin is loaded but gating is disabled
# (useful for staging / migration). On = full gating active.
enabled: false
# Logging level. One of: error, warn, info, debug, trace.
# debug + trace include UUIDs and IPs — do not run those in production
# unless actively investigating.
log-level: info
# Reserved for future limbo world / spawn settings.
# limbo:
# world: limbo
# spawn: { x: 0, y: 64, z: 0 }
# timeout-seconds: 300
# Reserved for future AuthMe integration knobs.
# authme:
# db-path: plugins/AuthMe/authme.db
# poll-interval-ms: 250
# Reserved for future queue knobs (FIFO, no priority — see DRAMA-AVOIDANCE.md).
# queue:
# max-concurrent-logins: 8
# admin-reserved-slots: 0

8
src/main/resources/plugin.yml Normal file
View file

@ -0,0 +1,8 @@
name: AuthLimboV2
version: ${project.version}
main: ru.authlimbov2.AuthLimboV2
api-version: '1.21.4'
author: s8n
description: Production Minecraft auth/login gatekeeper. Successor to AuthLimbo v1.
website: https://git.s8n.ru/s8n/auth-limbo-v2
load: STARTUP