Reference of v4 user history

arguments	description	optional
user	user name or 9-digit user code	YES, while passing usercode
usercode	9-digit user code	YES, while passing user
quantity	the number of records expected	YES
songname	any song name for fuzzy search	NO
difficulty	accept format are 0/1/2/3 or pst/prs/ftr/byn or past/present/future/beyond	NO

Explain

Search user's history records of a given song id.
You could configure the limitations of history in BOTARCAPI_USERBEST_HISTORY_DEFAULT and BOTARCAPI_USERBEST_HISTORY_MAX

Return data

• The records in history come from the local database.
  While someone triggered the search, it will be updated automatically. It's NOT an arcapi hack.

{
    "status": 0,
    "content": {
        "history": [
            {
                "score": 233,
                "health": 100,
                "rating": 233,
                "song_id": "grievouslady",
                "modifier": 0,
                "difficulty": 2,
                "clear_type": 1,
                "best_clear_type": 5,
                "time_played": 233,
                "near_count": 23,
                "miss_count": 23,
                "perfect_count": 23,
                "shiny_perfect_count": 23
            },
        // more data...
        ]
    }
}

Error status

status	description
0	everything is OK
-1	invalid username or usercode
-2	invalid usercode
-3	invalid songname
-4	invalid history quantity
-5	invalid difficulty
-6	invalid difficulty (map format failed)
-7	this song is not recorded in the database
-8	too many records
-9	internal error
-10	this song has no beyond level
-11	internal error occurred
-12	user not found
-13	too many users
-14	internal error occurred
-15	clear friend list failed
-16	allocate an arc account failed
-17	add friend failed
-18	internal error occurred
-19	internal error
-233	unknown error occurred