Ver código fonte para Add-on Getting Started/es

'''Primeros pasos con addons''' explica lo que necesitas tener listo ''antes'' de conectar tu propio mod de Forge con DragonMineZ: las versiones de las herramientas, los mods que debes evitar y las partes de DMZ en las que un addon puede confiar sin riesgo. Léela antes de [[Special:MyLanguage/Creating a DMZ Addon|Crear un addon de DMZ]].

<span id="Who_this_is_for"></span>
== Para quién es ==
Estas páginas son para desarrolladores de addons de Forge que quieren que el jar de su mod reaccione a DMZ: dar TP extra, escuchar cambios de forma, añadir nuevos tipos de objetivos y recompensas de misiones, agregar botones al menú de utilidades, etc. Si solo quieres ajustar números o añadir razas, formas, misiones o deseos, no necesitas nada de esto; consulta [[Special:MyLanguage/Developer Scope and Prerequisites|Alcance y requisitos]].

DMZ no tiene una API de Java para registrar razas, formas, habilidades o técnicas nuevas: las razas y formas nuevas se añaden con archivos de configuración JSON (consulta [[Special:MyLanguage/Custom Races|Razas personalizadas]] y [[Special:MyLanguage/Custom Forms|Formas personalizadas]]).

<span id="Required_toolchain"></span>
== Herramientas necesarias ==

{| class="wikitable"
! Requisito !! Versión !! Dónde se declara
|-
| Minecraft || <code>1.20.1</code> || <code>gradle.properties</code>
|-
| Forge || <code>47.4.10</code> (acepta <code>[47,)</code>) || <code>gradle.properties</code>, <code>mods.toml</code> del addon
|-
| ForgeGradle || <code>6.0.30</code> || Plugins de <code>build.gradle.kts</code>
|-
| Java || <code>17</code> || Toolchain de <code>build.gradle.kts</code>
|-
| Mappings || Parchment <code>2023.09.03-1.20.1</code> || <code>gradle.properties</code>
|-
| GeckoLib || <code>4.8.3+</code> || <code>gradle.properties</code>, <code>mods.toml</code> del addon
|-
| TerraBlender || <code>3.0.1.10+</code> || <code>gradle.properties</code>, <code>mods.toml</code> del addon
|-
| Curios API || <code>5.14.1+1.20.1</code> o posterior || <code>gradle.properties</code>, <code>mods.toml</code> del addon
|}

<div lang="en" dir="ltr" class="mw-content-ltr">
Match these exactly (or with compatible version ranges) in your own add-on's <code>build.gradle</code> or <code>build.gradle.kts</code>, <code>gradle.properties</code> and <code>mods.toml</code>, or you will hit classloading and mixin mismatches at runtime. DMZ itself is currently on mod version <code>2.2-alpha</code> (<code>gradle.properties</code>).
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
GeckoLib, TerraBlender and Curios are '''mandatory''' dependencies of DMZ, so they must be on your development runtime classpath too.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Incompatible mods ==
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
DMZ refuses to start (it throws an <code>IllegalStateException</code> while loading) when any of these mods is installed, and declares them <code>incompatible</code> in its <code>mods.toml</code>:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Legendary Tooltips (<code>legendarytooltips</code>)
* Epic Fight (<code>epicfight</code>)
* Better Combat (<code>bettercombat</code>)
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Don't depend on them, bundle them or add them to your development run configurations.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Pre-release builds ==
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
<code>2.2-alpha</code> is a pre-release build. Alpha and beta builds of DMZ only let whitelisted usernames join a world or server. The default ForgeGradle development username <code>Dev</code> is on the whitelist, so <code>runClient</code> works out of the box: keep that username for local testing.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Package layout ==
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Before writing any hook code, skim the source layout (<code>AI/Context.md</code> in the DMZ repository documents it in detail):
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* <code>com.dragonminez.client</code>: rendering, GUI and animation; client only.
* <code>com.dragonminez.common</code>: config, stats, networking, quests and wishes; the surface most add-ons touch.
* <code>com.dragonminez.server</code>: commands, storage, world generation and server events.
* <code>com.dragonminez.mixin</code>: mixins; avoid depending on these from an add-on.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Add-ons should hook <code>com.dragonminez.common</code> almost exclusively: it is the shared, most stable layer. The only client-side hooks meant for add-ons are <code>DMZClientEvent</code> and the utility menu slots (see [[Special:MyLanguage/Implementation and Events|Implementation and Events]]).
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Two integration styles ==
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# '''Hard dependency:''' your add-on requires DMZ to be present (<code>mandatory=true</code> in <code>mods.toml</code>). This is the simplest option, but your add-on won't load without DMZ.
# '''Soft (optional) dependency:''' your add-on works on its own and only turns on DMZ-specific behavior when DMZ is detected. DMZ uses this pattern itself for its optional integrations (<code>common/compat/WeaponLevelingCompat.java</code>, <code>common/compat/ApotheosisCompat.java</code>): check <code>ModList.get().isLoaded("dragonminez")</code> once, and keep every class that imports DMZ code behind that check. This is recommended if your add-on has value without DMZ installed. See [[Special:MyLanguage/Implementation and Events#Optional dependency pattern|Optional dependency pattern]].
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== What you can safely rely on ==
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* '''Events:''' the nested classes of <code>com.dragonminez.common.events.DMZEvent</code> (server and common) and <code>com.dragonminez.client.events.DMZClientEvent</code> (client) are the intended public hook surface. See [[Special:MyLanguage/Implementation and Events|Implementation and Events]] for the full list.
* '''Read-only player state:''' <code>StatsCapability</code>, <code>StatsProvider</code> and <code>StatsData</code>, for reading race, form, stats and resources.
* '''Extension registries:''' <code>QuestObjectiveRegistry</code> and <code>QuestRewardRegistry</code> (custom quest content types), <code>DMZTextPlaceholders</code> (custom <code>%placeholders%</code> in quest and dialogue text) and <code>UtilityMenuScreen.addMenuSlot</code> (buttons in the client utility menu).
* '''Registries:''' <code>MainItems</code>, <code>MainBlocks</code>, <code>MainEntities</code>, <code>MainAttributes</code>, <code>MainEffects</code>, <code>MainEnchants</code> (and the other <code>Main*</code> classes) under <code>common/init/</code> expose <code>RegistryObject</code> and <code>DeferredRegister</code> references you can import directly.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== What to avoid relying on ==
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Values reported by the client for anything related to progression. DMZ never trusts them either; read from the server-side capability instead.
* Changing <code>StatsData</code> fields directly outside of events or commands. Prefer reacting to or cancelling events over poking values, and prefer DMZ's existing commands when you need to change something DMZ owns.
* Registering packets on DMZ's network channel. DMZ's packet ids depend on registration order; use your own channel.
* Depending on <code>com.dragonminez.mixin</code> classes or DMZ internals not mentioned above. These can change without notice between versions.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
== Next step ==
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
Once your development environment builds against DMZ and you can see it detected at runtime, move on to [[Special:MyLanguage/Implementation and Events|Implementation and Events]] to wire up actual hooks, then to [[Special:MyLanguage/Creating a DMZ Addon|Creating a DMZ Addon]] for the full Gradle and <code>mods.toml</code> setup.
</div>

{{Navbox Add-ons}}