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
This may include records with conditions such as the following:
Insufficient proof
Used a disallowed emulator
Used savestates before the run, but in a way that doesn't adhere to the ladder rules (e.g. in Climax)
And, potentially, even the following:
Used turbo inputs
Used savestates and slowdown during the run (TAS)
These are records which people may want to view on the FZC website in some way. In many cases, giving these records a home can also lead to new ladders/rulesets later. For example: allowing a emulator that was previously disallowed, adding a ladder for using pre-run savestates more liberally, allowing turbo with certain conditions, or even adding a TAS ladder.
(I would personally draw the line at using cheat codes/hacks - it ought to still be the same game at least.)
To support this, perhaps in addition to viewing charts/player pages/etc. through a particular ladder, there can also be an "archive view" of some sort which includes records like the above (marked appropriately, of course).
Supporting these kinds of records may involve adding several more filter groups for each game - in which case, it remains to be seen how much that would slow down operation of the regular ladders. If the slowdown's noticeable, then we might want to think of a solution which effectively separates out these 'less common' filter groups versus the 'more common' ones, so that the common ones operate as smoothly as possible. (This is more of an API problem, but worth mentioning here.)
The text was updated successfully, but these errors were encountered:
This may include records with conditions such as the following:
And, potentially, even the following:
These are records which people may want to view on the FZC website in some way. In many cases, giving these records a home can also lead to new ladders/rulesets later. For example: allowing a emulator that was previously disallowed, adding a ladder for using pre-run savestates more liberally, allowing turbo with certain conditions, or even adding a TAS ladder.
(I would personally draw the line at using cheat codes/hacks - it ought to still be the same game at least.)
To support this, perhaps in addition to viewing charts/player pages/etc. through a particular ladder, there can also be an "archive view" of some sort which includes records like the above (marked appropriately, of course).
Supporting these kinds of records may involve adding several more filter groups for each game - in which case, it remains to be seen how much that would slow down operation of the regular ladders. If the slowdown's noticeable, then we might want to think of a solution which effectively separates out these 'less common' filter groups versus the 'more common' ones, so that the common ones operate as smoothly as possible. (This is more of an API problem, but worth mentioning here.)
The text was updated successfully, but these errors were encountered: