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

Add ModSide to manifest. #12

Open
Claycorp opened this issue May 30, 2015 · 3 comments
Open

Add ModSide to manifest. #12

Claycorp opened this issue May 30, 2015 · 3 comments

Comments

@Claycorp
Copy link

Adding

manifest {
        attributes 'ModSide': 'CLIENT'
    }

to jar in your build.gradle file will mark the mod as client side and will prevent it from loading on server and thus crashing them.

@asaskevich
Copy link
Owner

Like this?

buildscript {
...
}
...
apply plugin: 'forge'
...
version = "1.5.0"
group= "com.asaskevich.smartcursor" // http://maven.apache.org/guides/mini/guide-naming-conventions.html
archivesBaseName = "SmartCursor"
...
minecraft {
...
}

manifest {
    attributes 'ModSide': 'CLIENT'
}

dependencies {
...
}

processResources {
...
} 

because in the last release there are no anything inside manifest file, only its version

@dries007
Copy link

No, it needs to go inside of the jar block, like this:

https://github.com/dries007/TapeMouse/blob/master/build.gradle#L82

Also, you might want to include the build.gradle in the project repo.
A build server would then be able to build the project every time you push a commit.
You can still hide details like passwords in a separate gradle file in your user directory. (More info on the gradle website)

@asaskevich
Copy link
Owner

@Claycorp @dries007 okay, will look on it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants