Fix message validation and chat log order
Corrected conditional logic in VoteToMuteHelper to validate messages properly and adjusted sorting of chat logs in VoteToMuteStarter to display in reverse chronological order. The update now accurately verifies the existence of selected messages and presents recent logs first for more user-friendly navigation.
This commit is contained in:
parent
8393d12c6d
commit
a908e32d0b
|
|
@ -150,7 +150,7 @@ public class VoteToMuteHelper {
|
|||
}
|
||||
int highestLogEntry = max.get();
|
||||
|
||||
if (voteToMuteStarter.getTotalLogEntries() > highestLogEntry) {
|
||||
if (voteToMuteStarter.getTotalLogEntries() < highestLogEntry) {
|
||||
commandContext.getSource().sendMessage(Utility.parseMiniMessage("<red>Some of your selected messages do not exist.</red>"));
|
||||
return 1;
|
||||
}
|
||||
|
|
|
|||
|
|
@ -60,7 +60,7 @@ public class VoteToMuteStarter {
|
|||
private void parseChatLogs(List<ChatLog> chatLogs) {
|
||||
TagResolver.Single playerTag = Placeholder.parsed("player", votedPlayer.getUsername());
|
||||
TagResolver.Single prefixTag = Placeholder.component("prefix", prefix);
|
||||
chatLogs.sort(Comparator.comparing(ChatLog::getTimestamp));
|
||||
chatLogs.sort(Comparator.comparing(ChatLog::getTimestamp).reversed());
|
||||
parsedChatLogs = IntStream.range(0, chatLogs.size())
|
||||
.mapToObj(i -> Utility.parseMiniMessage(
|
||||
"<number>. <prefix> <player>: <message>",
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user