Configurable Daycare Price Rate

[AerunDev]

As a Pokémon Studio user configuring game economy
I want to define the price paid by the player per level gained by a Pokémon in the Daycare
So that I can balance the Daycare cost according to my project’s economy without manually editing PSDK scripts or common events

Today, this behavior requires manual changes in PSDK code and in the Daycare (management) common event from RPG Maker XP. Pokémon Studio should expose this value as a project setting, while PSDK reads and applies the configured parameter.

The goal is to make this configuration accessible and maintainable, without encouraging users to modify internal scripts directly.

Acceptance Criteria

• Pokémon Studio exposes a Daycare price rate setting as a numeric input.
• The setting defines the price paid per level gained before retrieving a Pokémon from the Daycare.
• The value is saved in the project configuration so that PSDK can read it through Configs.settings.daycare_price_rate.
• PSDK uses this configured value when calculating Daycare withdrawal cost.
• Existing projects keep the current/default behavior unless the setting is explicitly changed (100 P by default).
• The input includes basic validation:
  • Value must be numeric.
  • Value cannot be negative.
  • A reasonable upper bound may be defined to avoid invalid economy values or UI issues.
• The user should not need to manually edit:
  • scripts\4 Systems\201 Daycare\011 Daycare.rb in PSDK - Direct link to the code
  • the common event Daycare (management)
• If the project uses a legacy or customized Daycare implementation, Pokémon Studio should avoid assuming compatibility beyond the standard PSDK setup.

Identified and Relevant Use Cases

Relevant

• Adjusting Daycare cost to fit a custom game economy.
• Making Daycare cheaper or more expensive depending on project balance.
• Avoiding repeated manual script edits after updates.
• Keeping Daycare behavior configurable from Studio rather than hidden in code.

Not Prioritized / Out of Scope

• Per-species or per-Pokémon pricing.
• Dynamic pricing based on badges, region, trainer progress, or story state.
• Editing or generating custom Daycare common events from Studio.
• Supporting heavily modified Daycare systems in a first iteration. This part will need more reflexion to add a dedicated settings block on Pokémon Studio.

Product Perspective

This is a good candidate for a Pokémon Studio setting because it is:

• simple to expose,
• meaningful for balancing,
• currently hidden behind technical edits,
• and expected to be read directly by PSDK.

The preferred approach is a single global project setting first, rather than a complex pricing rule system.

[Green00101]

Hi, I'd like to work on this issue.

I opened another PR yesterday, so I would like to ask: Is it okay if I open more than one PR at the same time, or should I wait until my previous PR is merged? Thanks!

[Aelysya]

Hello, yes it's absolutely okay, no problem with that. And of course you can work on this issue if you'd like.