TheBrokenRail
/
ModUpdater
Archived
2
2
Fork 3
Code Issues 12 Pull Requests 1 Releases Wiki Activity

1.16.1 receiving "update" to 1.16 #8

New Issue
Open
opened 2020-08-05 23:19:27 +00:00 by morottao · 4 comments
morottao commented 2020-08-05 23:19:27 +00:00
Copy Link

see the photo

see the photo
Sem título.png
221 KiB
Sem título.png
madis0 commented 2020-08-07 15:12:34 +00:00
Copy Link

Duplicate of #1

Duplicate of #1
Giselbaer commented 2020-08-11 20:12:45 +00:00
Contributor
Copy Link

This might be a slightly different issue, as those seem all to be "my" mods, which are all using the json strategy, and, this being a "-pre" version, I didn't include the version number in my jsons. I did include "1.16" and "1.16.1" (and 1.16.2 since that was released today).

I think ModUpdater might/should be able to find the version of the base MineCraft, and use that in the keys for the json strategy.

This might be a slightly different issue, as those seem all to be "my" mods, which are all using the json strategy, and, this being a "-pre" version, I didn't include the version number in my jsons. I did include "1.16" and "1.16.1" (and 1.16.2 since that was released today). I think ModUpdater might/should be able to find the version of the base MineCraft, and use that in the keys for the json strategy.
Giselbaer commented 2020-08-11 20:35:55 +00:00
Contributor
Copy Link

Which version of MineCraft was that? The title says "1.16.1 receiving update ..."

If that was MineCraft 1.16.1, the ModUpdater was actually correct in complaining. The versions to the right were the correct, current versions for 1.16.1 (even when they had 1.16 in the name), while the installed versions were for 1.16.2-pre1, so, not the correct versions for that MC version.

Which version of MineCraft was that? The title says "1.16.1 receiving update ..." If that was MineCraft 1.16.1, the ModUpdater was actually correct in complaining. The versions to the right were the correct, current versions for 1.16.1 (even when they had 1.16 in the name), while the installed versions were for 1.16.2-pre1, so, not the correct versions for that MC version.
TheBrokenRail commented 2020-08-11 21:26:23 +00:00
Owner
Copy Link

Is this fixed in 1.1.10, try in both release and pre-release.

Is this fixed in ``1.1.10``, try in both release and pre-release.
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Branches Tags
master
1.1.11+1.16.2
1.1.10+1.16.2
1.1.9+1.16.2
1.1.9+1.16.1
1.1.8+1.16.1
1.1.7+1.16.1
1.1.6+1.16.1
1.1.5+1.16.1
1.1.4+1.16.1
1.1.3+1.16.1
1.1.2+1.16.1
1.1.1+1.16.1
1.1.0+1.16.1
1.0.11+1.16.1
1.0.10+1.16.1
1.0.9+1.16.1
1.0.8+1.16.1
1.0.7+1.16.1
1.0.6+1.16.1
1.0.5+1.16.1
1.0.4+1.16.1
1.0.3+1.16.1
1.0.2+1.16.1
1.0.2+1.16
1.0.1+1.16
1.0.0+1.16
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
4 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: TheBrokenRail/ModUpdater#8
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?