CfgVehicles Config Reference – Talk
Jump to navigation
Jump to search
m (hidden selections) |
No edit summary |
||
| Line 1: | Line 1: | ||
I doubt that the hidden selections array has anything to do with actions. It just defines (together with the cfgModels) which selections on the model can be changed by using setObjectTexture. | I doubt that the hidden selections array has anything to do with actions. It just defines (together with the cfgModels) which selections on the model can be changed by using setObjectTexture. | ||
>i've probaly badly worded that 1. | |||
i noticed eg, that all soldiers can {medic} while the medic cannot. | |||
so i'll reword it (or you can please) | |||
--[[User:Raedor|Raedor]] 22:17, 2 July 2006 (CEST) | --[[User:Raedor|Raedor]] 22:17, 2 July 2006 (CEST) | ||
| Line 7: | Line 13: | ||
--[[User:Raedor|Raedor]] 22:25, 2 July 2006 (CEST) | --[[User:Raedor|Raedor]] 22:25, 2 July 2006 (CEST) | ||
>you're right. access does that. private just stops createVehicle afaik | |||
Revision as of 13:27, 3 July 2006
I doubt that the hidden selections array has anything to do with actions. It just defines (together with the cfgModels) which selections on the model can be changed by using setObjectTexture.
>i've probaly badly worded that 1.
i noticed eg, that all soldiers can {medic} while the medic cannot.
so i'll reword it (or you can please)
--Raedor 22:17, 2 July 2006 (CEST)
Again me :) Are you sure that you can't inherit private classes from other configs? I thought the only difference to protected is the fact that you can't createVehicle it... but never tested it, though.
--Raedor 22:25, 2 July 2006 (CEST)
>you're right. access does that. private just stops createVehicle afaik