You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that all the Zrips-plugins use CMILib, I was hoping if it was possible they could community with each-other to help build an in-depth version-profile that helps both the server owner, as well as yourself in bug reports, and the Discord community. I will include an example.
Having the option to run one command that gathers up a bit of hopefully non-intrusive server setup and plugin details, would help speed up narrowing down where potential issues lie. The extensive /cmi version is a great example. In a glance we know if they're using an unsupported server engine, outdated build, or if chat is even enabled, or any of the required modules for a feature someone might have a problem with. If this could get extended to all plugins, that would be pretty cool. Jobs received the same type of /jobs version, which is great. Which got me thinking, .. would it be possible to let CMILib have a a debug, profiler, support, version command ala cmil support or 'cmil version` which figures out which of the zrips-made plugins are installed, if there are any newer versions out, some database type info, economy engine info if applicable, check the server engine details, and perhaps even include the /ver output .. get the plugin list, and informs them they can copy paste all that info into a pastebin for github bug reporting, or discord community support questions. etc etc ..
console command:
> CMILib version
Results gathered on July 14th, 2023 at 18:40:06
Zrips plugins detected:
» CMILib, Version: 1.4.0.0 -> 1.4.0.1
» JobsReborn, Version: 5.2.0.0
(SQLite, Economy: CMIEconomy Vault: 1.7.3-b)
» TradeMe, Version: 6.1.3.4 -> 6.2.0.0
(SQLite)
» CMI, Version: 9.6.0.1 -> 9.6.0.2
(CMI economy: Enabled Vault: 1.7.3-b CMI Chat: Enabled)
(Modules -> 57 enabled 1 disabled: flightCharge)
Server engine:
» Paper: 1.20.1 (git-Paper-71 | 1.20.1-R0.1-SNAPSHOT)
» Minecraft version 1.20.1
Note: Paper (1.20.x) is supported.
(example: Note: Mohist is not supported)
(example: Note: 1.19.0 is not supported, upgrade)
Note: Checking version, please wait...
This server is running Paper version git-Paper-71 (MC: 1.20.1) (Implementing API version 1.20.1-R0.1-SNAPSHOT) (Git: b3dc7a3)
You are 9 version(s) behind
Download the new version at: https://papermc.io/downloads/paper
Previous version: git-Paper-68 (MC: 1.20.1)
Plugins detected:
LuckPerms, Vault, FastAsyncWorldEdit, WorldGuard, PlaceholderAPI, CMILib, JobsReborn, CMI, TradeMe, mcMMO
Note:
If you need support, you can select ALL of the above text, and paste the text in a pastebin (https://paste.md-5.net/) which you can then share on github.com/zrips or discord.gg/dDMamN4
Some of your zrips plugins are outdated, we recommend to /stop, backup, and update your plugins, then start your server and test again. Before asking for support or reporting any bugs.
Since there's no automated pastebin happening, there's no 'what info are they gathering up and sharing, is that public or not?` .. and they can still remove things they're uncomfortable sharing manually before sharing their pastebin URL.
And maybe the /<plugin> version for each plugin could be like the cmi version output, so individual queries are still possible.
The text was updated successfully, but these errors were encountered:
Now that all the Zrips-plugins use CMILib, I was hoping if it was possible they could community with each-other to help build an in-depth version-profile that helps both the server owner, as well as yourself in bug reports, and the Discord community. I will include an example.
Having the option to run one command that gathers up a bit of hopefully non-intrusive server setup and plugin details, would help speed up narrowing down where potential issues lie. The extensive
/cmi version
is a great example. In a glance we know if they're using an unsupported server engine, outdated build, or if chat is even enabled, or any of the required modules for a feature someone might have a problem with. If this could get extended to all plugins, that would be pretty cool. Jobs received the same type of/jobs version
, which is great. Which got me thinking, .. would it be possible to let CMILib have a a debug, profiler, support, version command alacmil support
or 'cmil version` which figures out which of the zrips-made plugins are installed, if there are any newer versions out, some database type info, economy engine info if applicable, check the server engine details, and perhaps even include the /ver output .. get the plugin list, and informs them they can copy paste all that info into a pastebin for github bug reporting, or discord community support questions. etc etc ..Since there's no automated pastebin happening, there's no 'what info are they gathering up and sharing, is that public or not?` .. and they can still remove things they're uncomfortable sharing manually before sharing their pastebin URL.
And maybe the
/<plugin> version
for each plugin could be like the cmi version output, so individual queries are still possible.The text was updated successfully, but these errors were encountered: