Results 9 issues of Phil25

- [ ] Allows to specify time until death - [ ] Allows to specify unlimited, death-persistent time. - [ ] Allows to specify custom settings - [ ] Allows...

request :: general

Nosoop's [SM-CustomStatusHUD](https://github.com/nosoop/SM-CustomStatusHUD) is great for syncing up HUD updates when multiple plugins are calling them. It's weird that nobody had requested RTD support for it. ### Tasks - [ ]...

Current way of checking perk preconditions is by specifying which classes or weapons it's available for through the config. This greatly limits perk variety because it's impossible to determine whether...

request :: general
request :: api

There are two configs considered for perk configuration: `rtd2_perks.default.cfg` and `rtd2_perks.custom.cfg`. Since perks cannot be configured per map (only disabled), this mechanism could be extended to allow just that. Example:...

request :: general

Whole new feature which allows good perks to be dropped on the ground and shared with other players. ## Summary * Only good and timed perks are droppable. * Perks...

request :: general

Perk config is very versatile, but it can be even more so. ## Example There could be an unused-by-default `call` function which is able to execture commands provided via perk's...

request :: api

Add a field to perk config indicating how costly every perk can be on the entity count. ## Suggestion 1 Perks will have a new field called `entity_cost` which tells...

request :: general

# Overview Perks define the `call` method and now the `init` method which correspond to the function names in code. With the upcoming programmatic preconditions ([#71](https://github.com/Phil25/RTD/issues/71)), there will be a...

request :: general

It's not gonna be supported soon and you shouldn't have done it in the first place. What were you thinking?

bug