[Bug]: In multi-project workspace, mod config gets generated under {mod}/src/main/resources directory

[ItsVerday]

Plugin Version

1.0.35

Hytale Version

0.5.2

Stacktrace

N/A, not an error

Describe the bug

When running my dev server with the runAllMods task, my plugin Renode creates a config file, which is supposed to go under {runDir}/mods/{modConfigFolder}/config.json. Because of the symlinking the gradle plugin performs, the config ends up at renode/src/main/resources/config.json (Renode is the name of my Library plugin). I would expect it to just appear under the mod config directory in the dev server directory, but the symlinking breaks this expectation.

To Reproduce

1. Have a mod in a multi-mod workspace that creates/saves a config file.
2. Run dev server with runAllMods.
3. The config.json file appears in the wrong location, as described above.

[AzureDoom]

Do you have your project here on git I can pull as a test bed to ensure I'm working with the same setup as you. I assume your runDir is your host project just to confirm.

[ItsVerday]

Yes, the project is at https://github.com/ItsVerday/Hytale_Worldgen_Mods. I have not configured my runDir to anything different than the default.

[AzureDoom]

Perfect, thank you. I'll poke this here now as past 4pm EST today, I'll be off the Hytale grind for about a week haha

[AzureDoom]

Actually was easier than I thought haha

Mind testing with 1.0.36-alpha.1 on your end. You'll need to update your settings.gradle to include:

pluginManagement {
    repositories {
        gradlePluginPortal()
        mavenCentral()
        maven {
            name = 'AzureDoom Maven'
            url = uri("https://maven.azuredoom.com/mods")
        }
    }
}

plugins {
    id("org.gradle.toolchains.foojay-resolver-convention") version "1.0.0"
}

But it should now only properly save the config to the runs folder and not the renode/src/main/resources/ folder.

[ItsVerday]

Yep, that fixed the issue for me! Thanks for the quick response and turnaround time!

[AzureDoom]

No problem! I'll have it out an non-alpha here in a bit, fixing some other cache related issues for gradle with this as well.