Creators
Details
Licensed MIT
Published 9 months ago
Updated 8 months ago
All versions
1.0.3
Release
Viscord 1.0.38 months ago 72
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Dedicated servers only
Changes
Version 1.0.3 - 2025-12-03
✨ New Features
🎛️ Per-Player Message Filtering System
- Reorganized
/viscord messagescommand - Individual players can now control whether they see messages from bots and webhooks (other servers)/viscord messages- Check your current filter status/viscord messages enable- Show ALL messages including bots/other servers (default)/viscord messages disable- Only show messages from Discord users and your own server
- New
/viscord eventscommand - Control event messages (achievements, join/leave)/viscord events- Check your current event filter status/viscord events enable- Show achievements and join/leave messages (default)/viscord events disable- Hide achievements and join/leave messages
- Pure player preference system - No global config option, fully player-controlled
- Persistent storage - Preferences saved to
config/viscord-player-preferences.json - Default behavior - All players see everything by default (most inclusive)
- Smart filtering - Only filters bot/webhook messages and events, never filters real Discord users
- Command restructuring - Moved filtering commands from
/discordto/viscordfor better organization - Status: ✅ Implemented in NeoForge 1.21.1, Forge 1.21.1, and Forge 1.20.1
🐛 Bug Fixes
- Fixed duplicate advancement messages - Advancements were sometimes sending twice with different emoji templates
- Removed duplicate
sendAdvancementEmbed()call in event handler - Standardized on trophy emoji (🏆) for all advancement types (Challenge/Goal/Task)
- Single consistent embed format for all advancement notifications
- Affects: All versions (Forge 1.20.1, Forge 1.21.1, NeoForge 1.21.1)
- Removed duplicate
⚙️ Configuration Changes
- Changed
ignoreBotsdefault fromtruetofalse- Loop prevention is now handled by webhook ID filtering in code
- No need to blanket ignore all bot messages
- Users can still manually enable if needed for specific use cases
- Affects: All versions (Forge 1.20.1, Forge 1.21.1, NeoForge 1.21.1)
📝 Version Compatibility
- ✅ Forge 1.20.1: Full feature set implemented
- ✅ Forge 1.21.1: Full feature set implemented
- ✅ NeoForge 1.21.1: Full feature set implemented
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:9NvsRotH:YpKBGms1"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9NvsRotH:YpKBGms1"
}

