Unable to access nested module

[RayBenefield]

Please select what you are reporting on:

Verse

What Type of Bug are you experiencing?

Verse

Summary

Creating multiple layers of modules results in access issues.

Steps to Reproduce

• Have the following directory structure:

• device.verse
• TopLevelModuleFolder
  • SubLevelModuleFolder
    • fileInModule.verse

• Add using { TopLevelModuleFolder.SubLevelModuleFolder } to device.verse

Expected Result

Should be able to access things in fileInModule.verse

Observed Result

fileInModule.verse cannot be accessed due to being “internal” to TopLevelModuleFolder

Platform(s)

PC

Additional Notes

There is no way to affect the module access level and change it to public if the module is defined by directory structure. Ideally, I can set both the TopLevelModuleFolder and the SubLevelModuleFolder to both be public somehow, allowing all files in each directory to be easily accessed.

I’ve attempted to add a TopLevelModuleFolder.verse with TopLevelModuleFolder<public> := module {} but that results in an “ambiguous” definition with the folder itself.

[t.tutiya]

Additional info.

How to use a nested folder's module in Verse?

Hi. How to access a nested folder’s module in Verse? For example, if I want to access a module in Sub3.verse placed in the Sub1/Sub2 folder, how should I write the using clause? Unfortunately, the code below did not work. using { /Fortnite.com/Devices } using { /Verse.org/Simulation } using { /UnrealEngine.com/Temporary/Diagnostics } using { Sub1} using { Sub2} #Invalid access of internal module `(/localhost/MyProject230520/Sub1:)Sub2` using { Sub1.Sub2} #Invalid access of in…

[RayBenefield]

Yep the problem is still a bug and should still be addressed. But thank you for referencing the other threads on this.