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.

Sign up for GitHub

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

Jump to bottom

[1.20.1] Invalid mod version causes log to suggest FML is missing #65

Open
UpcraftLP opened this issue Jan 13, 2024 · 0 comments
Open

[1.20.1] Invalid mod version causes log to suggest FML is missing #65

UpcraftLP opened this issue Jan 13, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@UpcraftLP
Copy link

I had set an invalid version in development, something like development+202401010000-1.20.1, which failed to parse and then subsequently made it appear as if neoforge was missing entirely.

image

changing my dev version scheme to 1.20.1-development+202401010000 fixed this.

Yes, there was a message about my version failing to parse higher up, but this "missing javafml" error should not appear nonetheless.

tested on: 1.20.1-47.1.85
@Shadows-of-Fire Shadows-of-Fire added the bug Something isn't working label May 18, 2024
shartte added a commit that referenced this issue Dec 22, 2024
@shartte
Add utility method to quickly construct JarContent if no filters or r…
5c4f4f8 
…eplacement manifests are to be used (#65)

The most common use of JarContentBuilder is:

```java
new JarContentsBuilder().paths(path).build()
```

This allows:

```java
JarContents.of(path)

or

paths.map(JarContents::of)
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Shadows-of-Fire @UpcraftLP