|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002054||OpenClonk||Engine||public||2019-03-31 08:01||2019-03-31 08:09|
|Priority||normal||Severity||feature||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0002054: Feature request: Register custom OCFs|
|Description||Made a separate issue for the OCF proposal from https://bugs.openclonk.org/view.php?id=1384|
We could also remove OCF and replace it with these custom bits. In fact the features could be separated and work like this:
static OCF_Prey = RegisterOCF("Prey");
static OCF_Monster = RegisterOCF("Monster");
RegisterCrossCheck(OCF_Monster, OCF_Prey, "OnHitPrey");
It could even be made downwards compatible with some of old OCFs like OCF_Alive, and also work in FindObject(Find_OCF(...)).
|Tags||No tags attached.|
I am not sure about the gain of this. Yes, it allows to create custom OCFs, but what is the difference between those and a property (yes, there is a difference implementation-wise)?
After all, either is just a boolean flag (well, properties can be of other types, too). Also, I'd imagine that the amount of custom OCFs could increase very fast in a custom pack?
|2019-03-31 08:01||Marky||New Issue|
|2019-03-31 08:02||Marky||Relationship added||related to 0001384|
|2019-03-31 08:09||Marky||Note Added: 0006212|