Skip to content

fix(esx_lib): load imports from the correct resource name#1809

Open
ASTROWwwW wants to merge 1 commit into
esx-framework:v1.14.1from
ASTROWwwW:fix/esx-lib-resource-name
Open

fix(esx_lib): load imports from the correct resource name#1809
ASTROWwwW wants to merge 1 commit into
esx-framework:v1.14.1from
ASTROWwwW:fix/esx-lib-resource-name

Conversation

@ASTROWwwW

@ASTROWwwW ASTROWwwW commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Description

xLib.name was "xLib", which is not a resource, so the import metatable fed it to LoadResourceFile and resolved nothing: silent on Legacy, a hard error on Enhanced. Points it at the real resource name. Boots clean on both.

PR Checklist

  • My commit messages and PR title follow the Conventional Commits standard.
  • My changes have been tested locally and function as expected.
  • My PR does not introduce any breaking changes.
  • I have provided a clear explanation of what my PR does.

@ASTROWwwW
ASTROWwwW force-pushed the fix/esx-lib-resource-name branch from 21ebd0f to df64e31 Compare July 22, 2026 14:19
@Zykem
Zykem changed the base branch from main to v1.14.1 July 23, 2026 22:55
xLib.name was "xLib", which is not a resource, so the import metatable fed it to LoadResourceFile and resolved nothing. It failed silently on Legacy and hard-errored on Enhanced (Resource 'xLib' not found). Point it at the real resource name.
@ASTROWwwW
ASTROWwwW force-pushed the fix/esx-lib-resource-name branch from df64e31 to 477b713 Compare July 26, 2026 22:25
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

Successfully merging this pull request may close these issues.

1 participant