Brennan Ravenscroft Shadows-of-Fire

Introduction to Eclipse Runs

Description

To launch programs within the Eclipse IDE, a configuration file known as a Run Configuration must be created, which instructs Eclipse to perform a particular action or series of actions, eventually starting the program.

Basic Information

Eclipse Run Configurations (.launch files) are XML files. Each file declares one element named launchConfiguration, which holds the data of the run config.

The launchConfiguration must declare a type attribute, where the type is any launchConfigurationType declared by Eclipse or an extension (such as Buildship).

Forge Triage Union Strike Demands

Code of Conduct

Context

In repeated instances, recently on May 28th[^1], and even more recently on June 22nd[^11][^12][^13] Lex acts as if he is above the Code of Conduct[^14].
Unfortunately, the idea is sustained by the fact that the CoC currently has the famous "Lex Clause" which allows Lex to do whatever he wants when interacting with the community and the team. This is an extremely pressing issue, as his behaviour is becoming more concerning every day, and he still is the face of Forge.

Demands

The aforementioned clause will be removed in totality. There will be absolutely no exceptions made for any member of the team or the community regarding beha

Intro

The CFG (Configuration) File Specification is a format utilized by Minecraft Mods that was originally developed by MinecraftForge. At this time, this format is no longer supported by Forge, but is still in use by a variety of mods.

This document only applies to mods utilizing the implementation that is bundled with Placebo. This document may be applicable to other implementations.

File Specification

Properties

The PCFG (Placebo Configuration) File Format is a configuration format that supports categorized key-value pairs where the keys are strings, but the values are valid JSON embedded within the document.

The file specification is as follows:

Comments

A comment is marked by a #. For any line, any text following a # will be ignored. Comments are not valid within JSON-values, but are valid after termination of those JSON-values.

Examples:

# A commented line

Port work is beginning for Apotheosis. This means a ton of things are going to be redone, looked at, touched up, or perhaps even removed. The current slate of preemptive changes thus far looks like this:

Garden Module
No real changes. The content in this module is focused solely on the growth cap changes to bamboo, sugarcane, and cacti. The way they work might change a little bit, but not in a way that would be noticable.
The psuedo-changes are because the world height is no longer capped.

Potion Module
Endless Quiver will be moving to the Enchantment Module. This has been a long time coming but the change was never made due to binary compat reasons.
Everything else (sundering, ancient knowledge, potion charms, recipes) will be staying as-is.

	---- Minecraft Crash Report ----
	// Hi. I'm Minecraft, and I'm a crashaholic.

	Time: 2023-04-14 00:08:19
	Description: Ticking entity

	java.lang.NullPointerException: Cannot invoke "net.minecraft.world.entity.npc.Villager.m_5803_()" because "this.targetVillager" is null
	at com.legacy.blue_skies.entities.ai.NightwatcherRobGoal.m_8037_(NightwatcherRobGoal.java:87) ~[blue_skies-1.19.2-1.3.20.jar%23476!/:1.3.20] {re:classloading}
	at net.minecraft.world.entity.ai.goal.WrappedGoal.m_8037_(WrappedGoal.java:65) ~[server-1.19.2-20220805.130853-srg.jar%23761!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B}
	at net.minecraft.world.entity.ai.goal.GoalSelector.m_186081_(GoalSelector.java:119) ~[server-1.19.2-20220805.130853-srg.jar%23761!/:?] {re:mixin,pl:accesstransformer:B,re:classloading,pl:accesstransformer:B,pl:mixin:APP:botania_xplat.mixins.json:GoalSelectorAccessor,pl:mixin:A}

	"string" // [Mandatory] \|\| Mojangson string representation of a Compound Tag -- See https://github.com/aramperes/Mojangson for spec

	OR

	Object // [Mandatory] \|\| Object representation of a Compound Tag, which is just write a JSON object that maps to your desired nbt.

	// A string representation of CompoundTag implies -> "nbt": "{Data:0}"
	// The object representation implies -> "nbt": { "Data": 0 }
	// Either form is valid, and the object form is easier.

	{
	"type": "string", // [Mandatory] \|\| Registry Name of the Entity Type bound to this Data Model. Only one data model may exist for a single Entity Type.
	"subtypes" [
	"string" // [Optional] \|\| An array of entity type registry names that will count towards kills for this model. Names that are invalid or not currently loaded are ignored, so you can add optional compat through this.
	],
	"name": "string", // [Mandatory] \|\| The translation key for the name of the entity within this data model. Typically it is "entity.domain.path" where domain and path are the first and second half of the Registry Name (respectively).
	"name_color": "string", // [Optional] \|\| A hex integer of the form 0xRRGGBB which determines the name color of the Data Model
	"gui_scale": float, // [Mandatory] \|\| A factor to scale the displayed entity by in the Deep Learner GUI. Must be greater than zero.
	"gui_x_offset": float, // [Mandatory] \|\| X Coordinate offset for the displayed entity in the D

	package shadows.darkohax2;

	import org.apache.logging.log4j.LogManager;
	import org.apache.logging.log4j.Logger;

	import net.minecraftforge.fml.common.Mod;

	@Mod(DarkoHaxRP.MODID)
	public class DarkoHaxRP {

	{
	"width": integer, // [Mandatory]
	"height": integer // [Mandatory]
	}

	// This one should be self explanatory, I hope...