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

VSCode Issues with Classpaths/Configurations #37

Open
Blue-Beaker opened this issue Dec 3, 2024 · 2 comments
Open

VSCode Issues with Classpaths/Configurations #37

Blue-Beaker opened this issue Dec 3, 2024 · 2 comments

Comments

@Blue-Beaker
Copy link

When I include CraftTweaker2-MC1120-Main in dependencies, CraftTweaker API is loaded into classpath in the editor instead.
This makes me unable to auto-complete anything in the crafttweaker.api.minecraft package. However runClient worked fine.

Environment: Kubuntu 22.04, VSCode + Extension pack for Java, java.import.gradle.java.home set to my jdk21
图片

My dependencies.gradle
https://gist.github.com/Blue-Beaker/39dd42e9756173f01ba83bfa936f5c00

Also I have

# Dependencies
version_crafttweaker=1.12-4.1.20.689

in my gradle.properties.

@Rongmario
Copy link
Member

I sincerely recommend using IntelliJ IDEA instead of VSCode's WIP extensions with Java/Gradle.

@Blue-Beaker
Copy link
Author

I tried IDEA and it worked flawlessly.
图片

I use vscode because it has extensions to search autocomplete items/blocks/fluids in configs and crafttweaker scripts.
Maybe I should use both at the same time, until VSCode has completed their support. IDEA for the code, VSCode for the others.

I sincerely recommend using IntelliJ IDEA instead of VSCode's WIP extensions with Java/Gradle.

@Rongmario Rongmario changed the title Wrong package from a dependency is loaded into editor. VSCode Issues with Classpaths/Configurations Dec 3, 2024
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