studio/idle-survivors
2
0
Fork 0
Code Issues 14 Pull Requests 1 Packages Projects Releases Wiki Activity

Implement Attribute System #2

New Issue
Open
opened 2023-07-12 22:19:54 -04:00 by madxmike · 4 comments
madxmike commented 2023-07-12 22:19:54 -04:00
Owner
Copy Link

This is super rough just to get ideas on the page. Will be much clearer with a proof of concept.

As with all roguelike rpgs, we need some way to describe an Attribute Set (hp, str, dex, etc) along with ways to provide temporary or permenant changes to these attributes. To do this we need to create an Attribute system that has the following core ideas:

Attribute

  • Effectively a float but wrapped to provide some convience functions, bounds checking and because non-primative types are useful here
  • Really would be 2 floats, the base value and the current value.
    AttributeSet
  • Defines a collection of Attributes that exist as one set
  • Responsible for initializing and providing control of attributes

Effect

  • A class defining a bit of logic for modifying attributes
  • Can be duration based, infinite, or instant
  • Can be addative or multiplicative
  • Can basically do whatever to any attribute on the character its on

AttributeSystem
- Stored on a character or other object with attributes
- Can contain many AttributeSets
- Entry point for applying Effects
- Manages lifecycle of applied Effects

Lets say we pickup an item that gives our units 20% more health for 10 seconds. We would grab all the units, apply an Effect to their AttributeSystem. The attribute system will then start managing the lifecycle of the Effect. Each tick, the AttributeSystem will go through all its active Effects, reprocess them and update the current value of the attributes, remove effects no longer valid.

This is super rough just to get ideas on the page. Will be much clearer with a proof of concept. As with all roguelike rpgs, we need some way to describe an Attribute Set (hp, str, dex, etc) along with ways to provide temporary or permenant changes to these attributes. To do this we need to create an Attribute system that has the following core ideas: Attribute - Effectively a float but wrapped to provide some convience functions, bounds checking and because non-primative types are useful here - Really would be 2 floats, the base value and the current value. AttributeSet - Defines a collection of Attributes that exist as one set - Responsible for initializing and providing control of attributes Effect - A class defining a bit of logic for modifying attributes - Can be duration based, infinite, or instant - Can be addative or multiplicative - Can basically do whatever to any attribute on the character its on AttributeSystem - Stored on a character or other object with attributes - Can contain many AttributeSets - Entry point for applying Effects - Manages lifecycle of applied Effects Lets say we pickup an item that gives our units 20% more health for 10 seconds. We would grab all the units, apply an Effect to their AttributeSystem. The attribute system will then start managing the lifecycle of the Effect. Each tick, the AttributeSystem will go through all its active Effects, reprocess them and update the current value of the attributes, remove effects no longer valid.
zephyr added a new dependency 2023-07-12 22:43:45 -04:00
#3 Implement Friendly Units (aka "Lil duders")
zephyr added this to the Prototype milestone 2023-07-12 22:45:08 -04:00
zephyr commented 2023-07-13 00:02:47 -04:00
Owner
Copy Link

Just a note: "a float" won't really be able to capture the idle game spirit. I think we'll want some variety of arbitrary precision number. Doubles may suffice, depending on final balancing, but I'm hesitant to include the possibility of infinities.

Just a note: "a float" won't really be able to capture the idle game spirit. I think we'll want some variety of arbitrary precision number. Doubles may suffice, depending on final balancing, but I'm hesitant to include the possibility of infinities.
zephyr commented 2023-07-22 21:42:46 -04:00
Owner
Copy Link

Since duders and enemies have different stats, is the idea to make AttributeSet an interface with a public Attribute Get(someAttrEnum)?

Since duders and enemies have different stats, is the idea to make AttributeSet an interface with a `public Attribute Get(someAttrEnum)`?
zephyr self-assigned this 2023-07-22 23:03:42 -04:00
zephyr referenced this issue from a commit 2023-07-23 15:18:34 -04:00
add Attribute definition
zephyr referenced this issue from a commit 2023-07-23 15:38:00 -04:00
add Attribute definition
zephyr referenced this issue from a commit 2023-07-30 11:58:20 -04:00
feature-attributes (#7)
zephyr commented 2023-07-30 12:01:45 -04:00
Owner
Copy Link

Attribute and Effect are implemented, at least to an extent. AttributeSet and AttributeSystem are not. I feel like we can hold off on those for a while and go ahead with #3.

Attribute and Effect are implemented, at least to an extent. AttributeSet and AttributeSystem are not. I feel like we can hold off on those for a while and go ahead with #3.
zephyr removed a dependency 2023-07-30 12:01:50 -04:00
#3 Implement Friendly Units (aka "Lil duders")
madxmike commented 2023-07-30 12:03:41 -04:00
Author
Owner
Copy Link

Attribute and Effect are implemented, at least to an extent. AttributeSet and AttributeSystem are not. I feel like we can hold off on those for a while and go ahead with #3.

Sounds good to me.

> Attribute and Effect are implemented, at least to an extent. AttributeSet and AttributeSystem are not. I feel like we can hold off on those for a while and go ahead with #3. Sounds good to me.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Prototype
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
zephyr
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: studio/idle-survivors#2
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?