Links
Tags
Creators
Details
1.0.0-Beta.1
Compatibility
Changes
💬 NeoTalk 1.0.0-Beta.1
This is the first public beta of NeoTalk.
This release is intended to test the new chat system under real server conditions, identify remaining edge cases, and improve the plugin before NeoTalk 1.0.0 reaches stable release.
Feedback and bug reports are highly appreciated. <3
NeoTalk 1.0.0-Beta.1 introduces the first complete foundation of the plugin.
The focus of this release is intentionally limited: provide a modern and interactive Minecraft chat experience with a clean default style, useful everyday features, and live configuration—without turning NeoTalk into an oversized all-in-one system.
💬 Modern Chat Formatting
NeoTalk replaces Minecraft’s default chat presentation with a clean, Adventure-based format.
Example:
[Owner] DasEtwa » Killa Haus, ich geh Dias minen.
The renderer supports:
- Adventure Components
- MiniMessage formatting
- LuckPerms prefixes and ranks
- Interactive player names
- Hover information
- Clickable player names
- Configurable formatting
LuckPerms is optional. When installed, NeoTalk can automatically display rank and prefix information.
👤 Player Hover and Click Actions
Player names are interactive.
Hovering over a player name can display information such as:
DasEtwa
Rank: Owner
Click to message
Clicking the name can prepare a private message command:
/msg DasEtwa
This keeps regular Minecraft chat simple while making common interactions faster and more convenient.
📨 Private Messages
NeoTalk includes its own private messaging system.
Available commands:
/msg <player> <message>
/reply <message>
Reply targets are stored in bounded runtime state and are cleaned up when they are no longer needed.
⚔️ Item Display
Players can display the item currently held in their hand:
/item
NeoTalk creates a snapshot of the item and inserts it into chat as an interactive component.
Hovering over the item displays Minecraft’s native item tooltip, including supported information such as:
- Custom names
- Lore
- Enchantments
- Attributes
- Armor and tool information
- Other item component data
The original inventory item is never removed, changed, or modified.
👋 Join and Leave Messages
NeoTalk can replace Minecraft’s default join and leave messages with configurable custom messages.
Changes are applied live through the NeoTalk runtime configuration.
📢 Automated Announcements
Beta 1 includes scheduled server announcements for:
- Tips
- Rules
- Server information
- Reminders
- Community messages
Announcements are bounded and managed directly by NeoTalk to prevent uncontrolled background tasks.
🖥️ GUI-First Configuration
NeoTalk is designed around live configuration.
The intended editing workflow is:
Edit
→ Preview
→ Apply
→ Validate
→ Activate
→ Persist
Configuration changes do not require a regular server restart.
Configuration files remain available for server owners who prefer manual editing, backups, or Git-based configuration management.
⚡ Performance and Runtime Design
Even this first beta includes several runtime safeguards.
NeoTalk uses:
- Viewer-independent rendering where possible
- Cached LuckPerms metadata
- Bounded reply state
- Bounded editor sessions
- Asynchronous configuration persistence
- No configuration write for every GUI interaction
- Cleanup when players leave
- Reusable Adventure Components where practical
- Bounded scheduled announcements
The goal is to keep NeoTalk lightweight and reliable as more features are added in future releases.
🔌 Compatibility
NeoTalk 1.0.0-Beta.1 currently targets:
- Minecraft Java Edition 1.20.6+
- Java 21+
- Paper
Purpur support is part of the long-term full-support direction.
Spigot compatibility is planned where it can be supported without compromising the modern Paper implementation.
Folia support is planned for a later update and is already being considered in the project’s architecture.
🧪 Testing and Validation
NeoTalk Beta 1 has been developed and tested on a real Paper server running behind Velocity.
Validation includes:
- Gradle clean builds
- Automated unit tests
- Paper plugin loading
- LuckPerms integration
- Public chat formatting
/msg/reply/item- Player hover and click actions
- Configuration reloads
- Lobby deployment behind Velocity
NeoTalk is still in beta. The plugin has already received dedicated logic, permission, and performance reviews, but long-term production behavior and broader plugin compatibility are still being evaluated.
Please report any unexpected behavior so it can be fixed before the stable 1.0.0 release.
🚧 Not Included Yet
Beta 1 intentionally does not include the entire NeoTalk roadmap.
The following features are planned for later releases:
- Moderation and word filtering
- URL allowlists and denylists
- More advanced reply interactions
[item]support inside regular messages- Emoji aliases
- Chat statistics
- Personalized automated messages
- NeoData integration
- Velocity network chat
- Folia support
- Optional chat logging
The goal is to build these systems on top of a stable core instead of releasing everything half-finished at once.
🐛 Reporting Bugs
Found a bug or unexpected behavior?
Please report it through GitHub Issues.
When possible, include:
- NeoTalk version
- Server software and version
- Minecraft version
- Java version
- Installed plugins
- Relevant configuration
- Full console output
- Steps to reproduce the issue
GitHub Issues are preferred because they make problems easier to track, reproduce, and resolve.
🔄 Updating
For this first beta release:
- Stop the server.
- Back up your existing NeoTalk configuration.
- Replace the NeoTalk JAR file.
- Start the server normally.
- Check the console for warnings or errors.
- Test chat,
/msg,/reply, and/item.
Because this is the first public beta, configuration compatibility between early beta versions is not guaranteed.
Thank you for testing the first NeoTalk beta! 💜
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:QLEiXTFI:WEsCZAqB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:QLEiXTFI:WEsCZAqB"
}
