@idosgames/core 0.5.1 → 0.6.0

package/CHANGELOG.md

@@ -14,6 +14,82 @@ and this project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.ht
 
 ## [Unreleased]
 
+## [0.6.0] - 2026-08-09
+
+### Added
+
+- **`client.tutorial` (`TutorialService`)** — onboarding flows: `getTutorialDefinitions`,
+  `getUserTutorialState`, `startFlow`, `reportStepShown`, `completeStep`,
+  `completeStepsBatch`, `skipStep`, `skipFlow`, `claimFlowReward`, `resetFlow`. Definitions
+  are cached like the rest of the title config.
+- **Tutorial progress rides on every response.** A tutorial step is usually closed by an
+  ordinary game action (a purchase, a dice roll), not by a tutorial call — so the backend puts
+  an optional `TutorialProgress` block into the envelope of **any** response, the transport
+  lifts it out, and `UserData` merges it into the state. Subscribe to `tutorial:systemProgress`
+  instead of polling `getUserTutorialState`: the state is already fresh after any request, and
+  polling also skews the `ReportStepShown` funnel.
+- `SegmentGate.Tutorial` (`TutorialGateCondition` / `TutorialGateMode`) — gate any module's
+  definitions on the player's onboarding progress.
+- **`client.localization` (`LocalizationService`)** — `t(key, params)`, `has`, `locale`,
+  `fallbackLocale`, `locales`, `setLocale`, `getManifest`. Resolution is
+  **own table → fallback table → the key itself**, so a title whose config holds literal
+  display names ("Iron Sword") keeps working without migration: the literal is a key with no
+  translation. Plural forms come from `Intl.PluralRules` (suffixes `.one/.few/.many/.other`).
+- Translation tables arrive **with the player state** — no separate load. `UserService` sends
+  the locale and the versions of the tables it already has and resolves what comes back
+  through the same source chain as the title config (storage → CDN → endpoint → stale copy),
+  with one deliberate difference: a failure here does **not** fail the login. No config means
+  nothing to play; no translations means the UI shows keys.
+- `settings.locale` (`SettingsInput.locale`) — the starting locale, defaulting to the device
+  language. It is a **wish**, not a fact: the server folds it to what the title is actually
+  translated into (`pt-BR` → `pt` → `en`), and the answer is `client.localization.locale`.
+- `TitlePublicConfigurationModel.Localization` — locale settings only. The tables are
+  delivered separately, one file per locale.
+- `localization:changed` event (login, `setLocale`, new tables). `t()` is synchronous, so
+  already-rendered labels need this signal to repaint.
+- `PostOptions.throttleKey` — override the throttle / in-flight-dedup key when one route
+  serves genuinely different requests back to back. Added for the localization tables: own and
+  fallback both go through `Localization/GetLocalizationTable`, and under the default key
+  (the endpoint) the second call would be dropped as a duplicate — the fallback table would
+  never arrive, silently, and only for players whose language is partially translated. The
+  throttle window still applies, just per key.
+- **Batch claims** — `season.claimTierRewardsBatch(seasonChainID, tierNumbers)` and
+  `referral.claimInviteRewardsBatch(inviteRewardIDs)`. Season tiers in particular are reached
+  in batches: one token grant can raise a player through several at once. The merged
+  `Resources` is applied **once** from the top level; per-item `Data.Resources` is null by
+  contract so summing both cannot double count.
+- **Multi-open ceilings** — `collection.openPack(collectionID, packTypeID, count?)`,
+  `collection.openCollectionChest(collectionID, chestID, count?)` and
+  `coopEvent.spin(chainID, groupID, count?)` open/spin `count` times in one atomic operation
+  (`count` defaults to 1, so existing calls are unaffected). Each roll sees the state left by
+  the previous one, so a repeat drop is correctly counted as a duplicate. The count is clamped
+  server-side; responses report what actually happened (`OpenedCount` + per-item `Packs` /
+  `Chests`, `RequestedSpins` / `SpinsUsed` / `Sectors`). Only spins that happen are charged —
+  a run stops at the spin that completes the object.
+- Config for those ceilings: `LootboxDefinitions.Settings` (`LootboxGlobalSettings`) and
+  `LootboxDefinition.MaxOpenCount`, `CollectionDefinitions.Settings`
+  (`CollectionGlobalSettings`), `CollectionPackTypeDefinition.MaxOpenCount`,
+  `CollectionChestDefinition.MaxOpenCount`, `CoopBuildObjectsDefinition.MaxSpinsPerCall`.
+- `FriendActionResponse.Target` (the other side's public profile) and `.Counters`
+  (`SocialCounters`) — a new friend can be shown without a second `getFriendsList()`.
+- New events: `tutorial:definitionsLoaded` / `:userStateLoaded` / `:flowStarted` /
+  `:flowSkipped` / `:flowReset` / `:stepChanged` / `:stepsCompletedBatch` / `:rewardClaimed` /
+  `:systemProgress`, `localization:changed`, `season:tierRewardsBatchClaimed`,
+  `referral:inviteRewardsBatchClaimed`, `user:tutorialUpdated`.
+
+### Notes
+
+- Everything here is additive: the new `count` parameters default to `1`, the new response
+  fields are optional, and no existing signature changed.
+- `TutorialStepPolicy.TimeoutSeconds` is carried in the schema but **not applied** — neither
+  the backend (it has no "N seconds passed" moment) nor `core` (it renders no UI) can enforce
+  it. Whoever draws the tutorial implements it, and only for `ClientAck` steps; on a step
+  waiting for a game event the backend rejects `completeStep`.
+
+## [0.5.1] - 2026-08-05
+
+Version-only republish of 0.5.0 — no source changes.
+
 ## [0.5.0] - 2026-08-04
 
 ### Added