top | item 47035633

(no title)

Jeremy1026 | 14 days ago

Another example is the tower stat caps. When Claude Code generate the first pass, it make it so that the tower level would control each individual stat's cap. Which was way too high. I didn't know exactly what the limits were, but knew they needed to be pulled back some. So I asked it:

-Start Prompt-

Currently, a towers level sets the maximum a single stat can be. Can you tell me what those stat caps are?

-End Prompt-

This primed the context to have information about the stat caps and how they are tied to levels. I followed up after it gave me a chart back with Tower Level and Max Stat Rank with some real stats from play

-Start Prompt-

Lets change the stat cap, the caps are currently far too high. All towers start at 1 for each IMPACT stat, my oldest tower is Level 5, and its stats are I-3, M-4, P-6, A-3, C-1, T-1. How do you think I could go about reducing the cap in a meaningful way.

-End Prompt-

It came back with a solution to reduce the individual stat cap for individual stats to be tower level + 1. But I felt that was too limiting. I want players to be able to specialize a tower so I told it have the stat cap be total, not per stat.

-Start Prompt-

I'm thinking about having a total stat cap, so in this towers case, the total stats are 18.

-End Prompt-

It generated a couple of structures of how the cap could increase and presented them to me.

-Start Prompt-

Yes, it would replace the per-stat cap entirely. If a player wants to specialize a tower in one stat using the entire cap that is fine.

Lets do 10 + (rank * 3), that will give the user a little bit of room to train a new tower.

Since it's a total stat cap, if a user is training and the tower earns enough stat xp to level beyond the cap, lock the tower at max XP for that stat, and autoamtically level the stat when the user levels up the tower.

-End Prompt-

It added the cap, but introduced a couple of build errors, so I sent it just the build errors.

-Start Prompt-

/Users/myuser/Development/Shelter Defense/Shelter Defense/Views/DebugTowerDetailView.swift:231:39 Left side of mutating operator isn't mutable: 'tower' is a 'let' constant

/Users/myuser/Development/Shelter Defense/Shelter Defense/Views/DebugTowerEditorView.swift:181:47 Left side of mutating operator isn't mutable: 'towerInstance' is a 'let' constant

-End Prompt-

And thus, a new stat cap system was implemented.

discuss

order

No comments yet.