@bobschlowinskii/clicraft 0.4.0

package/CHANGELOG.md

@@ -0,0 +1,191 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+## [0.4.0] - 2026-01-22
+
+### Added
+
+- **Multi-Account Authentication** (`clicraft auth`)
+  - Support for multiple Microsoft/Minecraft accounts
+  - New unified `clicraft auth` command with subcommands:
+    - `auth login` - Add a new account or update existing
+    - `auth logout [account]` - Remove an account (interactive selection if multiple)
+    - `auth switch [account]` - Switch between saved accounts
+    - `auth status [account]` - Show all accounts or specific account details
+    - `auth list` - List all saved accounts
+  - Accounts stored in `~/.clicraft/auth/accounts.json`
+  - Active account highlighted with `▶` marker in status
+  - Token status (valid/expired) shown for each account
+  - Automatic migration from legacy `auth.json` format
+
+### Changed
+
+- **Auth Commands Restructured**
+  - Replaced standalone `login`, `logout`, `status` commands with `auth` subcommand
+  - Backward compatible `loadAuth()` and `refreshAuth()` exports maintained
+
+### Deprecated
+
+- Old `clicraft login`, `clicraft logout`, `clicraft status` commands are now under `clicraft auth`
+
+## [0.3.2] - 2026-01-22
+
+### Changed
+
+- **Major Codebase Refactoring**
+  - Created centralized helper modules for shared functionality
+  - `helpers/constants.js` - Centralized API URLs, user agent, pagination settings
+  - `helpers/utils.js` - Core utilities: fetchJson, downloadFile, loadConfig, saveConfig, paginatedSelect, mavenToPath
+  - `helpers/modrinth.js` - Modrinth API functions: getProject, getProjectVersions, searchMods, downloadMod, findMod
+  - `helpers/minecraft.js` - Minecraft/Fabric/Forge API: version fetching, library/asset downloads
+  - Eliminated 7+ duplicate function patterns across command files
+  - Reduced code duplication and improved maintainability
+  - All commands now use shared imports instead of local implementations
+
+## [0.3.1] - 2026-01-22
+
+### Added
+
+- **Uninstall Command** (`clicraft uninstall`)
+  - Remove mods from your Minecraft instance
+  - Interactive multi-select when no mod specified
+  - Confirmation prompt before deletion (skip with `--force`)
+  - Removes mod file and updates mcconfig.json
+
+## [0.3.0] - 2026-01-19
+
+### Added
+
+- **Config Command** (`clicraft config`)
+  - New command to manage CLI settings and game settings
+  - `config show` - Display CLI settings (Java path, memory, mod source)
+  - `config set <key> <value>` - Modify CLI settings
+  - `config ignore` - Show game settings ignore list
+  - `config ignore-add <pattern>` - Add pattern to ignore list (supports wildcards)
+  - `config ignore-remove <pattern>` - Remove pattern from ignore list
+  - `config defaults` - Show default game settings for new instances
+  - `config defaults-set <key> <value>` - Set a default game setting
+  - `config defaults-remove <key>` - Remove a default game setting
+  - `config defaults-clear` - Clear all default game settings
+  - `config capture` - Capture game settings from options.txt to mcconfig.json
+  - `config game-settings` - Show saved game settings in mcconfig
+  - `config clear-game-settings` - Remove game settings from mcconfig
+
+- **Global Configuration Directory** (`~/.clicraft/`)
+  - Centralized config directory for CLI-wide settings
+  - `settings.json` - CLI settings (Java path, memory, mod source, etc.)
+  - `game-settings-ignore.json` - Patterns for settings to exclude when capturing
+  - `default-game-settings.json` - Default Minecraft settings applied to new instances
+  - `auth.json` - Authentication tokens (migrated from ~/.mcpkg/)
+
+- **Game Settings in mcconfig.json**
+  - New `gameSettings` field to store Minecraft options
+  - Capture settings from options.txt with customizable ignore list
+  - Automatically apply game settings when creating from config
+
+- **Create from Existing Config** (`clicraft create` with mcconfig.json)
+  - Detects mcconfig.json in current directory
+  - Creates new instance from existing configuration
+  - Installs same Minecraft version, mod loader, and loader version
+  - Automatically installs all mods from the config
+  - Applies game settings if present
+
+- **Added `--mods` option to `clicraft info`** 
+  - Shows only installed mods instead of the entire instance info
+
+### Changed
+
+- Migrated auth storage from `~/.mcpkg/` to `~/.clicraft/`
+- Improved mod installation with better error handling
+
+## [0.2.2] - 2026-01-19
+
+- **Fixed Bugs**
+  - Fixed bug in `clicraft --version` where I forgot to put the exports
+  - Fixed bug from package.json where importing made a default object
+
+## [0.2.1] - 2026-01-18
+
+### Added
+
+- **Version Command** (`clicraft -v, --version`)
+  - Displays cool art and version!
+
+## [0.2.0] - 2026-01-18
+
+### Added
+
+- **Instance Info** (`clicraft info`)
+  - Display comprehensive instance information
+  - Shows instance name, type, mod loader, and versions
+  - Lists installed mods with version numbers
+  - Storage breakdown by directory (libraries, assets, mods, etc.)
+  - World saves count and details
+  - Verbose mode for detailed output (`--verbose`)
+
+- **Upgrade Command** (`clicraft upgrade`)
+  - Interactive upgrade menu for mods, loader, or Minecraft version
+  - Upgrade all mods at once to latest compatible versions
+  - Upgrade individual mods by name (`clicraft upgrade sodium`)
+  - Upgrade Fabric loader version with automatic library downloads
+  - Config format migration for future compatibility
+  - Force upgrade option (`--force`)
+
+- **Config Versioning**
+  - Added `configVersion` field to `mcconfig.json`
+  - Enables future migrations and compatibility checks
+
+### Changed
+
+- Improved mod tracking with `updatedAt` timestamp on upgrades
+
+## [0.1.0] - 2026-01-17
+
+### Added
+
+- **Instance Creation** (`clicraft create`)
+  - Interactive prompts for instance configuration
+  - Support for Fabric and Forge mod loaders
+  - Client and server instance types
+  - Automatic download of Minecraft client/server JAR
+  - Automatic download of all required libraries
+  - Automatic download of game assets
+  - Paginated version selection (10 items per page)
+  - Creates `mcconfig.json` with instance metadata
+
+- **Mod Search** (`clicraft search`)
+  - Search mods on Modrinth by name
+  - Filter by Minecraft version (`--version`)
+  - Filter by mod loader (`--loader`)
+  - Limit results (`--limit`)
+  - Displays download counts, supported loaders, and Modrinth links
+
+- **Mod Installation** (`clicraft install`)
+  - Install mods from Modrinth to instance
+  - Automatic version matching for Minecraft version and loader
+  - Dependency detection with warnings
+  - Force reinstall option (`--force`)
+  - Instance path option (`--instance`)
+
+- **Microsoft Authentication** (`clicraft login`, `clicraft logout`, `clicraft status`)
+  - Microsoft OAuth login via browser
+  - Xbox Live and Minecraft Services authentication
+  - Token refresh for persistent sessions
+  - Secure token storage in `~/.mcpkg/auth.json`
+
+- **Game Launching** (`clicraft launch`)
+  - Launch Minecraft directly from terminal
+  - Automatic classpath building for vanilla and Fabric libraries
+  - Support for offline mode (`--offline`)
+  - Verbose output option (`--verbose`)
+  - Instance path option (`--instance`)
+
+### Technical Details
+
+- Built with Node.js ES modules
+- Uses Commander.js for CLI interface
+- Uses Inquirer.js for interactive prompts
+- Chalk for colored terminal output
+- Native fetch API (Node.js 18+)
+- Supports Linux, macOS, and Windows

package/CONTRIBUTING.md

@@ -0,0 +1,261 @@
+# Contributing to CLIcraft
+
+Thank you for your interest in contributing to CLIcraft! We welcome contributions from the community.
+
+## 📋 Table of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [Getting Started](#getting-started)
+- [Development Setup](#development-setup)
+- [How to Contribute](#how-to-contribute)
+- [Pull Request Process](#pull-request-process)
+- [Coding Guidelines](#coding-guidelines)
+- [Reporting Issues](#reporting-issues)
+- [Community](#community)
+
+## 🤝 Code of Conduct
+
+We are committed to providing a welcoming and inclusive environment for all contributors. Please be respectful and constructive in all interactions.
+
+### Our Standards
+
+- **Be respectful**: Treat everyone with respect and kindness
+- **Be constructive**: Provide helpful feedback and suggestions
+- **Be patient**: Remember that everyone has different levels of experience
+- **Be inclusive**: Welcome newcomers and help them get started
+
+## 🚀 Getting Started
+
+Before you begin contributing, please:
+
+1. Read through the [documentation](https://benjamin.bsstudios.org/clicraft)
+2. Check the [existing issues](https://github.com/theinfamousben/clicraft/issues) to see if your idea or bug has already been reported
+3. Look at open [pull requests](https://github.com/theinfamousben/clicraft/pulls) to avoid duplicate work
+
+## 💻 Development Setup
+
+### Prerequisites
+
+- **Node.js** 18 or higher
+- **Java** 21 or higher (for testing Minecraft functionality)
+- **Git** for version control
+
+### Setting Up Your Development Environment
+
+1. **Fork the repository** on GitHub
+
+2. **Clone your fork**:
+   ```bash
+   git clone https://github.com/YOUR-USERNAME/clicraft.git
+   cd clicraft
+   ```
+
+3. **Add the upstream remote**:
+   ```bash
+   git remote add upstream https://github.com/theinfamousben/clicraft.git
+   ```
+
+4. **Install dependencies**:
+   ```bash
+   npm install
+   ```
+
+5. **Link the package locally** (to test your changes):
+   ```bash
+   npm link
+   ```
+
+6. **Verify the installation**:
+   ```bash
+   clicraft --version
+   ```
+
+### Project Structure
+
+```
+clicraft/
+├── commands/      # Command implementations
+├── helpers/       # Utility functions
+├── docs/          # Documentation
+├── index.js       # Main entry point
+└── package.json   # Project metadata
+```
+
+## 🛠️ How to Contribute
+
+### Types of Contributions
+
+We welcome various types of contributions:
+
+- **Bug fixes**: Fix issues reported in the issue tracker
+- **New features**: Add new functionality to CLIcraft
+- **Documentation**: Improve or add documentation
+- **Tests**: Add or improve test coverage
+- **Code improvements**: Refactor code for better performance or readability
+
+### Making Changes
+
+1. **Create a new branch** for your work:
+   ```bash
+   git checkout -b feature/your-feature-name
+   ```
+   
+   Use descriptive branch names:
+   - `feature/add-mod-search-filter`
+   - `bugfix/fix-launch-error`
+   - `docs/update-installation-guide`
+
+2. **Make your changes** following the [coding guidelines](#coding-guidelines)
+
+3. **Test your changes**:
+   ```bash
+   # Test the CLI manually
+   clicraft --help
+   clicraft create
+   # etc.
+   ```
+
+4. **Update documentation** if needed:
+   - Update `README.md` for user-facing changes
+   - Update docs in the `docs/` folder for detailed documentation
+   - Add inline comments for complex code
+
+5. **Commit your changes**:
+   ```bash
+   git add .
+   git commit -m "Brief description of changes"
+   ```
+   
+   Write clear, concise commit messages:
+   - ✅ "Add filter option to search command"
+   - ✅ "Fix authentication error on Windows"
+   - ❌ "Update stuff"
+   - ❌ "WIP"
+
+## 🔄 Pull Request Process
+
+1. **Update your fork** with the latest upstream changes:
+   ```bash
+   git fetch upstream
+   git rebase upstream/main
+   ```
+
+2. **Push your branch** to your fork:
+   ```bash
+   git push origin feature/your-feature-name
+   ```
+
+3. **Create a Pull Request** on GitHub:
+   - Use a clear, descriptive title
+   - Describe what changes you made and why
+   - Reference any related issues (e.g., "Fixes #123")
+   - Include screenshots or examples if applicable
+
+4. **Wait for review**:
+   - A maintainer will review your PR
+   - Address any feedback or requested changes
+   - Once approved, your PR will be merged
+
+### Pull Request Guidelines
+
+- **Keep PRs focused**: One feature or fix per PR
+- **Write clear descriptions**: Explain what and why, not just how
+- **Include examples**: Show how to use new features
+- **Update CHANGELOG.md**: Add your changes under the "Unreleased" section
+- **Be responsive**: Respond to review comments promptly
+
+## 📝 Coding Guidelines
+
+### JavaScript Style
+
+- Use **ES6+ syntax** (arrow functions, const/let, template literals, etc.)
+- Use **4 spaces** for indentation
+- Use **descriptive variable names**
+- Add **comments** for complex logic
+- Follow existing code style in the project
+
+### Best Practices
+
+- **Error handling**: Always handle errors gracefully with helpful messages
+- **User feedback**: Use chalk for colored console output
+- **Async/await**: Prefer async/await over callbacks or raw promises
+- **Modularity**: Keep functions small and focused on a single task
+- **Validation**: Validate user input before processing
+- **Prettier**: Code styling should automatically applied by prettier (i think)
+
+### Example Code Style
+
+```javascript
+import chalk from 'chalk';
+
+async function searchMods(query, options = {}) {
+    try {
+        // Validate input
+        if (!query || query.trim() === '') {
+            console.error(chalk.red('Error: Search query cannot be empty'));
+            return;
+        }
+
+        // Perform search
+        const results = await fetchFromModrinth(query, options);
+    
+        // Display results
+        if (results.length === 0) {
+            console.log(chalk.yellow('No mods found matching your query'));
+            return;
+        }
+
+        displayResults(results);
+    } catch (error) {
+        console.error(chalk.red(`Search failed: ${error.message}`));
+    }
+}
+```
+
+## 🐛 Reporting Issues
+
+### Before Submitting an Issue
+
+1. **Search existing issues** to avoid duplicates
+2. **Update to the latest version** to see if the issue is already fixed
+3. **Gather information**:
+   - Your operating system and version
+   - Node.js version (`node --version`)
+   - CLIcraft version (`clicraft --version`)
+   - Steps to reproduce the issue
+   - Expected vs actual behavior
+   - Error messages or logs
+
+### Submitting an Issue
+
+When creating an issue, please include:
+
+- **Clear title**: Describe the issue in one line
+- **Description**: Explain the issue in detail
+- **Steps to reproduce**: List exact steps to trigger the issue
+- **Expected behavior**: What should happen
+- **Actual behavior**: What actually happens
+- **Environment**: OS, Node.js version, etc.
+- **Screenshots**: If applicable
+
+### Issue Labels
+
+- `bug`: Something isn't working
+- `enhancement`: New feature or request
+- `documentation`: Documentation improvements
+- `help wanted`: Extra attention needed
+- `good first issue`: Good for newcomers
+
+## 💬 Community
+
+- **GitHub Issues**: For bug reports and feature requests
+- **GitHub Discussions**: For questions and general discussion
+- **Pull Requests**: For code contributions
+
+## 📜 License
+
+By contributing to CLIcraft, you agree that your contributions will be licensed under the ISC License.
+
+---
+
+Thank you for contributing to CLIcraft! Your efforts help make this tool better for everyone. 🎮✨

package/LICENSE.md

@@ -0,0 +1,7 @@
+ISC License
+
+Copyright 2026 Benjamin Mueller
+
+Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.
+
+THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

package/README.md

@@ -0,0 +1,55 @@
+# CLIcraft
+## [READ THE DOCS](https://benjamin.bsstudios.org/clicraft)
+
+
+A simple Minecraft Mod Package Manager and launcher written in Node.js. Create and manage Minecraft instances with Fabric or Forge mod loaders, search and install mods from Modrinth, and launch the game directly from the command line.
+
+## Why CLIcraft?
+Unlike other PMs or Launchers, CLIcraft can do both! Simply type a few commands and you're playing fabric or forge minecraft.
+
+## Features
+
+- 🎮 **Create Instances** - Set up new Minecraft client or server instances with Fabric or Forge
+- 🔍 **Search Mods** - Find mods on Modrinth with filters for version, loader, and more
+- 📦 **Install Mods** - Download and install mods directly to your instance
+- � **Upgrade** - Update mods, mod loader, or Minecraft version
+- ℹ️ **Instance Info** - View detailed information about your instances
+- �🔐 **Microsoft Login** - Authenticate with your Microsoft account to play online
+- 🚀 **Launch Game** - Start Minecraft directly from the terminal
+
+## Installation
+
+### Cloning from Source
+```bash
+# Clone the repository
+git clone https://github.com/theinfamousben/clicraft.git
+cd clicraft
+
+# Install dependencies
+npm install
+
+# Link globally (optional, for using 'clicraft' command anywhere)
+npm link
+```
+### Install NPM Package
+**npm package coming soon!**
+
+
+## Requirements
+
+- Node.js 18 or higher
+- Java 21 or higher (for running Minecraft)
+
+## Supported Platforms
+
+- ✅ Linux
+- ✅ macOS
+- ✅ Windows
+
+## License
+
+ISC
+
+## Contributing
+
+Contributions are welcome! Please read our [Contributing Guide](CONTRIBUTING.md) to learn how to get started. You can also open an issue or submit a pull request on [GitHub](https://github.com/theinfamousben/clicraft).