Requirement ID naming convention

Maddremor · 2017-07-31T08:00:34.000Z

I’m looking at adding more requirement lists to the game. However, there is no current ID naming convention to differentiate reqs from singular items, and I feel that that could lead to confusion down the road. Would a suffix in the ID, such as something_type, something_like, or something_req be suitable for a item requirement list?

kevin.granade · 2017-08-01T01:37:45.000Z

They’re already typed values, both in json and in the game code. Naming scenes are fragile and a pain to maintain.

Coolthulhu · 2017-08-01T02:04:53.000Z

They’re currently set apart by their inclusion method.
Similar to how item groups and individual items are applied with different tag (“item” vs “group”).

Maddremor · 2017-08-01T09:42:35.000Z

To clarify, I don’t propose making the reqs. ID semantic (codewise), rather sidestep getting a thesaurus to come up with good ID names. For example, nail_req being nail-like things instead of trying to find a good, unused synonym for nail.