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

Get KubeJS client script errors #22

Closed
calog3no opened this issue Jul 6, 2024 · 3 comments
Closed

Get KubeJS client script errors #22

calog3no opened this issue Jul 6, 2024 · 3 comments
Labels
Bug Something isn't working fixed in next release Fixed in the next release. If the issue this is on is closed, the fix is already released

Comments

@calog3no
Copy link

calog3no commented Jul 6, 2024

Modpack Version

1.3.0 develop branch

Describe your issue.

When I load the pack in Prism Launcher I get a KubeJS script error and pack will not load. I uninstalled, and synched the fork again and still get the error. I looked at my forked repo and all the scripts looked identical to the original develop branch. I am using NeoForge 21.0.59 beta mod loader.

Crash Report

Latest Log

https://gist.github.com/calog3no/882f336f0c4312fe54312719f976aba5

Have you modified the modpack?

No

User Modifications

No response

Did the issue happen in singleplayer or on a server?

Singleplayer

Discord Username

calog3no

@calog3no calog3no added the Bug Something isn't working label Jul 6, 2024
@HeatherComputer
Copy link

HeatherComputer commented Jul 6, 2024

what on earth are you trying to do with that script tag there

also
If you installed the pack via prism's curseforge installation ui, did you make sure to download all the mods it said were blocked?
It'll automatically recognise each one as it's downloaded, dismissing the prompt without actually downloading the mods will effectively give you a broken pack.

@calog3no
Copy link
Author

calog3no commented Jul 6, 2024

I fixed the wonky script and moved it to the correct location in the bug report under latest log.😬 I have made a fork of the repo and have cloned it using Git bash to my install. I have been updating using the upstream function and this is the first time receiving an error after updating to the latest develop branch.

@NielsPilgaard
Copy link
Collaborator

I fixed that bug a few minutes ago 👍

@NielsPilgaard NielsPilgaard added the fixed in next release Fixed in the next release. If the issue this is on is closed, the fix is already released label Jul 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working fixed in next release Fixed in the next release. If the issue this is on is closed, the fix is already released
Projects
None yet
Development

No branches or pull requests

3 participants