Re: More flexible "key" type areas.
Posted: Thu Oct 03, 2013 7:41 am
Just an update, this feature was merged by Oskar this morning in the official AT code !
I am proud to now be a contributor to AT !
Many things changed since the explanations I gave, thanks to Oskar's feedback. Most notably the format, as the area name is now useless (and can be used as a meaningful comment/description of the area), and the requirement is defined using three properties : "requireType", "requireId", and "requireValue".
"requireType" field is one of the following :
questProgress
questLatestProgress
inventoryRemove
inventoryKeep
wear
skillLevel
killedMonster
timerElapsed
usedItem
spentGold
consumedBonemeals
So far there is no way to require for examples BMP consumption to be less than requireValue, but requirement negation will be implemented soon !
I am proud to now be a contributor to AT !
Many things changed since the explanations I gave, thanks to Oskar's feedback. Most notably the format, as the area name is now useless (and can be used as a meaningful comment/description of the area), and the requirement is defined using three properties : "requireType", "requireId", and "requireValue".
"requireType" field is one of the following :
questProgress
questLatestProgress
inventoryRemove
inventoryKeep
wear
skillLevel
killedMonster
timerElapsed
usedItem
spentGold
consumedBonemeals
So far there is no way to require for examples BMP consumption to be less than requireValue, but requirement negation will be implemented soon !