A few months ago I was working on the ship builder functionality of the upcoming game I'm working on and around the same time I was playing around with reflection -- the ability to automatically find functions on all classes with specific attributes on them to be precise. I needed this particular feature for TNet 3: I wanted to eliminate the need to have to register RCCs (custom object instantiation functions). I added that feature without any difficulty: simply get all assemblies, run through each class and then functions of that class, then simply keep a list of ones that have a specific attribute. Implementing it got me thinking though... what if I was to expand on this idea a bit? Why not use the same approach to add certain game functionality? Wouldn't it be cool if I could right-click an object in game, and have the game code automatically get all flagged custom functionality on that object and display it somehow? Or better yet, make it interactable?
Picture this: a modder adds a new part to the game. For example some kind of sensor. Upon right-clicking on this part, a window can be brought up that shows that part's properties: a toggle for whether the part is active, a slider for its condition, a label showing how much power it's currently consuming, etc. There aren't that many types of data that can be shown. There's the toggle, slider, label... Other types may include a button (for a function instead of a property), or maybe an input field for an editable property. So how can this be done? Well, quite easily, as it turns out.
First, there needs to be custom attribute that can be used to flag functionality that should be displayed via UI components. I called it simply "GameOption":
[AttributeUsage(AttributeTargets.Field | AttributeTargets.Property, AllowMultiple = false)]
public class GameOption : Attribute
{
public MonoBehaviour target;
public FieldOrProperty property;
public virtual object value { get { return Get(target); } set { Set(target, value); } }
public object Get (object target)
{
if (target != null && property != null) return property.GetValue(target);
return null;
}
public T Get<T> () { return Get<T>(target); }
public T Get<T> (object target)
{
if (target != null && property != null) return property.GetValue<T>(target);
return default(T);
}
public virtual void Set (object target, object val)
{
if (isReadOnly || target == null) return;
if (property != null) property.SetValue(target, val);
}
}
Next, there needs to be a function that can be used to retrieve all game options on the desired type:
// Caching the result is always a good idea!
static Dictionary
<Type, List
<GameOption
>> mOptions
= new Dictionary
<Type, List
<GameOption
>>();
static public List<GameOption> GetOptions (this Type type)
{
List<GameOption> list = null;
if (!mOptions.TryGetValue(type, out list))
{
list
= new List
<GameOption
>(); mOptions[type] = list;
var flags = BindingFlags.Instance | BindingFlags.Public | BindingFlags.NonPublic;
var fields = type.GetFields(flags);
for (int b = 0, bmax = fields.Length; b < bmax; ++b)
{
var field = fields[b];
if (field
.IsDefined(typeof(GameOption
),
true)) {
GameOption opt
= (GameOption
)field
.GetCustomAttributes(typeof(GameOption
),
true)[0]; opt.property = FieldOrProperty.Create(type, field);
list.Add(opt);
}
}
var props = type.GetProperties(flags);
for (int b = 0, bmax = props.Length; b < bmax; ++b)
{
var prop = props[b];
if (!prop.CanRead) continue;
if (prop
.IsDefined(typeof(GameOption
),
true)) {
GameOption opt
= (GameOption
)prop
.GetCustomAttributes(typeof(GameOption
),
true)[0]; opt.property = FieldOrProperty.Create(type, prop);
list.Add(opt);
}
}
}
return list;
}
Of course it's even more handy to have this on the Game Object:
static public List<GameOption> GetOptions (this GameObject go)
{
return go.GetOptions<GameOption>();
}
static public List<T> GetOptions<T> (this GameObject go) where T : GameOption
{
List
<T
> options
= new List
<T
>(); MonoBehaviour[] mbs = go.GetComponents<MonoBehaviour>();
for (int i = 0, imax = mbs.Length; i < imax; ++i)
{
MonoBehaviour mb = mbs[i];
List<GameOption> list = mb.GetType().GetOptions();
for (int b = 0; b < list.size; ++b)
{
GameOption opt = list[b] as T;
if (opt != null)
{
opt = opt.Clone();
opt.target = mb;
options.Add(opt);
}
}
}
return options;
}
So now I can have a property like this in a custom class:
public class CustomClass : MonoBehaviour
{
[GameOption]
public float someValue { get; set; }
}
...and I can do this:
var options = gameObject.GetOptions<GameOption>();
foreach (var opt in options)
{
opt.value = 123.45f;
Debug.Log(opt.value);
}
Better still, I can inherit a custom attribute from GameOption and have custom code handle both the getter and the setter. I could filter exactly what kind of custom attribute is retrieved using the gameObject.GetOptions<DesiredAttributeType>() call. With the way of retrieving custom properties set, all that's left is to draw them automatically after some action.
That is actually quite trivial using NGUI. I simply registered a generic UICamera.onClick delegate, and inside it I collect the options using gameObject.GetOptions then display them using an appropriate prefab. For example
if (opt
.value is float) // draw it as a slider
I also register an event listener to the appropriate UI element itself (in the case above -- a slider), so that when the value changes, I simply set the opt.value to the new one. So there -- the mod content maker no longer needs to worry about creating custom UI elements at all. All he needs to do is mark desired fields or properties as [GameOption], and they will show up via right-click. Simple!
Of course I then went on to make it more advanced than that -- adding an optional sorting index and category values (so that the order of properties that show up can be controlled via the index, and filtered using the category). I also added support for buttons -- that is, I simply expanded the attribute to include methods:
AttributeTargets.Field | AttributeTargets.Property | AttributeTargets.Method
...and added a MethodInfo to go with the FieldOrProperty attribute as well as an Invoke() function to trigger it. I also added support for Range(min, max) property for sliders, popup lists for multiple selection drop-down lists... I can go on, but there is no need to complicate the explanation further. Point is -- this approach is highly customizable and very powerful:
C# reflection is fun!
