Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OE - Add list of loaded objects per package/level #36

Open
juso40 opened this issue Jul 17, 2023 · 1 comment
Open

OE - Add list of loaded objects per package/level #36

juso40 opened this issue Jul 17, 2023 · 1 comment
Labels
enhancement New feature or request target-1.5.0 Possible 1.5.0 target?

Comments

@juso40
Copy link

juso40 commented Jul 17, 2023

As a mod author, I would like to know what objects are loaded at all times.
For this, a list of packages/levels in each object's dump could be useful. Obviously, this would need a few blacklisted objects, e.g., SkillsDefinition, Meshes, Materials... that are only part of a character package.

Another nice addition would be to allow filtering for certain packages in the search.
For example: inclass:SkillDefinition package:Sanctuary_P
This would search for only SkillDefinitions that are loaded in Sanctuary. Similar, this could be expanded to allow for a list of packages or even for All which would need to internally match all level packages to work correctly.

@juso40 juso40 added the enhancement New feature or request label Jul 17, 2023
@apocalyptech apocalyptech added the needs investigation Still need to nail down exactly what the issue is label Aug 4, 2023
@apocalyptech
Copy link
Contributor

Eesh, this has been three weeks, eh? Sorry for the delay; I got caught up on font-scaling issues which took a hell of a lot longer than expected, and didn't want to interrupt my flow lest I lose steam on it.

Anyway, yeah, I agree -- this'd be a cool addition. I don't think I've got the brainpower/time for it at the moment, but I'll leave this open. Perhaps for a v1.5.0? I was thinking about some other datalib improvements for 1.5.0 as well, so it might make sense to do all that at the same time.

@apocalyptech apocalyptech added the target-1.5.0 Possible 1.5.0 target? label Aug 4, 2023
@apocalyptech apocalyptech removed the needs investigation Still need to nail down exactly what the issue is label Aug 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request target-1.5.0 Possible 1.5.0 target?
Projects
None yet
Development

No branches or pull requests

2 participants