by mhughes2k on Mon Oct 19, 2009 11:09 am
There is an imaginary construct in existence here...namely the "Player-Character". The player-character is in SIMPLE is no specific thing. If you have simulation (instance) (which is created from a blueprint within a Project) then there is an implied "Player-Character" but we've never explicity said *who* that is.
So here goes...
Each blueprint represents the process/workflow/experience of A SINGLE PLAYER-CHARACTER. Now that player (dropping Character from now on) can be:
1)a single physical entity e.g. Joe bloggs the Lawyer.
2)a compound physical entity. e.g. Linklaters the law firm.
For the purposes of designing the simulation blueprint it doesn't matter.
When it comes to *playing* the simulation it becomes a little problematic. In case (1) its pretty easy, there would normally be a 1-to-1 mapping of the Player to a single user.
In case (2) you *may* have multiple users allocated to the "firm".
Underlying this SIMPLE allows this to be implemented in a number of ways:
You can allocate a single user account to a simulation and you have case (1).
You can allocate multiple, individual user accounts and you have case (2).
-or-
You can create a group (comprising of multiple individual accounts) and allocate them to a simulation. This implements case (2).
Now this is fine for student-level users, adding any account to a simulation by any means makes them a "student" and they only have the basic Player tools.
But when you add a user or group to a simulation you *can* change the rights that that it has on the simulation you are adding to. This is the basic premise for making users into "staff" users.