rakuja / bybe Goto Github PK

Many users requested to generate creature based on a locale and, if possible, have some kind of relationships between creatures (ex vampire and vampire spawn). The latter one is not a necessity, as "family" and "traits" could already be enough

To allow implementation of TheAsel/BYBE-frontend#4 we should return the list of sources

Rules with xp budget: https://2e.aonprd.com/Rules.aspx?ID=668
List of hazars: https://2e.aonprd.com/Hazards.aspx

For PF2e specifically, I'd love for an encounter builder to provide the opportunity to mix in hazards

Implement Proficiency without Level, a new table used to compare level difference and exp received

https://2e.aonprd.com/Rules.aspx?ID=1370

Right now, traits and creature_types filter allow for a vector of values.
We should mirror that behavior on all the filters

To implement TheAsel/BYBE-frontend#9 we need to allow the frontend to filter by min number of creatures and max number of creatures

Redis was used for four main reasons:

1. Ease of use in python
2. Original bestiary was only a key: value store, it did not require filtering at first
3. Fly instance allows only 220mb of RAM for the basic tier, python would eat up 180-200mb, leaving no ram space for any db. Now that we (we=Rust) optimized the structure and use only 80mb, we have space for a sqlite db.
4. Possibility of different shards in different locations, reconciliation, etc..

This will improve latency (local db), remove ugly sanitation code when converting from json array to array of strings.

This is a SQL injection waiting to happen, right now there is no risk thanks to the type system and controlled flow, but in the future it may become a problem

When randomly generating an encounter, if the generated enemy is level 2 we could fetch an enemy of level 2 or instead an elite level 1 enemy or weak level 3 enemy. This would increase exponentially the permutations and avoid a lot of empty results

Right now, the "fey" "undead" etc filters cannot be applied because there is missing information about the traits. Implement traits, both in the encounter generator as filter and as the field of a creaturer

The encounter info struct should be clearer on xp award/xp budget
https://2e.aonprd.com/Rules.aspx?ID=575

When applying a filter with min = 1, max = 1
and a party of 5 adventurers with level 4, the encounter builder fails to generate a valid encounter.
This is a strange behaviour, because with a party of 4 and level 4, it generates correctly.

Adding a creature's role (brute, magical striker, etc.) could be useful. The classification would have to be made by hand or somehow inferred by the creature's stats/DCs. More info at the link below, in the "Base Road Maps" section.

https://2e.aonprd.com/Rules.aspx?ID=995

The encounter builder should offer more filters options: Type of fighter (melee/ranged) (caster/not caster)

Add the Cache-Control HTTP header

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control