Main Page - Revision history

Argony: /* Specifying 'this object' */

2025-07-08T01:58:53Z

Specifying 'this object'

← Older revision		Revision as of 18:58, 7 July 2025
Line 620:		Line 620:
	=== Specifying 'this object' ===		=== Specifying 'this object' ===

	'''__ARGON_THIS_OBJECT__''' is a special string. When any reference name is set to '__ARGON_THIS_OBJECT__', the import script will set the reference using the ~~target~~ object.		'''__ARGON_THIS_OBJECT__''' is a special string. When any reference name is set to '__ARGON_THIS_OBJECT__', the import script will set the reference using the current object; in other words, the object to which the custom component is attached.

	[[File:MFTrainStationBle_This.jpg]]		[[File:MFTrainStationBle_This.jpg]]

2025-07-08T01:55:51Z

How to Define Custom Components

← Older revision		Revision as of 18:55, 7 July 2025
Line 572:		Line 572:

	The definition should contain the following key-values:		The definition should contain the following key-values:
	* '''default''': an object that defines ~~what fields~~ the fields to be set; (more details below).		* '''default''': an object that defines the fields to be set; (more details below).
	* '''hint''': must always be the string "CUSTOM_COMPONENT"		* '''hint''': must always be the string "CUSTOM_COMPONENT"
	* '''help''': an explanation of what the component does		* '''help''': an explanation of what the component does

2025-07-08T01:52:04Z

Installation

← Older revision		Revision as of 18:52, 7 July 2025
Line 17:		Line 17:
	== Installation ==		== Installation ==

	* Follow ~~the instructions under '''Installation''' on the~~ [https://github.com/Argon-ops/argon-slim ~~github~~ repository's main page] ~~(just clone into your Assets folder)~~		* Follow [https://github.com/Argon-ops/argon-slim these instructions under '''Installation''' on the Argon repository's main page]
	<span id="adding-properties-to-objects"></span>		<span id="adding-properties-to-objects"></span>

2025-07-08T01:51:04Z

Installation

← Older revision		Revision as of 18:51, 7 July 2025
Line 17:		Line 17:
	== Installation ==		== Installation ==

	* ~~Install~~ the ~~package using the Unity Package Manager~~ '''or''' ~~from~~ the ~~repo hosted~~ [https://github.com/Argon-ops/argon-slim ~~here~~] (just clone into your Assets folder)		* Follow the instructions under '''Installation''' on the [https://github.com/Argon-ops/argon-slim github repository's main page] (just clone into your Assets folder)
	* Open Blender and open a Preferences view
	* Go to Add-ons
	* Click the ‘Install…’ button
	* Find and install Argon_Plugin.zip under Resources/Blender
	* The Argon plugin activation box should come into view (possibly after several seconds)
	* Click the check box to activate it
	* You should see a new tab on the right side of your 3D views in Blender that is titled ‘Argon’ (Press ‘n’ if you don’t see any right side tabs)

	<span id="adding-properties-to-objects"></span>		<span id="adding-properties-to-objects"></span>

2025-05-01T15:14:27Z

Installation

← Older revision		Revision as of 08:14, 1 May 2025
Line 17:		Line 17:
	== Installation ==		== Installation ==

	* Install the package using the Unity Package Manager or from the repo hosted [https://github.com/Argon-ops/argon-slim here]		* Install the package using the Unity Package Manager '''or''' from the repo hosted [https://github.com/Argon-ops/argon-slim here] (just clone into your Assets folder)
	* Open Blender and open a Preferences view		* Open Blender and open a Preferences view
	* Go to Add-ons		* Go to Add-ons

2025-05-01T15:13:19Z

Installation

← Older revision		Revision as of 08:13, 1 May 2025
Line 17:		Line 17:
	== Installation ==		== Installation ==

	* Install the package using the Unity Package Manager		* Install the package using the Unity Package Manager or from the repo hosted [https://github.com/Argon-ops/argon-slim here]
	* Open Blender and open a Preferences view		* Open Blender and open a Preferences view
	* Go to Add-ons		* Go to Add-ons

2025-05-01T15:08:39Z

More About Exporting:

← Older revision		Revision as of 08:08, 1 May 2025
Line 99:		Line 99:
	[[File:Correct-rotation.jpg\|180px\|Correct rotation]]		[[File:Correct-rotation.jpg\|180px\|Correct rotation]]

	Correct rotation: If this option is checked, Argon will use EdyJ’s export script to fix rotations before exporting. This sometimes fixes rotation issues in the file. Use on a case-by-case basis.		Correct rotation: If this option is checked, Argon will use EdyJ’s export script to fix rotations before exporting. This sometimes fixes rotation issues in the file. Use on a case-by-case basis.
	<span id="properties"></span>		<span id="properties"></span>

2025-04-18T14:56:00Z

About Component and GameObject References

← Older revision		Revision as of 07:56, 18 April 2025
Line 620:		Line 620:
	In MFTrainStation, the last default field '''_exit''' is a Component reference.		In MFTrainStation, the last default field '''_exit''' is a Component reference.

	In Blender, the game designer can replace '''<game-object-name>''' with the name of an object that owns an'''MFTrainStationExit''' component.		In Blender, the game designer can replace '''<game-object-name>''' with the name of an object that owns an '''MFTrainStationExit''' component.

	[[File:MFTrainStationBle2.jpg]]		[[File:MFTrainStationBle2.jpg]]

2025-04-18T14:54:35Z

Custom Component Types

← Older revision		Revision as of 07:54, 18 April 2025
Line 590:		Line 590:
	* any primitive type		* any primitive type
	* any reference to another Component or GameObject that will exist along side this one including this object itself at import time. (In other words, any object in the same FBX file; any object in your current scene in Blender, in most cases).		* any reference to another Component or GameObject that will exist along side this one including this object itself at import time. (In other words, any object in the same FBX file; any object in your current scene in Blender, in most cases).

			=== About Component and GameObject References ===

	In the case of references to components or gameobjects, the value you supply should be the string name of the object.		In the case of references to components or gameobjects, the value you supply should be the string name of the object.
Line 615:		Line 617:

	The class just has to be defined somewhere in your project.		The class just has to be defined somewhere in your project.

	~~=== Component and GameObject References ===~~

	In MFTrainStation, the last default field '''_exit''' is a Component reference.		In MFTrainStation, the last default field '''_exit''' is a Component reference.

2025-04-18T14:50:25Z

How to Define Custom Components

← Older revision		Revision as of 07:50, 18 April 2025
Line 580:		Line 580:

	The definition should contain the following key-values:		The definition should contain the following key-values:
	* '''default''': an object that defines what fields ~~will~~ be set; (more details below).		* '''default''': an object that defines what fields the fields to be set; (more details below).
	* '''hint''': must always be the string "CUSTOM_COMPONENT"		* '''hint''': must always be the string "CUSTOM_COMPONENT"
	* '''help''': an explanation of what the component does		* '''help''': an explanation of what the component does