upd: custom component documentation

Author: pascal541

content/docs/extension-docs/custom-components.md

@@ -73,6 +73,9 @@ interface TemplateContext {
 	dialogueScene: (sceneDefinition: any, openDialogue = true) => void
 	onActivated: (eventResponse: any) => void
 	onDeactivated: (eventResponse: any) => void
+	lootTable: (lootTable: any) => string
+	tradeTable: (tradeTable: any) => string
+	spawnRule: (spawnRule: any) => void
 }
 ```
 
@@ -97,6 +100,15 @@ interface TemplateContext {
 -	`dialogueScene(sceneDefinition: any, openDialogue?: boolean): void`
 	Creates a new dialogue scene to be used within your add-on. This function is only available if your project target version is at least "1.17.40"
 
+-	`lootTable(lootTable: any): string`
+     Returns a string that points to your defined loot table
+
+-	`tradeTable(tradeTable: any): string`
+     Returns a string that points to your defined trade table
+
+-	`spawnRule(spawnRule: any): void`
+     Creates a new spawn rule file for entities that use the custom component
+
 #### Item
 
 ```ts
@@ -131,6 +143,8 @@ interface TemplateContext {
 			condition?: string | false
 		) => void
 	}
+	lootTable: (lootTable: any) => string
+	recipe: (recipe: any) => void
 }
 ```
 
@@ -148,6 +162,12 @@ The `player` object gives access to these functions:
 -   `create(template: any, location?: string): void`
     Allows you to create data inside of the player. `template` should be a JavaScript object of the data to merge into the player behavior file at the given `location`. `location` should be a path separated by `'/'` to where you want the `template` to be created. For example: `minecraft:entity/description`. The default merge behaviour can optionally be overridden with `operation` which should be a function that takes default merge function `deepMerge`, the data at `location` (`oldData`) and the new data being merged in (`newData`). It should return the result of the custom merge. For example: `(deepMerge, oldData, newData) => newData` will overwrite the data at `location`.
 
+-	`lootTable(lootTable: any): string`
+     Returns a string that points to your defined loot table
+
+-	`recipe(recipe: any): void`
+     Creates a new recipe for items that use the custom component
+
 #### Block
 
 ```ts
@@ -168,6 +188,8 @@ interface TemplateContext {
 	projectNamespace: string
 	onActivated: (eventResponse: any) => void
 	onDeactivated: (eventResponse: any) => void
+	lootTable: (lootTable: any) => string
+	recipe: (recipe: any) => void
 }
 ```
 
@@ -180,6 +202,12 @@ interface TemplateContext {
 -	`onDeactivated(eventResponse: any): void`
 	Trigger an event reponse whenever your component gets removed from this block
 
+-	`lootTable(lootTable: any): string`
+     Returns a string that points to your defined loot table
+
+-	`recipe(recipe: any): void`
+     Creates a new recipe for blocks that use the custom component
+
 ### Creating Files
 
 Files can also be automatically created with custom components. Functions that can be called to create files are: