Список изменений
CoreTuff v2.0 — Nightly-2
After approximately one month of development, debugging, college, real-life side quests, and several encounters with the "I'll finish this tomorrow" boss fight, CoreTuff v2.0 Nightly-2 is finally here.
Yes, we know.
Nightly-1 was released a month ago.
No, we did not forget about CoreTuff.
College simply decided that CoreTuff needed a little more development time.
We apologize for the delay, and thank you for sticking around while development continued behind the scenes.
Nightly-2 is a major step forward for the v2.0 development cycle, focusing heavily on server monitoring, performance awareness, incident tracking, and a much more capable CoreTuff Dashboard.
Server Health Monitoring
CoreTuff now continuously monitors the health of your server.
The Dashboard can now display:
• TPS (1m / 5m / 15m) • MSPT • CPU usage • Memory usage • Player count • JVM information • Operating system information • World count • Folia status • Plugin health • CoreTuff subsystem health • Integration status • Recent exceptions
Your server can now basically tell you that something is wrong before you have to stare at the console for 20 minutes wondering what happened.
Performance Monitoring
CoreTuff now actively watches server performance instead of simply displaying numbers.
Performance monitoring currently tracks:
• TPS • MSPT • Memory usage • CPU usage
Performance conditions must persist for a period of time before an alert is created.
This prevents temporary fluctuations from turning your Dashboard into a panic room.
Performance states include:
• Healthy • Warning • Critical
When a performance issue is detected, CoreTuff can automatically create an incident.
When the server recovers, the incident is automatically resolved.
Performance Alerts
The Performance section has been upgraded with automatic alert states.
Metrics can now indicate:
• Healthy • Warning • Critical
The Dashboard receives the server's actual performance state instead of trying to guess it from frontend data.
This means the Web Panel now knows whether a metric is actually problematic rather than simply looking at a number and hoping for the best.
Incident Management
Introducing the CoreTuff Incident System.
CoreTuff can now automatically detect, track, and resolve important server events.
Incidents can be created for:
• Performance problems • Database issues • Configuration events • Dashboard events • Dashboard session events • Module problems • Integration issues • Exceptions • Server events • CoreTuff events
Each incident maintains its own timeline, severity, status, description, and relevant information.
Incidents can be:
• Detected • Active • Recovered
So instead of:
"Something broke."
you can now have:
"Something broke at 19:42, remained broken for 31 seconds, and recovered at 19:43."
Progress.
Incident Timeline
The CoreTuff Dashboard now includes a complete incident timeline.
Recent events can be viewed directly from the Overview page, while the full timeline provides a more detailed history.
The timeline supports filtering by:
• Severity • Status • Subsystem
Incidents are displayed chronologically so administrators can understand what happened and when it happened.
Because "it was lagging earlier" is not exactly a useful incident report.
Recent Incidents
The Dashboard Overview now includes a Recent Incidents section.
It provides a quick look at the latest server events without requiring administrators to open the full timeline.
Active incidents are highlighted, while recovered incidents remain available for reference.
Dashboard
The CoreTuff Dashboard is now the central interface for both server monitoring and configuration management.
The Dashboard provides access to:
• Server health • Performance statistics • Live configuration management • Plugin information • Integration information • CoreTuff subsystem status • Incident monitoring • Server events • Diagnostics
The previous /ct editor command has been removed.
It has been replaced by:
/ct dash
Permission: coretuff.admin (or OP)
Running /ct dash creates a secure Dashboard session and generates a clickable link to the CoreTuff Web Panel.
One command.
One Dashboard.
Much less typing.
Dashboard Sessions
Dashboard sessions can now be monitored by CoreTuff.
The system can track:
• Session activation • Connection state • Disconnection • Session expiration • Session closure
When a Dashboard session expires, CoreTuff records the event and reports it through the Dashboard.
The server console also receives a notification when a Dashboard session expires.
No more wondering whether the Dashboard disappeared or just decided to take a vacation.
Dashboard States
The Dashboard health system now understands additional runtime states.
CoreTuff can distinguish between:
• Running • Starting • Stopped • Error • Disabled
This provides more accurate health information in the Web Panel.
A browser session disconnecting does not mean the Dashboard module itself has stopped.
Because apparently those are two different things.
CoreTuff Health
CoreTuff now reports the health of its major subsystems individually.
The Dashboard can display the status of:
• Database • Configuration • Dashboard • Modules • Exceptions
Each subsystem has its own health state.
This makes it easier to identify exactly which part of CoreTuff is having problems instead of simply being greeted with a mysterious "Warning" badge.
Plugin Health
The Dashboard now provides information about installed server plugins and their health.
Plugin status can include:
• Enabled • Disabled • Dependency problems
This gives administrators a quick overview of the server's plugin environment.
Integration Detection
CoreTuff's integration system has been improved.
Integrations are now based on actual CoreTuff integration registration rather than simply treating every installed plugin as an integration.
A plugin only appears as a CoreTuff integration when CoreTuff actually detects and uses the relevant API.
Much less:
"Plugin installed = integration."
Much more:
"CoreTuff actually knows what this thing is."
Web Panel
The CoreTuff Web Panel has been upgraded to:
v1.0-Alpha-2
The panel now includes the new health monitoring and incident management functionality introduced in Nightly-2.
The Dashboard now goes beyond configuration and provides a centralized view of your server's health and activity.
Incident Improvements
The incident system now supports different severity levels:
• Info • Warning • Critical
Informational events can now be recorded without making the entire server look like it is on fire.
Incident history is also retained with automatic cleanup of older resolved incidents.
Commands
/ct dash
Permission: coretuff.admin (or OP)
Creates a secure CoreTuff Dashboard session and provides a clickable link to the Web Panel.
The Dashboard replaces the previous /ct editor command.
The Dashboard provides:
• Configuration management • Server monitoring • Performance information • Incident monitoring • Plugin information • Integration status • CoreTuff health information
/ct dump
Permission: coretuff.admin.dump
Generates a comprehensive diagnostic report containing:
• System information • Server information • Runtime statistics • Database information • Loaded integrations • Configuration summary • Permission information • Exception history
Designed to simplify troubleshooting and bug reporting.
/ct dumpdata
Permission: coretuff.dump
Exports CoreTuff database tables into a readable dump file for debugging and support purposes.
/ct dashboard
Permission: coretuff.admin (or OP)
Manages the embedded CoreTuff Dashboard.
Available actions include:
• Generate pairing codes • View Dashboard status • Restart the Dashboard module
/ct bug
Permission: OP
Provides a clickable link to the CoreTuff GitHub Issue Tracker.
Because sometimes the fastest way to fix something is to admit that it is, in fact, broken.
Console & Event Logging
CoreTuff now provides clearer logging for important state changes.
Examples include:
• Performance degradation • Performance recovery • Dashboard session expiration • Database issues • Module failures • Integration changes • Configuration events
Normal monitoring activity does not flood the server console.
Only meaningful state transitions are logged.
Fixes
• Fixed performance condition tracking.
• Fixed incident escalation not immediately updating the Dashboard.
• Fixed incident recovery handling.
• Fixed active incident elapsed-time display.
• Improved Dashboard state reporting.
• Improved Dashboard session event handling.
• Improved health data synchronization.
• Improved performance alert accuracy.
• Improved integration detection.
• Improved subsystem health reporting.
• Improved incident history handling.
• Various internal stability improvements.
What Changed?
Nightly-1 focused heavily on establishing the new CoreTuff Dashboard and configuration experience.
Nightly-2 takes that foundation and turns the Dashboard into something that can actually watch your server.
CoreTuff can now:
Monitor → Detect → Report → Track → Resolve
server health issues automatically.
A Small Apology
Yes.
It has been a month.
We would like to formally blame:
College.
Assignments.
Exams.
Real life.
And the completely reasonable decision to say:
"I'll just fix this one thing before releasing."
That one thing was, unfortunately, followed by approximately 47 other things.
Thank you for being patient while Nightly-2 took its scenic route to production.
We'd rather release something properly tested than rush a build out just because the calendar looked at us funny.
Notes
CoreTuff v2.0 Nightly builds are development builds.
Features may change, be expanded, or occasionally decide they no longer understand the concept of software.
If you encounter a problem, please report it through the GitHub Issue Tracker.
GitHub: https://github.com/Voxelware-studios/CoreTuff/issues
Discord: https://discord.gg/tuArC9pTbv
Download: /plugins/coretuff
Thank you to everyone testing CoreTuff v2.0.
Welcome to CoreTuff v2.0 Nightly-2.
Write this content as blog for website and follow the same pattern