Handful of `Dictionary`s somewhere to centralize "entity group" storage (one for each `Entity` type)

Description

See title. That would literally be as simple as something like:

public class ModContent {
	private static IDictionary<string, IReadOnlyList<int>> _ItemGroups;
	public static IReadOnlyDictionary<string, IReadOnlyList<int>> ItemGroups { get; private set; }

	static ModContent() {
		_ItemGroups = new ConcurrentDictionary<string, IReadOnlyList<int>>();
		ItemGroups = new ReadOnlyDictionary<string, IReadOnlyList<int>>( _ItemGroups );
	}

	public static void AddToItemGroup( string groupName, IEnumerable<int> group ) {
		if( !_ItemGroups.ContainsKey( groupName ) ) {
			_ItemGroups[groupName] = group.ToList().AsReadOnly();
		} else {
			_ItemGroups[groupName] = _ItemGroups[groupName].Union( group ).ToList().AsReadOnly();
		}
	}

	...
}

What does this proposal attempt to solve or improve?

A place for mods to look for, and contribute to, listings of entities (by their type field’s value) by a given name (e.g. any ‘spooky’ NPC, any explosive item, etc.).

[Chicken-Bones]

Basically ore dictionary from minecraft forge. Yes

[hamstar0]

That works if all mods had a reference to the ItemFlammableTag class, but that might not always be the case with a crowd sourced list. If a system like that were added, the group definitions would have to exist in tModLoader.

No, you misunderstood the concept. That class is just a local shortcut, it does not define a tag, it’s like a ref to data of such tag.

Is TagData<TagShortcut>() meant to be a constructor call? This looks unfamiliar to me.

The parenthesis was a typo, replaced the link.

Alright, but if I’m understanding this correctly, entity group data is mapped to that (generic) class type. The generic parameter is the class that would need to be mod-agnostic, AKA stored in tModLoader or else expected as a mod dependency.