Reyhaneh Zafari
📎 1 file 3,973 chars
📄
Medic_Activity_Tracker_Prompt.txt
txt 125 lines
▶
Create a complete and functional Minecraft Java Medic Management Mod.

TARGET VERSION
- Minecraft Java 1.21.11
- Mod loader: Fabric
- Project name: Medic Activity Tracker
- Deliver a compiled .jar and the complete source project.

IMPORTANT DESIGN INSTRUCTION
Use the three uploaded reference screenshots as the structural and functional design references. Recreate their layout and organization as closely as possible. Do not replace them with a generic Minecraft dashboard.

DESIGN AND UI
Use a premium futuristic gaming interface.
- Dark Navy background: #101522
- Electric Cyan: #65D6E8
- Lavender: #A78BFA
- Dark blue panels: #192338
- Light text: #E8EDFF
Do NOT use green as the main theme.
Keep the interface clean, spacious, readable, and similar to the reference screenshots.

1. MEDIC ACTIVITY TRACKER
Follow the first reference image.
Create a table with:
- Medic Name
- Rank
- Total Revives

Display every medic who performs revives.
Features:
- Track revive counts when reliable game/server events are available.
- Show today's revive statistics.
- Keep previous days' records.
- Merge repeated revive records for the same player.
- Allow searching for medic names.
- Show individual medic activity history.

2. DAILY TASKS
Follow the second reference image.
Create a checklist with:
- Test
- Gasht
- Playtime
- Event
- Elamiye

Each task must have a checkbox.
Completed tasks should have a clear visual distinction.
Save daily task progress and reset the checklist for a new day without deleting previous records.

3. MEDIC CHECK
Follow the third reference image's Minecraft chat-style information layout.
Create a player verification system.
When an administrator enters a username, display:
- Username
- Is the player allowed to take the test?
- Gang membership status
- Wanted status
- Blacklist status
- Blacklist duration
- Number of previous tests
- Warning count
- Last test date and time
- Remaining test cooldown
- Reason for rejection

Show clear PASS / REJECT status.
If a player has taken a test within the previous 48 hours, prevent another test until the cooldown expires.
A player with an active blacklist, gang membership, Wanted status, or disqualifying warnings must be flagged according to configurable server rules.

4. TEST MANAGEMENT
Create a complete test history system.
Store:
- Player username
- Tester username
- Test date
- Test result
- Assigned rank
- Rejection reason

Include:
- Passed tests
- Rejected tests
- Test counts by rank
- Searchable history

5. WARNING AND BLACKLIST MANAGEMENT
Display warnings and blacklist information.
Allow authorized administrators to:
- Add warnings
- Remove warnings
- Add blacklist entries
- Remove blacklist entries
- Record reasons and dates

6. DATA STORAGE
All statistics must persist after restarting Minecraft.
Store historical data separately by date.
Never fabricate server information or display fake automatic detection.

7. SERVER INTEGRATION
Build an integration layer for the actual roleplay server.
Use available server APIs, plugins, logs, or authorized data interfaces to retrieve:
- Wanted status
- Gang membership
- Warning records
- Blacklist records
- Test history
- Revive events

If direct integration is unavailable, provide a clearly labeled manual-entry mode and configurable integration interface.

8. FINAL REQUIREMENTS
- Build a complete working Fabric project for Minecraft Java 1.21.11.
- Include all source files and dependencies/configuration needed to build it.
- Generate a compiled .jar file.
- Include installation instructions.
- Make all buttons and menus functional.
- Do not create a static mockup.
- Do not leave important features as placeholders.
- Verify compatibility with Minecraft Java 1.21.11.
- If a requested feature cannot work without server-side integration, explain the exact missing server interface and implement the supported fallback instead.

The final result must be a functional Medic Management System, not just a visual design.
Kodari AI
KodariNov 7 at 6:20 pm 3
MedicActivityTracker
Fabric mod for Minecraft 1.21.11 providing a medic management dashboard with a futuristic dark-navy UI. Tracks revive statistics per medic with daily and historical records, searchable history, and merge functionality. Includes a daily task checklist with persistent progress and daily reset, a medic verification system showing player status, gang membership, wanted/blacklist status, warnings, and test cooldowns, plus full test history management with pass/reject records and rank assignment. Features warning and blacklist administration, persistent JSON data storage separated by date, and an integration layer supporting server API connections with a manual-entry fallback mode.
  1. Set up the Fabric 1.21.11 project and persistent server-side medic, task, test, warning, and blacklist records.

  2. Add permission-checked management commands plus a manual integration API for servers without revive/status hooks.

  3. Add the owo-ui dashboard and client keybind, with buttons that run real management commands.

Created the Fabric 1.21.11 Medic Activity Tracker source project, including the server-side records, operator commands, manual integration API, and an owo-ui dashboard opened with M.

  • Revives, daily tasks, test history, warnings, blacklist entries, and eligibility settings persist in the world’s medic_activity_tracker.json.

  • Management commands require operator permission level 2; /medic help lists them. The dashboard’s controls run those commands, with server results reported in chat.

  • Vanilla has no standard revive, gang, wanted, or RP-record events. Those details must be entered with commands or supplied by another Fabric mod through MedicIntegration; the mod does not invent automatic detections.

  • The attachment contained the written prompt but not the three referenced screenshots, so the dashboard follows the specified colors and layout description rather than reproducing those images.

To get the compiled build: on desktop click Compile in the top bar (on phone, ⋮ → Compile Project), click Compile in the window, then Download when it succeeds. Install the mod and bundled owo-lib on the server and clients that use the dashboard, with Fabric API installed. The README includes installation and command instructions.

Kodari can make mistakes. Review important code before using.
Files
src
build.gradle
gradle.properties
manifest.kod
medicrevivesaver-12111-1.0.0.jar
README.md
settings.gradle
Code
14 1,256
src/client/java/com/kodari/medicactivitytracker/client/MedicActivityTrackerClient.java
package com.kodari.medicactivitytracker.client;

import com.kodari.medicactivitytracker.MedicActivityTracker;
import com.kodari.medicactivitytracker.client.ui.MedicDashboardScreen;
import net.fabricmc.api.ClientModInitializer;
import net.fabricmc.fabric.api.client.event.lifecycle.v1.ClientTickEvents;
import net.fabricmc.fabric.api.client.keybinding.v1.KeyBindingHelper;
import net.minecraft.client.option.KeyBinding;
import net.minecraft.util.Identifier;
import org.lwjgl.glfw.GLFW;

public final class MedicActivityTrackerClient implements ClientModInitializer {
    private static final KeyBinding OPEN_DASHBOARD = KeyBindingHelper.registerKeyBinding(new KeyBinding(
            "key.medic_activity_tracker.open",
            GLFW.GLFW_KEY_M,
            KeyBinding.Category.create(Identifier.of(MedicActivityTracker.MOD_ID, "general"))
    ));

    @Override
    public void onInitializeClient() {
        ClientTickEvents.END_CLIENT_TICK.register(client -> {
            while (OPEN_DASHBOARD.wasPressed()) {
                if (client.player != null && client.currentScreen == null) {
                    client.setScreen(new MedicDashboardScreen());
                }
            }
        });
    }
}