Merge main

.env.example

@@ -0,0 +1,4 @@
+# Experimental flags — copy to .env and edit as needed
+use_new_networking=true
+show_sandbox_collection=false
+alt_stakes=false

.github/FUNDING.yml

@@ -0,0 +1 @@
+ko_fi: virtualized

.github/RELEASE_CHECKLIST.md

@@ -0,0 +1,23 @@
+# RELEASE CHECKLIST
+
+## Creating the main ZIP
+*(This ensures we keep the DEV tag on the source code and ensures BMM and balatromp.com don't break, since they rely on the "BalatroMultiplayer.zip" file existing for each release)*
+1. Download the source code.
+2. Uncompress the source code and open `Multiplayer.json` to remove "~DEV" from the version tag.
+3. Recompress the source code, ensuring to recomopress from the files instead of the outer folder, and name it exactly "BalatroMultiplayer.zip".
+4. Upload `BalatroMultiplayer.zip` with the release.
+5. Upload `BalatroMultiplayer.zip` to [balatromp.com's releases page](https://balatromp.com/admin/releases)
+    - Ensure that the Steamodded version is set to the intended Steamodded version for ranked
+    - Ensure that the Lovely version is set to the intended Lovely version for ranked
+    - Ensure that the Branch is set to main
+    - Ensure the Version matches exactly the version in Multiplayer.json
+
+## Uploading the server files
+*(We upload the server files for each OS with every release so that people don't have to go digging for these files)*
+- If the server **has not** changed since last update then simply download the `server-win.exe`, `server-macos`, and `server-linux` files from the previous releasee and upload them with the new release.
+- If the server **has** changed since last update then run the build script for the server files locally, and upload the `server-win.exe`, `server-macos`, and `server-linux` files created in the `build` folder.
+
+## After release
+- Increase the version in the `Multiplayer.json` of main branch to be one patch version above the previous release, and ensure the "~DEV" tag still exists.
+  - Eg. "0.2.18~DEV" -> "0.2.19~DEV", Or if a higher version like 1.0 was released then it should become "1.0.1~DEV"
+- If the recommended Steamodded or Lovely was updated then be sure to update `README.md` and `CONTRIBUTING.md` with the correct versions.

.gitignore

@@ -1,4 +1,7 @@
-ref.lua
-node_modules
+.vscode
+.luarc.json
+.idea
+.lovelyignore
+.vs
+.DS_Store
 .env
-Config.lua

CONTRIBUTING.md

@@ -0,0 +1,123 @@
+# Contributing to Balatro Multiplayer
+
+Thank you for your interest in contributing to Balatro Multiplayer! We're building the definitive multiplayer experience for Balatro. Ready to make poker roguelikes even more unhinged? You've found the right repo.
+
+This little guide will help ensure consistency and quality across the codebase. Follow it and your PRs will merge. Ignore it and maintainers will reject your PR with the enthusiasm of a Neptune card.
+
+Let's build something that would make Jimbo proud.
+
+## Quick Start
+
+**Prerequisites**: Install [Steamodded 1.0.0~BETA-1016c](https://github.com/Steamodded/smods/releases/tag/1.0.0-beta-1016c) and [Lovely Injector](https://github.com/ethangreen-dev/lovely-injector) (>=0.8)
+
+```bash
+# 1. Fork on GitHub, then clone
+git clone https://github.com/YOUR_USERNAME/BalatroMultiplayer.git
+cd BalatroMultiplayer
+
+# 2. Set up remotes and install stylua
+git remote add upstream https://github.com/Balatro-Multiplayer/BalatroMultiplayer.git
+# Install stylua from: https://github.com/JohnnyMorganz/StyLua
+
+# 3. Ready to develop!
+git checkout -b feature/your-feature
+# Make changes, then:
+stylua .
+git commit -m "your changes"
+```
+
+## Development Workflow
+
+```bash
+# Sync and create branch
+git checkout main && git pull upstream main && git push origin main
+git checkout -b feature/your-feature
+
+# Develop → Format → Commit → Push → PR
+stylua . && git add . && git commit -m "feat: your change"
+git push origin feature/your-feature
+# Then create PR on GitHub
+```
+
+**Verify Setup**: Test that stylua works (`stylua --version`) before starting development.
+
+### Code Formatting
+
+We use [stylua](https://github.com/JohnnyMorganz/StyLua) for consistent code formatting.
+
+**Before submitting a PR**:
+```bash
+stylua --check .
+stylua .  # to format all files
+```
+
+**IDE/Editor Setup**: Most editors have Lua language support plugins that can format code on save using stylua:
+- **VS Code**: [Lua Language Server extension](https://marketplace.visualstudio.com/items?itemName=sumneko.lua) + StyLua
+- **JetBrains**: [SumnekoLua](https://plugins.jetbrains.com/plugin/22315-sumnekolua) + StyLua
+
+**File Structure**:
+- Keep related functionality in logical directories (`objects/`, `ui/`, `networking/`)
+- Use descriptive filenames that indicate purpose
+- Group similar objects together (jokers, consumables, etc.)
+
+### Balatro-Specific Patterns
+
+**Mod Integration Pattern**:
+* Use standard SMODS patterns
+* Refer to existing implementation in objects/ directories for working examples
+
+**Networking Actions**:
+```lua
+-- Follow the established action pattern
+MP.ACTIONS.example_action = function(data)
+	-- Validate input
+	if not data or not data.required_field then
+		return
+	end
+
+	-- Perform action
+	-- Update game state
+	-- Send response if needed
+end
+```
+
+**UI Components**:
+|  |  |
+|------|-------------|
+| [`ui/_common/`](ui/_common/) | Shared components. Config toggles, spacers, etc. |
+| [`ui/utils.lua`](ui/utils.lua) | Home of `MP.UI.UTILS`. Utils for creating UI nodes |
+| [`ui/game/`](ui/game/) | UI inside the pvp match |
+| [`ui/lobby/`](ui/lobby/) | Lobby UI |
+| [`ui/main_menu/`](ui/main_menu/) | Main menu UI |
+| [`ui/smods_menu/`](ui/smods_menu/) | SMODS settings menu entry |
+
+**Mod Injection**:
+- The entrypoint is in [`core.lua`](core.lua)
+- Files/dirs prefixed with `_` are loaded first in [`MP.load_mp_dir`](core.lua#L72)
+
+## Contribution Guidelines
+
+1. **Commits**: Write clear, descriptive commit messages
+2. **Testing**: Test your changes thoroughly across different scenarios
+
+## Testing Guidelines
+
+- Test in both single-player and multiplayer environments
+- Verify compatibility with supported Balatro / SMods / Lovely versions
+- Test with different rulesets and gamemodes
+- Include example seeds in PR description when relevant
+
+## Code Review Process
+
+All contributions go through code review. Reviewers will check for:
+
+- Code style compliance
+- Functionality correctness
+- Performance considerations
+- Compatibility with existing features
+- Security implications (networking code)
+
+## Questions?
+
+- Check existing [GitHub Issues](https://github.com/Balatro-Multiplayer/BalatroMultiplayer/issues)
+- Join the [Discord server](https://discord.gg/balatromp) for discussion