Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Suggestion] Dediated pile sheet #692

Open
PalaNolho opened this issue Jan 12, 2025 · 0 comments
Open

[Suggestion] Dediated pile sheet #692

PalaNolho opened this issue Jan 12, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@PalaNolho
Copy link

From what I understand from this module, the you can convert any Actor into a pile, and then you choose the type of pile you wnat it to be (merchant, loot chest, etc...).

I feel this may be a bit confusing at the moment. I'm pretty sure people would be asking themselves, "which actor should I use?", "is there a benefit or piling a Group actor?", "what happens if I pile a player character?", etc....

My feeling is that it would make things a lot cleaner and easier to understand if there were dedicated actors(or items, or whatever you think is more appopriate) for each option.

  • maybe merchants should be a type of Actor, while item, container and vault should be a type of Item

So basically, when you create a new actor (for example), you would have new options for:

  • Pile - Merchant
  • Pile - Item
  • Pile - Container
  • Pile - Vault

I was looking at the Pile settings on the different entities andthey also seem to be diferent. I myself donr (yet) understand the differences what I should be doing with the different settings on the different types of entities.

The ultimate goal would be to make things simpler to manage and understand.

hope it helps
cheers!

@PalaNolho PalaNolho added the enhancement New feature or request label Jan 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant