So it is a somewhat long-term goal at the moment.
#Siralim ultimate for free
This would mean I could no longer host it for free on GitHub pages, and would need to think about security, maintenance etc. The only way to achieve this would be to have a back end app, such as a Flask app, that could encode a build into a short URL (like how Grimtools does it). Such as artifact stats, nether stone traits, etc, but this is simply not possible without causing the build string to grow to ridiculous lengths. I would like to add other things to the app TODOĪt this stage I've pretty much reached the limit of what I can do with a pure front-end app. The relic codes are two characters, corresponding to the 6th and 13th character of the relic's name, after removing any non-alphabetical characters (because those two particular characters did not have any collisions). I don't think the order of the perks within a specialization will ever change but if they do, it will only be a minor
#Siralim ultimate code
the first perk in Bloodmage, "Bleed Out", has the anointment code BMA, the second perk "Blood Clot" has BMB, and so on. That the perk belongs to, and the third letter is a letter representing the index of the perk within the list of that specialization's The first two characters is the specialization code The anointment codes are three-character representation of a particular perk.
For a list of them, see data/steam-guide/specializations.csv. The specialization code string is much simpler - it is a two-character identifier for a specialization. The name of its trait changes at some point. Iron Golem just happens to be ef5667 and will always be ef5667 unless its family, creature or String that represents each monster, e.g. I chose a hash length of 6 (in order to minimise potential collisions). This should be more robust as the family, creature and traits don't So instead I decided to take the hash of the family + creature + trait. Then any builds loaded from previous versions of the Compendium would break. If a creature was added before creature 123, for example, But this would cause problems later down the line when new creatures are added.
0 kommentar(er)
