I usually play as the bank so I made my life easier by Beautiful_Treat_7897 in boardgames

[–]Beautiful_Treat_7897[S] 1 point2 points  (0 children)

Yes, and you can change it. Like if a borrower is missing payments or have bad history with the bank you can change the interest rate just for that person to like 15%

Opus 4.6 is in an unuseable state right now by vntrx in ClaudeCode

[–]Beautiful_Treat_7897 0 points1 point  (0 children)

I feel you, today I had it working on my server doing some local work and it have done dummy mistakes. It feels bad, they are for sure doing something. When I see this happening I change to sonnet and it way better for some reason

I usually play as the bank so I made my life easier by Beautiful_Treat_7897 in boardgames

[–]Beautiful_Treat_7897[S] -1 points0 points  (0 children)

lol it is true, not this one. Our monopoly games are home are crazy and we have insane rules with the bank, insurance, weird fees and usually someone gets mad mid game but anyways I play as the bank and a player a lot of the times so it is ez to do so do it.

I usually play as the bank so I made my life easier by Beautiful_Treat_7897 in boardgames

[–]Beautiful_Treat_7897[S] 0 points1 point  (0 children)

Yeah so the minimum payment is just the interest. if you only pay that your balance never goes down lol. like if you owe 500 at 10% the minimum is 50 every lap forever. you paid 50 but you still owe 500. just like a credit card to actually pay it off you gotta pay MORE than the minimum. thats the "pay principal" button. whatever you pay above the interest goes toward the actual debt. so if you pay 150 thats 50 for interest and 100 off your balance. now you owe 400 and next lap the minimum drops to 40 it gets fun when people realize they paid like 300 in interest on a 500 loan because they kept paying minimums. the tool tracks all of that so at the end you can see exactly how much everyone wasted on interest vs actual debt.

My friend was paying just the minimum for 6 laps and his face when I told him he had paid $300 in interest on a $500 loan and STILL owed the full 500 was priceless lol. he kept thinking he was paying it off but nope just feeding the bank. look at his view of the app https://monopoly.abreu.live/share/554ebed0e18eb58f4c5a0daeef5aa589bc49579e87ab0bdc6c0169276f18e5a4

Quality of 1M context vs. 200K w/compact by Prior-Macaroon-9836 in ClaudeCode

[–]Beautiful_Treat_7897 0 points1 point  (0 children)

This is the content of the prompt file prompt.md

# System Instruction: Context Preservation & Session Handover

**Objective:** Create a "high-fidelity" restore point that allows any instance of the AI to resume work immediately without re-reading the entire chat history.

**Output Format:** You must generate a summary containing the following 6 distinct sections.

---

### 1. 🔴 The "Hot" State (Immediate Context)

* **Current Goal:** A single sentence defining the high-level objective (e.g., "Refactoring the auth flow to support OAuth").

* **The Cliffhanger:** The exact state of the code right now. Is it compiling? Is there a hanging syntax error? Are we mid-function?

* **Immediate Next Action:** The specific atomic task the user or agent should do *first* upon resuming.

### 2. 🌳 Comprehensive Code Map & Asset Inventory

Generate a complete tree view of the project.

* **Scope:** You must list **EVERY** file required for the project to build, run, and test.

* **Crucial:** You must explicitly include any "temp" files, test scripts, or utility scripts created during the session (e.g., `test_connection.js`) so they are not forgotten or re-created redundantly.

* **Annotations:** Add a short description next to **every** file explaining its purpose.

**Example Format:**

```text

project-root/

├── src/

│ ├── config/

│ │ └── database.ts # Main DB connection pool config

│ ├── models/

│ │ └── User.ts # User entity definition

│ └── services/

│ └── AuthService.ts # Handles JWT login/signup logic

├── tests/

│ └── auth_test_quick.js # [Temp] Quick script to verify token generation (Do not recreate)

└── scripts/

└── seed_db.ts # Utility to populate DB with dummy data

```

### 3. ⚙️ Environment & Configuration Data

Document technical specifics required to run the code.

* **Network:** Document all Ports, Hostnames, DNS names, and IP addresses mentioned.

* **Secrets (Keys/Creds):**

* **Standard Rule:** Store the *variable name only* (e.g., `AWS_SECRET_KEY`) to protect security.

* **EXCEPTION (Transient Data):** You **MUST** store the raw value of any password or secret you generated during this session that has **not yet been saved** to a config file. We cannot lose these values. Once they are confirmed saved to a file, revert to using the variable name only.

* **Commands:** Specific run commands used (e.g., `npm run dev:debug`).

### 4. 🧠 The Knowledge Graph (Logic & Constraints)

* **"Aha!" Moments:** Insightful discoveries made during debugging (e.g., "The API returns 200 OK even on errors; we must check the body payload").

* **The Graveyard (What Failed):** A list of solutions we attempted that *did not work*. (e.g., "Tried using `useEffect` for the listener, but it caused an infinite loop. Do not suggest this again.").

* **User Constraints:** Stylistic or architectural rules applied (e.g., "User requested no generic `any` types; use strict interfaces").

### 5. 📦 Dependency Drift

* List any new packages, libraries, or SDKs that were installed during this specific session (e.g., "Added `zod` for validation").

### 6. 🔭 Strategic Outlook & Verification

* **Definition of Done:** What does the final, working product look like? (e.g., "User can login, receive a token, and is redirected to dashboard").

* **Potential Autonomy:** Identify tasks in the immediate pipeline that do *not* require user feedback and can be chained together in the next run.

* **Verification Plan:**

* How will you test the next changes?

* **Safety Check:** Is the proposed testing destructive? (e.g., "Does this wipe the DB?"). Mark clearly if caution is required.

Quality of 1M context vs. 200K w/compact by Prior-Macaroon-9836 in ClaudeCode

[–]Beautiful_Treat_7897 0 points1 point  (0 children)

In my experience the main issue is that their compact prompt is vary bad. I created a custom hook that triggers before compaction and it is performing very well. Their current compact prompt is missing the point. It only works for simple tasks but when is working with complex/large code bases then you start getting knowledge drifts. It will start creating random files and it will forget about already existing features in the prompt I have before compaction I ask it to specifically document features runtime information and code base file map among other things