Changes

# Finally, it patches and finalizes the code, ready for modder consumption.

# Finally, it patches and finalizes the code, ready for modder consumption.

This can either be triggered whenever an environment is first being set up, or when ForgeGradle determines the existing environment is out of date whether from changed access transformers, mapping sets, or the current forge version.

This is triggered whenever the <code>setup</code> task is ran.

== Needed knowledge ==

== Needed knowledge ==

== The Forge Side ==

== The Forge Side ==

When the Forge is first synced, it prepares the files for setting up the workspace.

When Forge is first loaded by gradle, it prepares the files for setting up the workspace.

The initial setup is done through the <code>gradlew setup</code> task. It will run the SetupMCP tasks and then start applying the Forge system to the processed vanilla code. After the MCPConfig/SetupMCP tasks are finished, ForgeGradle will print '''MCP Environment Setup is complete''' and wait for the user input.

The initial setup is done through the <code>gradlew setup</code> task. It will run the SetupMCP tasks and then start applying the Forge system to the processed vanilla code. After the MCPConfig/SetupMCP tasks are finished, ForgeGradle will print '''MCP Environment Setup is complete''' and continue. The text '''pausing after requested step''' is also printed twice during this task such that some necessary data can be extracted.

First, it applies ATs. After that, patches. Finally, the official mappings, or some other mappings from a provider like Parchment, are applied.

First, it applies ATs. After that, patches. Finally, the official mappings, or some other mappings from a provider like Parchment, are applied.