Fix os.epoch("ingame") throwing "Unsupported operation" #126
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
cc-tweaked/CC-Tweaked@69b211b I think it needs patching in a few more places. |
This has been here since 1.17 :D. Class rename gone wrong!
toad-dev
force-pushed
the
patch/fix-epoch-ingame
branch
from
e67f111
to
06ee57e
Compare
|
Ah, thank you! I should've looked into the git history first. |
|
is this mergable or is it stale? |
|
Mergable. |
|
Aight, not in an position to merge at the moment, feel free to merge at
your discretion
…On Sat, Oct 22, 2022, 4:00 PM Jonathan Coates ***@***.***> wrote:
Mergable.
—
Reply to this email directly, view it on GitHub
<#126 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACPQOXTV4RDD74STXQ3ILKTWERWZPANCNFSM6AAAAAAQER5HA4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #123
The issue was just the result of some sort of find and replace error.