Editor loading paths

[RaideX]

I know this has probably been asked quite a lot and this is probably just due to my fussiness but i'd like to let the amnesia editors (i.e. the leveleditor) load from custom directories as i'm currently working on a total conversion and i'd like to keep my custom meshes and entities in the sub folder of this conversion instead of moving them to the static_objects folder in the main directory. Is there anyway to bypass that behavior of the leveleditor? If so i'd be glad to receive answers.

-RaideX

[PutraenusAlivius]

Put the directory of the custom directories into the main Resources.cfg.

[RaideX]

Put the directory of the custom directories into the main Resources.cfg.

I've already done that ofcourse. Let me just try to higher the priority by putting it to the top of the list.

EDIT: Nope, that did not fix it.

[MsHannerBananer]

Well, I know it's not that great of a fix, and may not be exactly what you want, but you can make a custom folder in said static_object and entities folders inside the Amnesia directory (As an example, it would look something like this-> Amnesia: The Dark Descent/entities/YOUR CUSTOM FOLDER NAME HERE).

For the Full/Total Conversion I'm working on, that's the setup I have, because that's the easiest way to keep track of your custom entities and whatnot. I know it's not the greatest fix, but that's really the only way you can access your stuff in the level editor. As far as the other editors are concerned, you can simply open an entity from any directory you choose.

Once you have all the entities (and static_objects, etc) you want and need in your custom folders, you just copy and paste those custom folders them to the entities folder of your TC so that the engine can find them when people download your project.

I hope that makes sense, if not, I can make a video or something, haha.

I actually don't think there's a solid way of 'bypassing' this kind of thing. The level editor can only look in certain directories, and I think that's something that's scripted into the program itself. Looking at the program now, there doesn't seem to be anything that would allow you to change the directories the level editor accesses, so the way I described above would be the only way really. :/

[ExpectedIdentifier]

Open MainEditorSettings.cfg which is in your Amnesia directory. You can set the directories for static objects, entities and stuff like that there like this:

StaticObjectsDir="ModFolder/static_meshes"

[RaideX]

Well, I know it's not that great of a fix, and may not be exactly what you want, but you can make a custom folder in said static_object and entities folders inside the Amnesia directory (As an example, it would look something like this-> Amnesia: The Dark Descent/entities/YOUR CUSTOM FOLDER NAME HERE).

For the Full/Total Conversion I'm working on, that's the setup I have, because that's the easiest way to keep track of your custom entities and whatnot. I know it's not the greatest fix, but that's really the only way you can access your stuff in the level editor. As far as the other editors are concerned, you can simply open an entity from any directory you choose.

Once you have all the entities (and static_objects, etc) you want and need in your custom folders, you just copy and paste those custom folders them to the entities folder of your TC so that the engine can find them when people download your project.

I hope that makes sense, if not, I can make a video or something, haha.

I actually don't think there's a solid way of 'bypassing' this kind of thing. The level editor can only look in certain directories, and I think that's something that's scripted into the program itself. Looking at the program now, there doesn't seem to be anything that would allow you to change the directories the level editor accesses, so the way I described above would be the only way really. :/

yep. that was the workaround that I've been using. I guess there really is no other way. Though there is a config file named MainEditorSettings.cfg in the main directory, it doesn't seem to do anything as it resets itself after opening a editor. Thanks for the clarification though.

[ExpectedIdentifier]

Well, I know it's not that great of a fix, and may not be exactly what you want, but you can make a custom folder in said static_object and entities folders inside the Amnesia directory (As an example, it would look something like this-> Amnesia: The Dark Descent/entities/YOUR CUSTOM FOLDER NAME HERE).

For the Full/Total Conversion I'm working on, that's the setup I have, because that's the easiest way to keep track of your custom entities and whatnot. I know it's not the greatest fix, but that's really the only way you can access your stuff in the level editor. As far as the other editors are concerned, you can simply open an entity from any directory you choose.

Once you have all the entities (and static_objects, etc) you want and need in your custom folders, you just copy and paste those custom folders them to the entities folder of your TC so that the engine can find them when people download your project.

I hope that makes sense, if not, I can make a video or something, haha.

I actually don't think there's a solid way of 'bypassing' this kind of thing. The level editor can only look in certain directories, and I think that's something that's scripted into the program itself. Looking at the program now, there doesn't seem to be anything that would allow you to change the directories the level editor accesses, so the way I described above would be the only way really. :/

yep. that was the workaround that I've been using. I guess there really is no other way. Though there is a config file named MainEditorSettings.cfg in the main directory, it doesn't seem to do anything as it resets itself after opening a editor. Thanks for the clarification though.

Make sure the level editor is closed, save the changes to MainEditorSettings.cfg, then re-open the level editor.

[RaideX]

Make sure the level editor is closed, save the changes to MainEditorSettings.cfg, then re-open the level editor.

The non-custom static_objects would then not load, am i right?

That would cause problems too.

[Mudbill]

I'd say it's best to just keep your custom folder inside /static_objects and /entities until you export your mod. Move them to your own folders and the game will load them fine if the paths are within the resources.cfg file. You'll have access to everything. Since it only requires moving the files once I don't think it's tedious or annoying.