Conversation
Member
|
You changed the script exposed events to be less useful and less convenient |
|
|
MC-Samuel
force-pushed
the
thread_events_fix
branch
from
September 5, 2026 05:24
690af79 to
8032d3e
Compare
| return super.getContext(name); | ||
| } | ||
| } | ||
| package com.denizenscript.ddiscordbot.events; |
Member
There was a problem hiding this comment.
I think there's line-ending wonk or something in this file now?
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
These events were previously using events that trigger when the bot can no longer view the channel, causing them to not fire when intended. The Discord event listener has been updated, and the events have been merged into one since they have the same listener.