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

Region and node names mismatch lsx lsf #255

Closed
MANOLOV02 opened this issue Jun 21, 2024 · 2 comments
Closed

Region and node names mismatch lsx lsf #255

MANOLOV02 opened this issue Jun 21, 2024 · 2 comments

Comments

@MANOLOV02
Copy link

Hi. I am creating a resource with a single region which has one name and its root node has other “actionresourcepoint” as region name and “root” as node name.
I add a new region with .name=“root” and .RegioName=“ActionResourcePoint” then add it to the resource using .add method.
when I write the resource in .lsx everything is ok however if I write it in .lsf both the region name and the root node has “root” as a id (same resource saved two times in each format).
What I am doing wrong or is it a saving error?
I Iam using resourceutils.Save method for both

@MANOLOV02
Copy link
Author

Did the following test also to be sure I did not made a mistake.

  1. Wrote the resource as lsx (everything ok, region id saved as actionrsourcepoint and root node id as root) using resourceutils.save
  2. Read the lsx file into a new resource using resourceutils.load
  3. Saved the resource loaded as lsf without changing anything using resourceutils.save
  4. Load the lsf resource, the region id changed to root as well as the node remains as root.

other tests I did
I used the conveter after step 1) to convert the right lsx to lsf then used it again to convert back from lsf to lsx and again the region id changed to root

Ps: your lslib is amazing!!!

@MANOLOV02
Copy link
Author

Never mind. It must be left as lsx and not converted to lsf for BG3 modding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant