Installation
- 1Download the jar from your account page.
- 2Drop it into plugins/ and restart the server. A reload is not enough for a first install.
- 3That is the whole install — there are no dependencies and the defaults are usable as shipped.
- 4Optional: run /crops stats to confirm it is seeing your farms once someone has walked into one.
What players actually do
/crops opens a six-row settings screen. Every row states its current answer in words rather than relying on an icon colour, and there are six settings rather than twenty.
Markers appear over ready crops only. Nearly-ready markers and percentages both exist and are both off by default — detail is the thing this plugin removes, so a marker that means "not yet" would work against the one that means "harvest this".
Everything is per player and remembered across sessions in players.yml.
Tuning it for your server
The settings that matter are in the performance block of config.yml.
performance:
render-interval-ticks: 10 # how often markers redraw
sections-per-tick: 2 # ceiling on scanning work per tick
max-cached-sections: 512 # index size before least-used are dropped
max-radius: 16 # furthest a player may set their own range
vertical-range: 4 # how far up and down to look
max-markers-per-player: 48 # nearest are kept beyond thisRaising render-interval-ticks lowers average cost without creating a spike, because players are spread across the window rather than all redrawn on the same tick. sections-per-tick is the hard ceiling on scanning: raise it if markers are slow to appear when someone arrives at a large farm, lower it on a very busy server.
vertical-range is the one that surprises people. Crops sit in a thin slab, so searching a full view distance vertically would be almost entirely wasted reads — but it also means a farm more than four blocks above or below a player will not be marked until they are level with it.
Marker styles
Six styles: White beam, Green sparkle, Soft glow, Flame, Bright burst and Coloured dot.
They are six different particles, not one particle in six colours. That is the point — colour is the channel some players cannot read, so it never carries the meaning. White beam is the default because it has the highest contrast against green crops and brown soil; Flame tends to win in dark or underground farms.
Coloured dot is the one style whose colour you set, in display.dot-colour as an R,G,B triple. It exists for people who have a specific colour that works for them, not as the general answer.
Adding or changing crops
Crops are a list in config.yml, so a server on a version that lacks one is not an error.
crops:
- material: WHEAT
name: Wheat
ready-at-age: MAX
- material: SWEET_BERRY_BUSH
name: Sweet berries
ready-at-age: 2ready-at-age is MAX for almost everything, meaning whatever maximum that block reports on your version — it is read from the block rather than hard-coded, so a version that changes a crop’s stage count needs no edit. Sweet berries are the exception that proves the field is needed: they are pickable at 2 of 3.
name is what players are shown, so write it in plain words rather than leaving the material name.
Commands
| Command | What it does | Permission |
|---|---|---|
/crops | Open your settings | cropsight.use |
/crops on | Turn markers on | cropsight.use |
/crops off | Turn markers off | cropsight.use |
/crops here | What is ready around you, and how far the nearest is | cropsight.use |
/crops style (name) | Change the marker look | cropsight.use |
/crops radius (blocks) | How far markers reach | cropsight.use |
/crops narration on|off | Name the crop you look at | cropsight.use |
/crops stats | What CropSight is costing this server | cropsight.admin |
/crops reload | Re-read config.yml | cropsight.admin |
Still stuck?
Post in Discord with your server version and the relevant part of the log. That is almost always enough to get a straight answer the same day.
Get help