Just to clarify: The default license for the Path system states that it is free to use in commercial and non-commercial applications as long as the logo of the app is prominently displayed in the application splash-screen.

1. What Marty said. Specifically, you’ll want to use the PlayerPrefs class which works both in standalone and Unity Web Player targets.

2. What Marty said. In addition, Emil “AngryAnt” Johansen has created a pathfinding module for Unity, which he distributes for free. Find it here: http://angryant.com/path.html

3. What Marty said. You can also write editor scripts, which /can/ modify scene or project data. Check the docs here: http://unity3d.com/support/documentation/ScriptReference/20_class_hierarchy.Editor_Classes.html

Here’s to you enjoying Unity, joining the forums, and telling all your friends

d.

My quick, and oh-so-possibly-incorrect answers to your first three open questions are as follows:

1. You will have to roll your own, but it won’t be any more difficult than writing a bunch of variables to an external file. And Unity will even allow you to save user info from a web-based Unity game now!

2. There’s no native A*, etc. but there is a great article in he current (Premiere) issue of Unity Developer Magazine describing an implementation of A* in Unity. Plus, the Unity FPS demo has a great waypoints example. And there’s plenty more discussions of these topics on the Unity forums.

3. You’d probably have to write the modified terrain data out to an external file and read it back in, but that’s no biggie in Unity. And since Unity lets you build meshes at runtime, you’ll be able to use a lot of the techniques you have probably seen used to describe terrain reliefs in Director Shockwave (i.e. datasets, grayscale maps, etc.).