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

(feature request) more choices for the location of the .ent file #135

Open
Kinnuu opened this issue Apr 6, 2023 · 1 comment
Open

(feature request) more choices for the location of the .ent file #135

Kinnuu opened this issue Apr 6, 2023 · 1 comment

Comments

@Kinnuu
Copy link

Kinnuu commented Apr 6, 2023

Currently I have to store my entity definitions file deep inside the folder structure of the NetRadiant Custom install. This isn't particularly convenient, since it's not just that one install of NRC that might want to use my ent file. I would prefer NRC to search for the ent files in other folders if it can't find it in there.

If having an option to specify an explicit custom folder for the ent file is a step too far, what about something like...

Let's say my mod is called "mymod" Currently, NRC only tries to use the ent file in (e.g.)
C:\netradiant\netradiant-custom-win64\netradiant-custom-20210105\q1.game\mymod

I would suggest if it cannot find it there, look for it in
[Engine Path]\mymod

..and then if it cannot find it there, look for it in
[Extra Resource Path]\mymod

Obviously this is just a suggestion and there's a million other ways of doing this, but essentially I just want to be able to keep my ent file in a folder of my own choosing, since I have quite a few other tools that use it.

@Garux
Copy link
Owner

Garux commented Apr 6, 2023

Old way (1.4) of ent defs storing in radiant was in mod/scripts/, which wasn't robust to random entdef file drops.
I think having customization of each entdef file path would be nice, also control of the entdef loading order, as atm it follows implicit rules.

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

2 participants