Node.js SDK for the public Smash.gg API, which is rich with data about tournament brackets that have occurred on their platform.
require('colors');
const smashgg = require('smashgg.js');
const {Event} = smashgg;
smashgg.initialize('<your api key>');
(async function(){
let tournamentSlug = 'function-1-recursion-regional';
let eventSlug = 'melee-singles';
let meleeAtFunction = await Event.get(tournamentSlug, eventSlug);
let sets = await meleeAtFunction.getSets();
let phaseGroups = await meleeAtFunction.getPhaseGroups();
console.log('Function 1 had %s sets played in %s phase groups',
sets.length, phaseGroups.length);
console.log('Set Results:')
for(var i in sets){
console.log(`${String(sets[i].getFullRoundText()).magenta}: ${String(sets[i].getDisplayScore()).green}`);
}
return true; // exit async
})()Results:
- Organization: RecursionGG
- Email: [email protected]
- Discord: cookiE#7679
npm install --save smashgg.js- Please submit any issues or feature requests to the Issues Section of the Github
To begin coding with the SDK, you need an Access Token. You may get one by Joining the Smash.gg discord and asking Furtive for an API key.
Once you have this key, you may use the following function to authenticate with the API and then you may move on
// import the SDK
const smashgg = require('smashgg.js');
// authenticate with key
smashgg.initialize('<your api key here>');Currently, smashgg.js is limited by Smash.gg's rate limiting rules. Those are currently
80 requests per 60 seconds. That is, every request made to the API starts a 60 second timer.
If 80 requests are made before the first 60 second timer is completed, your next request will
be dropped.
This SDK implements a Queueing system when your code becomes "Delinquent", that is it has made too many requests too fast. Your requests won't be dropped, but rather will wait until the next available request slot opens.
If you wish to see this queuing info, it is recommended you maintain the "info" logging level (See Logging).
The original API has no Sunset date set currently. While this is the case, I thought it best to make the original SDK available to people so that they may maintain their apps while beginning to move into V4. You may access v1-v3 SDK as follows:
let smashggV1 = require('smashgg.js/src/v1');You can access the built in Winston logger by using the following methods
const smashgg = require('smashgg.js');
let log = smashgg.Log;
log.info('Here\'s some text')
log.debug('Don\'t print this here')
smashgg.setLogLevel('debug')
log.info('Print everything now!!')
log.verbose('Not to be verbose...')
log.debug('but i\'m trying to debug :)')
smashgg.setLogLevel('warn');You can also add a Logger of your own, say if you'd like a File logger added
const smashgg = require('smashgg.js')
let log = smashgg.Log
smashgg.addLog('file', {
filename: '/tmp/log',
level: 'verbose',
format: winston.format.combin(
winston.format.splat(),
winston.format.simple()
)
})The following are the operations at your disposal
-
setLogLevel(level)
- level: string
- Valid values are
- error
- warn
- info
- verbose
- debug
- Valid values are
- level: string
-
addLog(type, options)
- type: string
- valid values:
- console
- file
- valid values:
- options: winston.LoggerOptions
- if you need this, please see this link
- type: string
-
disableLog()
- disabled the embedded logger
-
enableLog()
- enables the embedded logger
This section is for detailing the transition between major versions.
Easily the largest change that has occurred in the lifespan of this SDK. Please read carefully to successfully upgrade versions.
- All major objects (
Tournament,Event,Phase,PhaseGroup) have refactored the main getter renamed toget()Tournament.getTournament(slug)==>Tournament.get(slug)Event.getEvent(eventName, tournamentName)==>Event.get(tournamentName, eventName)Phase.getPhase(id)==>Phase.get(id)PhaseGroup.getPhaseGroup(id)==>PhaseGroup.get(id)
Eventno longer acceptsTournamentslug shorthand- shorthand like "function1" need to be refactored to their full slug version like "function-1-recursion-regional"
Tournamentno longer has aggregate functions likegetAllSets()orgetAllPlayers()- due to the limitations, the SDK can no longer support aggregate functions for Tournament objects,
I recommend using individual
Eventobjects to accomplish your goals
- due to the limitations, the SDK can no longer support aggregate functions for Tournament objects,
I recommend using individual
- Take caution in doing aggregate functions on
Eventsof very large size, like Evo Melee or something similar. You could find yourself hitting the rate limit very easily.
As described in Access V1-V3, you may use the original SDK while it has not been Sunset. See that section for more details.
In order to transition successfully from V2 to V3, please ensure the following
All Set objects created by smashgg.js are renamed to GGSet
In order to transition successfully from V1 to V2, please ensure the following
- Event constructors now take eventId parameter before tournamentId parameter.
- Additionally, you can give the constructor an Id number for the event, and null tournamentId.
Tournament,Event,Phase, andPhaseGroupconstructors now take anoptionsobject that encapsulates the previousisCachedandexpandsparameters.- Please see documentation for further implementation.
- It is suggested you move to the Promise returning convenience methods, as the previous
readyevent will be deprecated from this point on.- Please see documentation for the convenience methods. They take the same parameters as the constructor.
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent