No. The random selection will only include admin models if it's an admin, but not guarantee that a admin model is selected. Currently, using one public and one admin-only class is the only way to do it.
However, this thread seems good to discuss how I should make this possible in the next release.
In addition to a improved authentication system, I'm going to make model collections. Then there can be custom model collections for various categories (admin models, vip, public, etc.). You can even make a collection per class so that each class can have their own set of models.
A collection will
- have a unique name
- have one or more references to models (names)
- belong to a team (zombies, mother zombies or humans)
I'm wondering how I should apply this to classes. Theres already a model attribute in class settings, so this could be expanded to a list format. That list could accept model names, some predefined options and collections. The technical syntax might look like this:
Code:
Syntax:
<option> | {<filter> | <model> | c:<collection> | <filter:collection>} ...
Options:
default | no_change
Filters:
random | random_public | random_admin | random_mother_zombie
This should make it possible to
- use a option to use default CS:S models or not change model at all
- use a filter to select any model from the global model list (as in beta2)
- apply one or more models
- apply one or more collections
- apply filters to individual collections
- give priority to entries where first entry get highest priority
This is flexible. But maybe not that user friendly unless we give enough examples.
The first post is a good example; assign admin models to admins and regular models to others in one class. That will need at least one collection of admin models. Then it might look like this:
Code:
c:MyAdminModels random_public
It would attempt to assign a admin model if player is admin or select a random public model otherwise.
Though I see a weakness in my idea, it doesn't fall back to a default. If you remove random_public it won't have a model to apply on regular players. But maybe that's how it should act, and just log a warning instead.
__________________