Struct CollectionPowerSettings

pub struct CollectionPowerSettings {
    pub first_ownership_share: f64,
    pub multiplied_attribute_ids: Vec<AttributeId>,
    pub equipment_stones: CollectionPowerFamily,
    pub laws: CollectionPowerFamily,
    pub artifact_stones: CollectionPowerFamily,
    pub ability_stones: CollectionPowerFamily,
    pub gacha_abilities: CollectionPowerFamily,
    pub pets: CollectionPowerFamily,
    pub stone_tier_weights: Vec<StoneTierCollectionWeight>,
    pub pet_rarity_weights: Vec<PetRarityCollectionWeight>,
}

Collection Power: a small permanent stat bonus for OWNING catalog content, paid whether or not the template is equipped.

Loadout keeps its job — active effects, synergies and the difference between builds. This pays only for breadth and rank, in three flat percentages on Attack / HP / Armor, so a stone or law that no longer fits the build is still worth having.

Deliberately NOT here: artifacts, which already pay an ownership bonus of their own (ArtifactTemplate::ownership_bonuses) and would be counted twice; pet facets, whose value arrives through the pet that carries them; cores, bridges and sockets, which are progression rather than collectible templates; and equipment items, which are constantly replaced and sold.

Fields

first_ownership_share: f64

The share of a template’s contribution that the FIRST copy pays, with the rest spread linearly across its rank ladder. Breadth is worth something immediately; depth is worth most of it.

multiplied_attribute_ids: Vec<AttributeId>

The attributes M_collection multiplies. Read by CODE through <code>.mod, the same channel artifact ownership uses, so the bonus reaches combat, the displayed power scalar and PvP matchmaking at once.

equipment_stones: CollectionPowerFamily

laws: CollectionPowerFamily

artifact_stones: CollectionPowerFamily

ability_stones: CollectionPowerFamily

gacha_abilities: CollectionPowerFamily

pets: CollectionPowerFamily

stone_tier_weights: Vec<StoneTierCollectionWeight>

pet_rarity_weights: Vec<PetRarityCollectionWeight>

Implementations

impl CollectionPowerSettings

pub fn stone_tier_weight(&self, tier: StoneTier) -> f64

Collection weight of an equipment-stone tier. An unweighted tier pays nothing — GameConfig::validate_collection_power requires a row per tier, so this is a safety net rather than a reachable state.

pub fn pet_rarity_weight(&self, rarity_id: PetRarityId) -> f64

Collection weight of a pet rarity. Same rule as Self::stone_tier_weight: an unweighted rarity pays nothing.

pub fn progress(&self, level: i64, max_level: i64) -> f64

Progress of one owned template, in 0..=1.

level is the template’s current rank and max_level the top of its family’s ladder. A one-rung ladder pays the full contribution on the first copy — there is no rank left to earn the rest.

Trait Implementations

impl Clone for CollectionPowerSettings

fn clone(&self) -> CollectionPowerSettings

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for CollectionPowerSettings

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for CollectionPowerSettings

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl JsonSchema for CollectionPowerSettings

fn schema_name() -> String

The name of the generated JSON Schema.

fn schema_id() -> Cow<'static, str>

Returns a string that uniquely identifies the schema produced by this type.

fn json_schema(generator: &mut SchemaGenerator) -> Schema

Generates a JSON Schema for this type.

fn is_referenceable() -> bool

Whether JSON Schemas generated for this type should be re-used where possible using the $ref keyword.

impl Serialize for CollectionPowerSettings

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl Tsify for CollectionPowerSettings

const DECL: &'static str = "/**\n * Collection Power: a small permanent stat bonus for OWNING catalog content,\n * paid whether or not the template is equipped.\n *\n * Loadout keeps its job \u{2014} active effects, synergies and the difference between\n * builds. This pays only for breadth and rank, in three flat percentages on\n * Attack / HP / Armor, so a stone or law that no longer fits the build is\n * still worth having.\n *\n * Deliberately NOT here: artifacts, which already pay an ownership bonus of\n * their own (`ArtifactTemplate::ownership_bonuses`) and would be counted twice;\n * pet facets, whose value arrives through the pet that carries them; cores,\n * bridges and sockets, which are progression rather than collectible\n * templates; and equipment items, which are constantly replaced and sold.\n */\nexport interface CollectionPowerSettings {\n /**\n * The share of a template\\\'s contribution that the FIRST copy pays, with\n * the rest spread linearly across its rank ladder. Breadth is worth\n * something immediately; depth is worth most of it.\n */\n first_ownership_share: number;\n /**\n * The attributes `M_collection` multiplies. Read by CODE through\n * `<code>.mod`, the same channel artifact ownership uses, so the bonus\n * reaches combat, the displayed power scalar and PvP matchmaking at once.\n */\n multiplied_attribute_ids: AttributeId[];\n equipment_stones: CollectionPowerFamily;\n laws: CollectionPowerFamily;\n artifact_stones: CollectionPowerFamily;\n ability_stones: CollectionPowerFamily;\n gacha_abilities: CollectionPowerFamily;\n pets: CollectionPowerFamily;\n stone_tier_weights: StoneTierCollectionWeight[];\n pet_rarity_weights: PetRarityCollectionWeight[];\n}"

const SERIALIZATION_CONFIG: SerializationConfig

type JsType = JsType

fn into_js(&self) -> Result<Self::JsType, Error>

where Self: Serialize,

fn from_js<T>(js: T) -> Result<Self, Error>

where T: Into<JsValue>, Self: DeserializeOwned,