> For the complete documentation index, see [llms.txt](https://doc.stellarvan.cn/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.stellarvan.cn/readme/kai-shi/xue-xi-lu-xian.md).

# 学习路线

## 学习路线

如果你刚开始写 Minecraft 插件，按这条路线最稳。

{% stepper %}
{% step %}

### 配好开发环境

先准备 Java、IDE、构建工具和本地测试服。

目标很简单。 你能本地编译插件，并把它丢进服务器测试。
{% endstep %}

{% step %}

### 写出第一个插件

先做最小可运行版本。

只要插件能加载、输出日志、响应一个命令，就已经入门。
{% endstep %}

{% step %}

### 学会三个核心能力

优先学这三块：

* 生命周期
* 命令与权限
* 事件监听

这三块覆盖大多数基础插件。
{% endstep %}

{% step %}

### 再学配置和数据

基础逻辑稳定后，再处理配置文件和持久化。

这样不容易把项目一开始就写复杂。
{% endstep %}

{% step %}

### 最后补调试和发布

你需要会看报错、定位问题、打包和发布。

这一步决定插件能不能真正交付。
{% endstep %}
{% endstepper %}

### 推荐技术栈

教程默认使用这套组合：

* Java
* Paper API
* IntelliJ IDEA
* Maven

Paper 兼容 Bukkit / Spigot 生态。 它也是现在最常见的入门选择。

{% hint style="info" %}
如果你后面想写更现代的服务端插件，可以继续学 Paper 专属 API。 如果你想做模组开发，路线就该换成 Fabric 或 Forge。
{% endhint %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc.stellarvan.cn/readme/kai-shi/xue-xi-lu-xian.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.