Asset locating in SpongeForge/Plugin development

Plugins Plugin Development
1

(I’m not sure if this is the correct forum category, it would be handy to have a plugin only category for help / support so things could be marked as solved)

So the current way I have my workspace set up in IntelliJ is probably incorrect, but I want to be able to work on SpongeForge/Common/API simultaneously as working on plugins so I can debug / possibly PR changes I believe need to be made.

When I use

 pluginContainer.getAsset("topics.conf");

The asset doesn’t seem to be found. My plugin id is

@Plugin(id = "betterhelp", name = "BetterHelp")
public class BetterHelp {

So I have stored the assets in the default directory of BetterHelp\src\main\resources\assets\betterhelp\topics.conf which I believe is the default resources / assets folder for gradle / Sponge.

There is absolutely nothing custom in my build.gradle relating to resources.

group 'au.id.rleach'
version '3.0'

apply plugin: 'java'

sourceCompatibility = 1.8

repositories {
    mavenCentral()
    maven {
        name = 'sponge'
        url = 'http://repo.spongepowered.org/maven'
    }
}

dependencies {
    testCompile group: 'junit', name: 'junit', version: '4.11'
    compile 'org.spongepowered:spongeapi:4.1.0-SNAPSHOT'
}

Before I run SpongeForge from my IDE run configuration, I must make sure that SpongeForge is depending on my plugin as a module dependency.

This allows me to debug mixins at the same time as debugging my plugin.

Upon running SpongeForge the resources get (correctly?) copied to the build directory of my plugin.

And as per the docs, (pending merges that have been reviewed as correct) https://github.com/ryantheleach/SpongeDocs/blob/ConfigRedux/source/images/InheritProjectCompileOutputPath.png

Flard damn it. That’s what the issue was.

I was setting the option on the SpongeForge module not the plugin module. Thanks for the help guys.

2 Likes
2

That’s a weird-looking eclipse.

1 Like
3

It’s not eclipse, it’s IntelliJ unless you mean the screen shot of the rubber ducky, in which case it’s just the first image I found for rubber ducky debugging.

2 Likes