| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: flow <flowlnlnln@gmail.com>
|
|
Signed-off-by: flow <flowlnlnln@gmail.com>
|
|
Also adds slug field.
Signed-off-by: flow <flowlnlnln@gmail.com>
|
|
The Modrinth changelog is fairly straight-forward, as it's given to us
directly with the API call we already did. Flame, on the other hand,
requires us to do another call to get the changelog, so it can introduce
quite a heavy performance impact. This way, we make it optional to get
such changelog.
Signed-off-by: flow <flowlnlnln@gmail.com>
|
|
Call added:
- Get Fingerprints Matches
- Get Mod File Changelog
Signed-off-by: flow <flowlnlnln@gmail.com>
|
|
More links for CF / Modrinth mods / modpacks
|
|
NOT DOWNLOAD LINKS! (someone would ask it i'm sure :p)
|
|
Also fix a dumb moment
|
|
|
|
|
|
Some stylistic changes, and get hashes from the mod providers when
building the metadata.
|
|
Also use it as a on-disk format for storing mod metadata. This will be
used later on to make better mod managment.
|
|
We have been asked by CurseForge to remove this workaround as it
violates their terms of service. This is just a partial revert, as the
UI changes were otherwise unrelated.
This reverts commit 92e8aaf36f72b7527322add169b253d0698939d0, reversing
changes made to 88a93945d4c9a11bf53016133335d359b819585e.
|
|
|
|
Co-authored-by: flow <thiagodonato300@gmail.com>
|
|
|
|
|
|
Right now we want to include Fabric mods in our searches where possible.
Modrinth allows definining multiple loaders, while Flame only allows a
single value.
As a compromise we ask for Fabric mods only on Flame and for both Fabric
and Quilt mods on Modrinth.
|
|
|
|
The checks used are roughly the same as the ones proposed in the
clang-tidy PR (except perhaps that I used modernize-* instead of listing
them individually,though I don't think this caused any readability
detriments).
In ModrinthModel.cpp and FlameModModel.cpp I ignored the
modernize-avoid-c-arrays one, mostly because making the sorts array an
std::array would most likely increase the code complexity because of the
virtual function. Aside from that, the static_cast warning from
Application.h was not dealt with, since it's not in this PR's scope.
|
|
Since there's little difference between them, let's remove duplication
and merge them.
|
|
Since there's no validation for forge mods since the start, we were just
looping with no porpuse in this situation.
|
|
Fixes #206 partially. Although we don't list mods that have no
compatibility with the mod loader we are using, mods that have support
for both loaders still show up, and the versions for both the loaders
are still shown.
Also simplifies a little the logic in
FlameModIndex::loadIndexedPackVersions
|
|
|
|
|
|
|
|
|
