> For the complete documentation index, see [llms.txt](https://litenametags.nemesismc.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://litenametags.nemesismc.net/litenametags.md).

# 👋 LiteNameTags

Modern packet-based nametags built for performance, stability, and smooth movement on modern Paper servers.

LiteNameTags is designed for servers that want clean visuals without sacrificing scalability. It uses a packet-based approach focused on smoother nametag movement, better behavior in crowded areas, and more control over formatting and compatibility.

***

### ✨ Highlights

* Smooth nametag movement
* Packet-based rendering
* Built for modern Paper servers
* Better scalability in busy environments
* Group-based customization
* Placeholder support
* Built-in performance tools

***

### 📦 Quick Requirements

Required:

* Paper 1.21+
* PacketEvents

Recommended:

* PlaceholderAPI

***

### 🚀 Getting Started

If this is your first time using LiteNameTags, follow this order:

1. Install the plugin and its dependencies
2. Review the default configuration files
3. Set up your main groups
4. Test nametag rendering in-game
5. Use `/lnt perf` to validate performance

***

### 🔗 Quick Links

* [Installation](/getting-started/installation.md)
* [Initial Setup](/getting-started/initial-setup.md)
* [config.yml](/configuration/config.yml.md)
* [groups.yml](https://groups.yml)
* [Integrations](/integrations.md)
* [Commands](/commands.md)
* [Performance](/performance.md)
* [Troubleshooting](/troubleshooting.md)

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://litenametags.nemesismc.net/litenametags.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.