You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
how about using the prop statistics as search criteria for maps in the map vault.
The FAF editor already calculates the prop statistics for a map..
..why don't we add the information to the scenario.lua when saving a map in the FAF editor or calculate it while uploading a map (no allowing manual editing).
That would enable us to sort maps via "props_total_mass" or "props_total_energy" in the vault.
Issues: Implementation via FAF editor or map upload?
Ozonex likes the idea and would add it to the FAF editor if needed. This way values could be changed manually. If we like to avoid that, we should calculate and write the values while uploading a map.
What to do with old maps?
Calculate value via script and add values to the db?! If we do like that, we could also use the script to recalculate the values if e.g. prop values were changed.
Advanced: Calculate total map reclaim (props + units)?
To get the total map reclaim we could calculate the reclaim value of units as well, but that would lead to problems with adaptive maps (amount depends on settings)
The client is not gonna parse this info evenr ->way to complex so either this gets saved as stats by api or whatever but then this issue is in the wrong repo
Hey guys,
how about using the prop statistics as search criteria for maps in the map vault.
The FAF editor already calculates the prop statistics for a map..
..why don't we add the information to the scenario.lua when saving a map in the FAF editor or calculate it while uploading a map (no allowing manual editing).
That would enable us to sort maps via "props_total_mass" or "props_total_energy" in the vault.
Issues:
Implementation via FAF editor or map upload?
Ozonex likes the idea and would add it to the FAF editor if needed. This way values could be changed manually. If we like to avoid that, we should calculate and write the values while uploading a map.
What to do with old maps?
Calculate value via script and add values to the db?! If we do like that, we could also use the script to recalculate the values if e.g. prop values were changed.
Advanced: Calculate total map reclaim (props + units)?
To get the total map reclaim we could calculate the reclaim value of units as well, but that would lead to problems with adaptive maps (amount depends on settings)
What do you think?
This issue is connected to FAForever/db#195 & FAForever/faf-java-api#320
The text was updated successfully, but these errors were encountered: