Articles

I’ve continued updating UnitySteer as we work on our game (eating our own dogfood, as they say), and I wanted to poll the community a bit in case anyone has objections to some upcoming changes.

1) Remove CharacterMotorVehicle and CharacterMotorVehicleEditor.

These classes depend on Unity’s CharacterMotor, which is included on the Standard Assets as a Unity script class. We’ve translated it to C# and are iterating over it to do some changes here and there, but part of this is that the naming conventions no longer match those used by Unity on the original. I’d rather remove it from the main repository than have in it something that will introduce noise for the majority of users (who may not even care about that particular behaviour).

2) Change the radar collections to C5.

The C5 collections are still better designed than the .Net ones, even on 3.5. For instance, List(T) has a Find method, but IList(T) doesn’t. List(T).AsReadOnly returns an IList, which means you can’t do .Find on it. So if you’d like to have that, you have to forget about the safety net of AsReadOnly, and end up writing to the implementation.

C5 allows us to return a GuardedList that behaves consistent with what you would expect from List, and on top of that the collection gets us other features.

I already have these changes implemented in a local branch, but haven’t merged them to development yet.