Command History Context

Quick rating

Command History Context

No reviews yet

A profile-based command history manager for Minecraft.

QoL & Tweaks
Mod Loaders
Fabric
Minecraft

Community voices

Reviews

Versions
Loading versions…
Match includes

Click once to include, again to exclude, again to clear

Rating Any
Any 0.5 1.0 1.5 2.0 2.5 3.0 3.5 4.0 4.5 5.0
Min
Max
Play Status
Reviews
Time Played
hrs+
Verified developers only
Has developer response
List view
Grid view
Compact view
Sort by
Date
Rating
Helpful
Unhelpful
Edited
Sort ascending
Delete this review?

This removes your review from the project. You can write a new review after.

Review submitted for moderation

Your review has been sent to moderators, who will check that it meets our guidelines before it appears publicly.

No reviews yet. Be the first to review this project!

Get it on

Available Platforms

About

Project Details

Type
Mod
Latest Version
CommandHistoryContext 1.0.0 for 1.21.9
Authors

For authors

Embed Badge

If you're the author of this project, you can embed a live badge anywhere that supports HTML or Markdown. It updates automatically whenever ratings change.

Custom banner text
ModDex rating badge preview

Use HTML for any page that supports it, or Markdown for README files and Markdown-based descriptions.

Identifiers

Platform IDs

CurseForge ID

Resources

External Links

Source Issues Wiki Discord

About

Description

Command History Context

Command History Context is a mod that manages Minecraft command history using custom profiles.

In vanilla Minecraft, command history is shared across all environments, including single-player worlds and multiplayer servers. While this is convenient, it can become problematic when frequently switching between different purposes, such as development, testing, building, and regular gameplay, as commands from unrelated contexts can get mixed together.

This mod allows you to create custom profiles and assign servers or environments to them. Each profile maintains its own command history, allowing related environments to share history while keeping unrelated commands separated.

Features

  • Create custom command history profiles
  • Manage command history by purpose or environment
  • Share command history between servers in the same profile
  • Separate development, testing, and regular gameplay commands
  • Automatically switch the active history context based on the connected environment

Examples

Building Profile

  • build.example.com
  • test-build.example.com

Use the same command history across multiple building servers.

Development Profile

  • localhost:25565
  • dev.example.com

Share development-related commands between a local environment and a test server.

Personal Gameplay Profile

  • survival.example.com

Keep regular gameplay commands separate from development commands.

Why Command History Context?

In vanilla Minecraft, all command history is stored together across every environment.

However, when using multiple servers or worlds for different purposes, there are situations where you want to organize commands based not on which server you are connected to, but on what purpose the environment serves.

CommandHistoryContext organizes Minecraft's shared command history into separate contexts based on environments and use cases, providing a more flexible way to manage your commands.

Disclaimer

Some English text related to this project including parts of the Modrinth description and in-game messages was created with the help of machine translation tools.

Translation accuracy is not guaranteed.

Screenshots

Gallery

This project has no gallery images yet.

Versions

Files

Relations

Project Relations

More like this

Similar Mods

Suggestions use data such as tags, dependencies, dependents, descriptions, titles, and more to rank how much they overlap with this mod.

On ModDex

Community snapshot

0
Ratings
0
Followers
0
In stacks

By the numbers

Statistics

<1,000
Downloads
Last Updated
Created
Last synced
When ModDex last fetched this project from CurseForge or Modrinth. Every project is re-checked on a schedule, and any project that ships a new file is synced automatically within hours of the release.
New file updates sync automatically
How syncing works