EventLens

See which plugins handled a Minecraft event — in what order, who cancelled it, who threw, and who was slow — without changing the event.

1.12.2 is the full release for Paper 26.2 (Java 25) and Minecraft 26.2 clients (NeoForge, Forge, and Fabric).

Download 1.12.2 · Wizard · Paper · Client · Agents · First trace · Commands · FAQ

What it is

When a player clicks a block, Paper fires an event. Other plugins listen to that event. One of them might cancel it, change it, throw an error, or just take a long time.

The client also fires its own events before the server sees the click. EventLens can record both sides.

Chat logs and spark do not show that path. EventLens does:

Which plugins (or mods) listened, and in what order
Who cancelled (or uncancelled) it
Which supported fields changed
Which listener or mod handler looks slow
Whether the trace was incomplete (limits, sampling, missing agent, or an error)

It watches. It does not cancel, reorder, re-fire, or hide exceptions.

flowchart LR
  playerClick["Player click"] --> clientMod["Client EventLens"]
  playerClick --> paperEvent["Paper event"]
  paperEvent --> plugins["Your plugins"]
  plugins --> serverEl["Server EventLens"]
  clientMod --> chatCmd["In-game command"]
  serverEl --> chatCmd
  serverEl --> dash["Dashboard"]
  serverEl --> html["Exported index.html"]

What to download

Everything is on the same 1.12.2 release. Use matching versions.

Download	What it is
`eventlens-setup-1.12.2.jar`	Start here. Desktop wizard — copies the right jars and can write Paper / Prism JVM args. See Setup wizard.
`EventLens-1.12.2-manual.zip`	All individual jars in one folder if you want to install by hand. Unzip, then follow Paper, Client, or Agents.

Unzip the manual zip and use these files:

File	Who	Where it goes
`EventLens-1.12.2.jar`	Paper server	`plugins/`
`eventlens-agent-1.12.2.jar`	Paper, for precise per-listener timing	JVM args — not `plugins/`
`eventlens-neoforge-1.12.2.jar`	NeoForge 26.2 client	`mods/`
`eventlens-forge-1.12.2.jar`	Forge 26.2 client	`mods/`
`eventlens-fabric-1.12.2.jar`	Fabric 26.2 client	`mods/`
`eventlens-client-agent-1.12.2.jar`	Any of those clients, for precise per-mod timing	Launcher JVM args — not `mods/`
`eventlens-observability-1.12.2.jar`	Optional next to an agent	Same folder as the agent (fat agents work alone)

Install the Paper plugin for server traces. Install one client mod if you also want the click on the player’s game. Agents are recommended so /eventlens status says precise. The setup jar already contains those files — you do not need to download them separately if you use the wizard.

Install

Setup wizard

The easiest path if you already have a Paper server, a mods folder, or a Prism / MultiMC instance. It does not create a new official Minecraft or CurseForge profile.

Download eventlens-setup-1.12.2.jar from the 1.12.2 release (not the manual zip).
Double-click it, or run java -jar eventlens-setup-1.12.2.jar. The wizard needs desktop Java 21+ (OpenJDK Platform Binary — Temurin, Microsoft OpenJDK, etc.). Do not use Java SE Platform Binary (that is usually Oracle Java 8 and cannot run the wizard). Java 25 is fine. Paper still needs Java 25.
Choose Paper, NeoForge, Forge, or Fabric.
Browse to your plugins/ folder, mods/ folder, or Prism/MultiMC instance.
Leave Install the Java agent checked unless you only want dispatch-only mode.
Click Install, then fully restart the server or quit the launcher and start again.
Run /eventlens status. You want version 1.12.2. If the agent attached, status says precise.

The wizard copies the matching jars. When it can, it also writes:

Paper: user_jvm_args.txt, and start.bat / start.cmd / start.sh / start.ps1 if those files exist
Prism / MultiMC: OverrideJavaArgs=true and JvmArgs= on instance.cfg

The last page puts the -javaagent: line in a highlighted box with Copy JVM argument and a button that opens the Java agents README (Prism, CurseForge, Modrinth, and start scripts). CurseForge and Modrinth still need that line pasted into JVM arguments by hand.

Manual steps below if you prefer not to use the wizard. Download EventLens-1.12.2-manual.zip from the same release, or build from source.

Paper server


Server	Paper 26.2
Java	25 (`java -version` should say 25)
Permission	Commands default to op

Download EventLens-1.12.2.jar.
Put it in the server’s plugins/ folder.
Stop the server, then start it again. Do not /reload.
Run /eventlens status. You should see 1.12.2.

For precise per-listener timing, also add the Paper Java agent.

Building from source? After .\gradlew.bat build the plugin is eventlens-paper/build/libs/EventLens-1.12.2.jar. Most people should use the release download.

Minecraft client

Pick one jar that matches your loader. Put it in that instance’s mods/ folder.

Your client	File
NeoForge 26.2.x	`eventlens-neoforge-1.12.2.jar`
Minecraft Forge 65.1+	`eventlens-forge-1.12.2.jar`
Fabric Loader 0.19 + Fabric API 0.157+	`eventlens-fabric-1.12.2.jar`

Then launch the game and run /eventlens status (or /eventlens ui). You should see the EventLens Screen, HUD toggle, and the same /eventlens / /el family as the server.

For precise per-mod timing, add the client Java agent below. Do not put the agent jar in mods/.

Java agents (optional)

EventLens works without an agent. An agent adds precise timing (which listener or mod handler was slow). /eventlens status says precise when it worked, or dispatch-only when it did not.

There are two agent jars. Do not mix them up.

Agent	File	Goes in
Paper (server)	`eventlens-agent-1.12.2.jar`	Server JVM args — not `plugins/`
Client (NeoForge, Forge, or Fabric)	`eventlens-client-agent-1.12.2.jar`	Launcher JVM args — not `mods/`

What goes where (client)

File	Put it here	Wrong place
`eventlens-neoforge-*.jar` (or Forge / Fabric mod)	Your instance `mods` folder	—
`eventlens-client-agent-*.jar`	A normal folder on disk + tell the launcher about it (below)	`mods/` (launcher says “not a valid mod file”)
`eventlens-observability-*.jar`	Same folder as the client agent jar	`mods/`

Client agent (NeoForge, Forge, and Fabric) — step by step

This is for your Minecraft launcher, not the server. The same eventlens-client-agent-1.12.2.jar works on NeoForge, Forge, and Fabric.

Step 1 — Download eventlens-client-agent-1.12.2.jar from the 1.12.2 release.

eventlens-observability-*.jar beside it is optional on 1.10.7+ (the agent jar is fat).

Step 2 — Put the agent jar in a normal folder (not mods/):

C:\Users\You\AppData\Roaming\eventlens-agents\eventlens-client-agent-1.12.2.jar

Step 3 — Copy this JVM argument (use your path, forward slashes even on Windows):

-javaagent:C:/Users/You/AppData/Roaming/eventlens-agents/eventlens-client-agent-1.12.2.jar

One line, no line breaks. Starts with -javaagent: then the full path.
Spaces in the path: -javaagent:"C:/Users/You/My Agents/eventlens-client-agent-1.12.2.jar"
Do not use a relative path unless you know the launcher’s working directory.

Step 4 — Paste into JVM arguments, not game arguments.

Prism Launcher / MultiMC

Select your NeoForge, Forge, or Fabric instance.
Edit (wrench) → Settings → Java.
Enable Custom Java arguments.
Paste the -javaagent:... line into JVM arguments (space, then paste, if there is already text).
OK, then Launch.

CurseForge app

Profile → ⋮ → Profile options.
Java Settings / Advanced.
Paste into JVM arguments. Save and Play.

If there is no JVM box, import the instance into Prism Launcher.

Modrinth App

Instance → Settings → Java / Advanced.
Paste into Custom JVM arguments, save, launch.

Other launchers or a .bat file

java -javaagent:C:/path/to/eventlens-client-agent-1.12.2.jar ... (rest of launch command)

The official Microsoft Minecraft Launcher does not expose JVM args for modded profiles. Use Prism, CurseForge, or Modrinth.

Step 5 — Fully restart the game (close Minecraft, launch again).

Step 6 — /eventlens status should say precise. Use [Copy JVM arg] in chat if you need the line again.

Instant crash after adding the JVM arg?

Wrong field — JVM / Java arguments, not game arguments, not mods/.
Bad path — open it in File Explorer; use a full path with /.
Typo — -javaagent: (colon), not = or -java-agent:.
Wrong jar — client uses eventlens-client-agent-*.jar. Paper uses eventlens-agent-*.jar.
Smart quotes — re-type the line.
Launcher log — Unable to access jarfile or agent failed.

Workaround: remove the JVM line. The client mod still works in dispatch-only.

Paper server agent (optional)

Download eventlens-agent-1.12.2.jar. Put it next to the server jar — not in plugins/.
Add to Paper’s startup JVM arguments:

-javaagent:/full/path/to/eventlens-agent-1.12.2.jar

Windows example: -javaagent:C:/server/eventlens-agent-1.12.2.jar

stop, then start (not /reload).
/eventlens status → Agent: attached, Mode: precise.

Dev runServer attaches this agent automatically. Agents load at Java startup, which is why they are not plugins.

First trace

On the Paper server (a click that “does the wrong thing”):

/eventlens status
/eventlens listeners PlayerInteractEvent --detail verbose
/eventlens trace start PlayerInteractEvent --preset block-flow

Reproduce the click in-game, then:

/eventlens trace view <sessionId>
/eventlens trace export <sessionId> --format bundle
/eventlens trace stop

Open the exported folder’s index.html (or the .zip from a hosted panel), or http://127.0.0.1:8765 on the server machine.

On the Minecraft client (same click, other half):

/eventlens status
/eventlens ui
/eventlens trace start ClientUseItemEvent

Click in the world, then /eventlens trace view or use the Sessions tab. To join both sides later: /eventlens trace correlate <serverSession> <clientSession> on the server.

<sessionId> is printed when the session starts. Click it in chat, or /eventlens trace list.

Words you will see

Word	Meaning
Event	Something that happened (`PlayerInteractEvent` = a click)
Listener	One plugin’s handler for that event
Cancelled	A plugin said “don’t do this action”
Session	One recording. Start → reproduce → view → stop
precise	Optional Java agent loaded; per-listener (or per-mod) times
dispatch-only	No agent. EventLens still traces; times are coarser
Hot event	Fires constantly (movement). Needs a filter and `--confirm-hot`

Commands

Alias: /el. All commands default to op.

Command	What it does
`/eventlens` or `/eventlens status`	Version, tracing state, agent mode
`/eventlens listeners <event>`	Who listens to this event (any Bukkit event)
`/eventlens events [text]`	Search the event catalog (`traceable`, `hot`, …)
`/eventlens plugin <name>`	One plugin’s listeners, timing, exceptions
`/eventlens plugin compare <a> <b>`	Compare two loaded plugins
`/eventlens exceptions`	Listener exceptions EventLens attributed
`/eventlens instrumentation test`	Agent / snapshot self-check
`/eventlens trace start …`	Start recording
`/eventlens trace view <id>`	Read the recording
`/eventlens trace stop`	Stop recording
`/eventlens trace export <id> --format bundle`	Shareable `index.html` folder

Full trace command list

/eventlens trace start <Event[,Event…]> [--preset <name>] [--plugin <name>] [--player <name>]
  [--world <name>] [--region x1,z1,x2,z2] [--cancelled any|yes|no]
  [--max-events n] [--max-duration 60s] [--slow-threshold 1ms]
  [--capture-stacks] [--confirm-hot] [--generic] [--detail brief|normal|verbose]

/eventlens trace stop [sessionId]
/eventlens trace restart <sessionId>
/eventlens trace list
/eventlens trace view <sessionId> [page] [--run <n>] [--dispatch <n>] [--plugin <name>]
  [--detail brief|normal|verbose] [--unchanged] [--changed] [--slow] [--conflict]
/eventlens trace live <sessionId> [--channels frequency,slow,cancel,exception,alert]
  [--display chat|actionbar|bossbar] [--filter-plugin <name>]
  [--threshold 1ms] [--burst 50] [--aggregate 3s]
/eventlens trace live status|stop|pause|resume
/eventlens trace export <sessionId> [--format json|ndjson|text|html|bundle] [--shareable|--full]
/eventlens trace copy <sessionId> [--dispatch <n>] [--shareable|--full]
/eventlens trace compare <sessionA> <sessionB> [--plugin <name>]
/eventlens trace correlate <serverSession> <clientSession>
/eventlens trace baseline save|list|compare|delete …
/eventlens trace history
/eventlens trace favorite list|add|remove <event>
/eventlens trace presets

Built-in presets: dev-debug, quick-interact, plugin-focus, block-flow, inventory-flow, chat-flow.

Permissions (all default op): eventlens.command.status, .listeners, .plugin, .instrumentation, .trace (plus children such as .trace.export.full for unredacted --full exports).

Trace tips

Allowlisted types get detailed snapshots (142 Paper types — search with /eventlens events <text>). Any other registered Bukkit event needs --generic (common fields only). listeners still lists every registered event.
Several types at once: /eventlens trace start PlayerInteractEvent,BlockBreakEvent or --preset block-flow.
Hot events such as PlayerMoveEvent need a narrowing filter and --confirm-hot.
stop with an id stops that session; omit the id to stop all of yours.
restart reuses the same id and keeps earlier runs. View a run with --run <n>.
Exports are redacted by default (player names, worlds, coordinates, paths). --full needs eventlens.command.trace.export.full.
bundle writes a folder: open index.html. json is the full dump.

Live feed, correlation, allowlist

Live feed (in-game player required) while a session runs:

/eventlens trace live <sessionId> --display actionbar
/eventlens trace live --filter-plugin WorldGuard
/eventlens trace live pause

Client–server correlation: a right-click is two traces (client + server). After you export both:

/eventlens trace correlate <serverSession> <clientSession>

trace view shows Linked when a dispatch has a peer. Live pairing uses the eventlens:correlate plugin channel when the player has a client mod and the server is running EventLens. Paper traces never require the client mod.

Allowlisted Paper events: 142 first-class snapshot types (combat, interact, inventory, progress, blocks, entities, weather/raid/chunk, craft/enchant/brew, async pre-login). Add more class names in config.yml under trace.additional-events, or start a custom event with --generic.

Dashboard

Same viewer, two ways in:

Live (same machine) — with the Paper plugin running, open http://127.0.0.1:8765 on the computer that runs the server. Pick a live session or a saved report.
Live (VPS / hoster with a port) — set a long dashboard.token (12+ characters) and dashboard.bind-address: 0.0.0.0 in config.yml, stop the server (not /reload), then open http://YOUR_IP:8765/?token=YOUR_TOKEN. EventLens will not start a remote dashboard without that token.
Offline / no open port (Aternos-style hosts) — /eventlens trace export <id> --format bundle, download plugins/EventLens/reports/*-bundle.zip from the host file manager, unzip it, and open index.html. Works from file://.

Views: Overview, Timeline, Flame graph, Event graph, Plugin graph, Compare. Click a dispatch to open detail. Overview pages recent dispatches eight at a time.

Do not advertise an unauthenticated serverip:8765. Leave dashboard.token empty unless you intend to bind beyond localhost.

Configuration

plugins/EventLens/config.yml is created on first start. You can leave it alone.

Key	Default	Purpose
`dashboard.enabled`	`true`	Local HTTP viewer
`dashboard.port`	`8765`
`dashboard.bind-address`	`127.0.0.1`	Localhost only unless you also set a token
`dashboard.token`	empty	Required (12+ characters) to bind beyond localhost
`output.detail-level`	`normal`	Chat verbosity
`trace.slow-threshold-default`	`1ms`	Slow-listener flag
`trace.additional-events`	`[]`	Extra event class names
`trace.require-hot-event-confirmation`	`true`	Gate `PlayerMoveEvent` and similar
`reports.retention-days`	`30`	How long export files stay

More keys, limits, and privacy

Also: reports.auto-cleanup, trace.live.*, trace.presets, preferences.max-recent-traces, preferences.max-favorites.

Default limits: 4 concurrent sessions, 4,096 records per session, 256 listener records per dispatch, 32 MiB export file. Design overhead targets (average ≤ 0.25 ms, p95 ≤ 0.75 ms) are EventLens defaults, not Paper guarantees. EventLens throttles or stops a session if its own overhead stays too high.

Privacy: no external telemetry. Shareable exports redact player names, world names, exact coordinates, and paths unless you pass --full. The dashboard binds to localhost by default and requires a token to bind remotely.

FAQ

Is there an installer? Yes — download eventlens-setup-1.12.2.jar and see Setup wizard. It copies jars and can patch Paper or Prism startup files. For hand install, unzip EventLens-1.12.2-manual.zip.

Setup jar errors with Java SE / UnsupportedClassVersionError. Windows associated the jar with Java SE Platform Binary (Java 8). Right-click → Open with → OpenJDK Platform Binary, or install Java 21+ from Adoptium. The wizard will relaunch OpenJDK 21+ automatically when it can find it.

Do I need a Java agent? EventLens works without one (dispatch-only). Add the matching agent if you want precise per-listener or per-mod times. The wizard can do this for you.

Can I /reload? No. Always stop, then start.

java -version says 1.8 or 17. The plugin needs Java 25. Point JAVA_HOME at a Java 25 JDK, then restart the server.

Dashboard is blank / connection refused. On the server machine, open http://127.0.0.1:8765. From another PC or a VPS, set dashboard.token and dashboard.bind-address: 0.0.0.0, then use http://YOUR_IP:8765/?token=.... If the host cannot open a port, export a bundle zip instead.

Commands say I don’t have permission. They default to op. Give eventlens.command.status (and the others you need) if you use a permissions plugin.

I put the client agent in mods/ and the launcher complains. That jar is not a mod. See Java agents.

Does this work on Folia / Velocity / Spigot? Paper 26.2 only. Not Folia, Velocity, or a plain Spigot jar.

Will EventLens break my plugins? It must not change observed events. If a trace looks wrong, that is a bug — open an issue.

Client mods

Install steps are under Minecraft client. Agent steps are under Java agents.

Chat commands, Screen, HUD, and keybinds work on NeoForge, Forge, and Fabric. For precise per-mod timing, add the client Java agent (launcher JVM args — not mods/).

	NeoForge	Forge	Fabric
Minecraft	26.2	26.2	26.2
Chat: status, listeners, trace	yes	yes	yes
`/eventlens mod` profile	`@SubscribeEvent` scan	`@SubscribeEvent` scan	coarse loaded-mod list
Screen + HUD (`/eventlens ui`)	yes	yes	yes
Restores last tab / session	yes	yes	yes
Client Java agent (`precise`)	yes	yes	yes

/eventlens on the client shows precise when the client agent loaded, otherwise dispatch-only plus [Copy JVM arg] / [Agent guide].

Client commands, Screen, and events

/eventlens
/eventlens listeners <ClientEvent>
/eventlens mod <id>
/eventlens mod compare <a> <b>
/eventlens exceptions
/eventlens ui
/eventlens trace start <ClientEvent> [--mod <id>] [--player <name>] [--max-events n] [--confirm-hot]
/eventlens trace stop|pause|resume [sessionId]
/eventlens trace restart <sessionId>
/eventlens trace list
/eventlens trace view <sessionId>
/eventlens trace export <sessionId> [--format json|ndjson|text|html] [--shareable|--full]

Open the Screen with /eventlens ui, chat [Open UI], or bind key.eventlens.open (Controls → EventLens). The world keeps running so traces still capture. Closing restores the last tab and session.

Tab	What you do
Home	Platform, tracing, precise vs dispatch-only, HUD toggle
Events	Search 55 client events, Start (hot events confirm). Double-click starts.
Sessions	View, Pause / Resume, Restart, Stop, Export. Double-click opens.
Session	Dispatch list and Fields / Handlers detail

HUD is off by default (key.eventlens.hud). While a session is active it shows the last dispatch, duration, and cancel state.

/eventlens mod on NeoForge/Forge uses scanned @SubscribeEvent rows. addListener() consumers need the client agent. Fabric lists a short set of loaded mod ids, not a full callback inventory.

Not traced: per-frame render events (RenderGuiEvent, RenderLivingEvent, and similar) and one-shot mod-bus registration events. Fabric still does not hook every NeoForge/Forge game-bus event.

Event	Hot?	Meaning
`ClientTickEvent`	yes	Every client tick
`ClientWorldTickEvent`	yes	Every client world tick
`ClientPlayerTickEvent`	yes	Every local player tick
`ClientChatEvent`		Chat you send
`ClientChatReceivedEvent`		Chat you receive
`ClientScreenOpenEvent` / `ClientScreenCloseEvent`		Screen opened / closed
`ClientAttackEvent`		Attack an entity or air
`ClientAttackBlockEvent`		Punch a block
`ClientUseItemEvent` / `ClientUseBlockEvent` / `ClientUseEntityEvent` / `ClientUseEmptyEvent`		Right-click item, block, entity, or air
`ClientPlayerMoveEvent`	yes	Position changed
`ClientMovementInputEvent`	yes	Movement keys updated
`ClientJoinEvent` / `ClientDisconnectEvent`		Joined / left a world
`ClientRespawnEvent`		Respawned
`ClientGameTypeChangeEvent`		Game mode changed
`ClientPauseEvent`		Pause state changed
`ClientKeyEvent` / `ClientMouseButtonEvent` / `ClientMouseScrollEvent`		Input
`ClientInteractionKeyEvent`		Attack, use, or pick keybind
`ClientTooltipEvent`	yes	Item tooltip gathered
`ClientScreenshotEvent` / `ClientToastEvent` / `ClientSoundEvent`		Screenshot, toast, sound
`ClientEntityJoinEvent` / `ClientEntityLeaveEvent`	yes	Entity loaded / unloaded
`ClientChunkLoadEvent` / `ClientChunkUnloadEvent`	yes	Chunk loaded / unloaded
`ClientRecipesUpdatedEvent`		Recipe book synced
`ClientItemTossEvent`		You dropped an item
`ClientItemPickupEvent`	yes	You picked up an item
`ClientDeathEvent`		A living entity died on the client
`ClientHurtEvent`	yes	You took damage
`ClientUseEntityAtEvent`		Right-click a specific point on an entity
`ClientUseItemFinishEvent`		Finished using an item
`ClientContainerOpenEvent` / `ClientContainerCloseEvent`		Container menu opened / closed
`ClientBreakSpeedEvent`	yes	Mining speed calculated
`ClientHealEvent`		Your health increased
`ClientFoodEvent` / `ClientAirEvent` / `ClientXpEvent`		Food, air, or XP changed
`ClientSelectedSlotEvent`		Hotbar slot changed
`ClientSprintEvent` / `ClientSneakEvent` / `ClientJumpEvent`		Movement state
`ClientGlideEvent` / `ClientSwimEvent` / `ClientSleepEvent`		Elytra, swim, or sleep
`ClientScreenClickEvent` / `ClientScreenKeyEvent`	yes	Click or key inside a screen

Compatibility (1.x)

These stay compatible across 1.x. Breaking them is a major version.

Contract	Current
Commands, permissions, `/el`	as documented above
Export JSON `reportVersion`	`2` (extra optional fields may appear)
Agent protocol	`2` (minimum `1`). Mismatch → `/eventlens status`, not silent wrong timings
Paper	26.2 · Java 25 (no multi-version jar)
Client mods	Minecraft 26.2 (NeoForge, Forge, Fabric)

Not in this project: Folia, Velocity, packet sniffing, event replay, network telemetry, Hangar / Modrinth / CurseForge publishing.

Development

.\gradlew.bat check
.\gradlew.bat runServer
.\gradlew.bat :eventlens-setup:runSetup

Java 25, Gradle Wrapper 9.6.1, Paper 26.2. Stop the test server with stop. CI runs ./gradlew check and Windows paperSmokeTest on push/PR.

Tasks, layout, and local Java 8 terminals

.\gradlew.bat paperSmokeTest
.\gradlew.bat runServerDebug          # JDWP 127.0.0.1:5005
.\gradlew.bat :eventlens-neoforge:runClient
.\gradlew.bat :eventlens-forge:runClient
.\gradlew.bat :eventlens-fabric:runClient
.\gradlew.bat --stop

If java -version shows 1.8 in a terminal:

$env:JAVA_HOME = [Environment]::GetEnvironmentVariable('JAVA_HOME','User')
$env:Path = "$env:JAVA_HOME\bin;" + $env:Path
.\gradlew.bat --stop

Path	Role
`eventlens-core`	Domain and application services (no Bukkit / Minecraft)
`eventlens-paper`	Paper plugin, commands, dashboard, bundle export
`eventlens-observability`	Shared agent protocol (Java 21 bytecode)
`eventlens-agent`	Optional Paper `-javaagent`
`eventlens-client-agent`	Optional client `-javaagent`
`eventlens-mod-common`	Shared client command / trace logic
`eventlens-neoforge` / `forge` / `fabric`	Client mods
`eventlens-setup`	Desktop setup wizard
`eventlens-viewer`	Dashboard TypeScript (bundled into the plugin)
`eventlens-testkit`	Fixture plugin for tests

Base package: dev.bellaouzo.eventlens. Main class: dev.bellaouzo.eventlens.EventLens.

License

MIT. See LICENSE.

Issues: github.com/bellaouzo/EventLensMC/issues
Changes: CHANGELOG.md
Vulnerabilities: SECURITY.md

Navigation Menu

Repository files navigation

EventLens

What it is

What to download

Install

Setup wizard

Paper server

Minecraft client

Java agents (optional)

What goes where (client)

Client agent (NeoForge, Forge, and Fabric) — step by step

Paper server agent (optional)

First trace

Words you will see

Commands

Dashboard

Configuration

FAQ

Client mods

Compatibility (1.x)

Development

License

About

Releases

Packages

Contributors

Languages

Name		Name	Last commit message	Last commit date
.cursor/rules		.cursor/rules
.github/workflows		.github/workflows
.vscode		.vscode
META-INF		META-INF
bin		bin
eventlens-agent		eventlens-agent
eventlens-client-agent		eventlens-client-agent
eventlens-core		eventlens-core
eventlens-fabric		eventlens-fabric
eventlens-forge		eventlens-forge
eventlens-mod-common		eventlens-mod-common
eventlens-neoforge		eventlens-neoforge
eventlens-observability		eventlens-observability
eventlens-paper		eventlens-paper
eventlens-setup		eventlens-setup
eventlens-testkit		eventlens-testkit
eventlens-viewer		eventlens-viewer
gradle/wrapper		gradle/wrapper
net/minecraftforge/client/event		net/minecraftforge/client/event
scripts		scripts
.cursorignore		.cursorignore
.cursorindexingignore		.cursorindexingignore
.gitignore		.gitignore
CHANGELOG.md		CHANGELOG.md
LICENSE		LICENSE
README.md		README.md
SECURITY.md		SECURITY.md
build.gradle		build.gradle
forge-fabric-errors.txt		forge-fabric-errors.txt
gradle.properties		gradle.properties
gradlew		gradlew
gradlew.bat		gradlew.bat
knip.json		knip.json
package.json		package.json
settings.gradle		settings.gradle

Latest commit

History

Folders and files

Repository files navigation

EventLens

What it is

What to download

Install

Setup wizard

Paper server

Minecraft client

Java agents (optional)

What goes where (client)

Client agent (NeoForge, Forge, and Fabric) — step by step

Paper server agent (optional)

First trace

Words you will see

Commands

Dashboard

Configuration

FAQ

Client mods

Compatibility (1.x)

Development

License

About

Topics

Resources

Security policy

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages