<for

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • mikebolt
    FFR Player
    • Nov 2007
    • 94

    #1

    <for

    Ive concluded that whenever I play a song and gain at least two tier points on it "<for" appears in the your best rank section of the score display. I think it's an xml leak or something. It only shows 7 digits so it's like 694<for . I have a screenshot of this on my profile, and i got like 3 more i could upload if anyone cares. But this never happens on just any song, or even on songs i only get one more tier point on. Odd.
  • qqwref
    stepmania archaeologist
    FFR Simfile Author
    • Aug 2005
    • 4092

    #2
    Re: &lt;for

    This has happened to me a few times, but it was never on public songs so I didn't bother to report it. In fact, there seem to be some songs that this always happens for, whether I improve my score or not.

    PS: It starts <font co
    Best AAA: Policy In The Sky [Oni] (81)
    Best SDG: PANTS (86)
    Best FC: Future Invasion (93)

    Comment

    • TC_goelo
      FFR Veteran
      • Jul 2009
      • 378

      #3
      Re: &lt;for

      it's been happening to me all day O:
      Originally posted by fido123
      Do you think a computer is a gnome in a metal box with a marker, paper, and mad fast art skills?


      Comment

      • Flks
        FFR Player
        • Dec 2007
        • 48

        #4
        Re: &lt;for

        I noticed that too, but actually it's not <for but <fon. I got this on smartsniff:

        &currentranking=253&totalcredits=0&ranking=131<font color=ff0000><br />
        <b>Warning</b>: mysql_num_rows(): supplied argument is not a valid MySQL result resource in <b>/home/virtual/site1/fst/var/www/html/t-ffrstatsup.php</b> on line <b>686</b><br />
        </font>

        So, it's a database problem.

        Comment

        • Sprite-
          HAVE ME WITH VODKA
          FFR Simfile Author
          • Aug 2005
          • 7316

          #5
          Re: &lt;for

          No, it was a php problem. It's fixed now.

          Comment

          Working...