OpenClonk Bugtracker - OpenClonk
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001977||OpenClonk||Engine||public||2018-01-13 09:12||2018-01-13 10:53|
|Priority||normal||Severity||feature||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0001977: Feature request - Specify locations of Material.ocg for scenarios|
|Description||I want to be able to specify the location of Material.ocg in Scenario.txt, and also allow subfolders for material. Requirements:|
* Reuse existing material definitions without copying them. At the moment I have two choices: 1) Create the material in Folder.ocf/Material.ocg - now, if another user creates an object pack and they want to use the materials, they have to copy them? 2) Create the material in Pack.ocd/Material.ocg - now, all scenarios that use Pack.ocd potentially overwrite the material definition?
* Create multiple material sets (Material.ocg/Industrial.ocg, Material.ocg/Rural.ocg) in one folder, for grouping them and setting them to different themes.
* For the purpose of overloading materials, I'd like to be able to specify the "default/source material" => this must be a complete material set that does not overload definitions or textures; as well as an "overload material" => this is optional, but must be a set that overloads textures or definitions.
Maybe this is possible already, but should be documented as such. I am thinking of the "DefinitionX" entries in Scenario.txt and the option to include/exclude specific definitions:
Theoretically, I could make a MaterialCollection.ocd/Industrial.ocd/Material.ocg, and MaterialCollection.ocd/Rural.ocd/Material.ocg and then import those into the scenario.
|Tags||No tags attached.|
|2018-01-13 09:12||Marky||New Issue|
|2018-01-13 10:53||Caesar||Note Added: 0006046|
|2018-01-13 10:53||Caesar||Note Edited: 0006046||bug_revision_view_page.php?bugnote_id=6046#r1358|