|
Ideally, it would just be the memory taken by of a couple if extra data-gathering functions. They'd only get called if you asked for them to, so there'd be no runtime overhead as long as you use all the results you ask for. Of course, if you ask for the gear just to look at their weapon(s), then there'd be some overhead there. My example above is a bad one in this regard, but it shows the simplicity of using it.
Note that I would be adding functions to the library's API, not changing the existing ones. You'd still have the option of doing it yourself.
Option 1:
Use the existing API, do all the data-gathering work yourself.
Option 2:
Use the API I proposed, have an easier time of it at the possible expense of a little more gathering overhead (if you don't use the full talent tree, for example).
Option 3:
Use the proposed API, but only request the bits you need all of and do the rest yourself.
|