Difference between pages "Card Tips:Ultimate Flame Swordsman" and "Yugipedia:API"

From Yugipedia
(Difference between pages)
Jump to: navigation, search
(Testing the new combo steps template to see how it looks on Card Tips articles)
 
(link the meta UA policy page too)
 
Line 1: Line 1:
{{Navigation}}
+
Yugipedia uses [[wikipedia:MediaWiki|MediaWiki]], which offers a powerful API for automated access to our data. This API can be accessed via https://yugipedia.com/api.php, and extensive documentation can be found on [[mw:Special:MyLanguage/API:Main page|MediaWiki.org]]. When using our API, please observe some points of etiquette, to avoid endangering the site; offending agents may be blocked without warning.
  
* One simple method to [[Fusion Summon]] this card requires only "[[Fighting Flame Swordsman]]". It also enables this card's effect to be used as a Quick Effect, while also increasing its ATK by 700.
+
== User agent ==
{{Combo steps
+
All automated requests to the API should set a descriptive User-Agent header, including the name of the service and contact information. Requesters who do not do so may be blocked at any time without warning. For more information, see the [[m:User-Agent policy|User-Agent policy]] on Wikimedia Meta.
| opening = "[[Fighting Flame Swordsman]]"
 
| end    = "[[Ultimate Flame Swordsman]]" equipped with "[[Salamandra, the Flying Flame Dragon]]" + "[[Flame Swordsrealm]]"
 
| steps  =  
 
# Summon "[[Fighting Flame Swordsman]]".
 
# Activate "Fighting Flame Swordsman" to search "[[Flame Swordsrealm]]".
 
# Activate "Swordsrealm" to send "Fighting Flame Swordsman" from the field to the GY to [[Special Summon]] "[[Flame Swordsman]]" from the Extra Deck.
 
# Activate "Fighting Flame Swordsman" to send "[[Salamandra, the Flying Flame Dragon]]" from the Deck to the GY.
 
# Activate "Salamandra, the Flying Flame Dragon" to search "[[Salamandra Fusion]]".
 
# Activate "Salamandra Fusion" by equipping it to "Flame Swordsman".
 
# Activate "Salamandra Fusion" by sending itself and and the equipped monster to Special Summon "[[Ultimate Flame Swordsman]]" from the Extra Deck, treating it as a Fusion Summon.
 
# Activate "Salamandra, the Flying Flame Dragon" to equip itself from the GY to "Ultimate Flame Swordsman".
 
}}
 
  
* "[[Fighting Flame Dragon]]" can equip itself to this card, allowing it to attack twice. With this card's ATK-doubling effect, it can potentially deal 14000 damage in a single turn.
+
== Request limit ==
 +
Please limit requests to no more than one per second. The content of multiple pages can be bundled together into a single request with a pipe (<code>|</code>), e.g. <code>titles=PageA|PageB|PageC</code>.
 +
 
 +
== Caching ==
 +
Results of requests should be cached wherever possible, and the cache should be used instead of repeatedly requesting the same resources. A good period for caching is 30 days.
 +
 
 +
== Updating data ==
 +
Certain tasks done via the API, such as automatically building and maintaining a card database, may require information to be updated more often than every 30 days. In these cases, instead of simply rerequesting the entire data set, you should only rerequest those resources that have changed. This can be determined by watching our [[Special:RecentChanges|recent changes feed]] using <code>[[mw:Special:MyLanguage/API:Recentchanges|list=recentchanges]]</code>.
 +
 
 +
== Other points ==
 +
In addition to these, you should assume that the points on the [[mw:Special:MyLanguage/API:Etiquette|API etiquette]] page on MediaWiki.org also apply to use of the Yugipedia API; that page also has some advice on how to reduce the potential impact of requests. If you have questions, need help, or want to provide feedback, you can join our [[Yugipedia:Discord|Discord server]].
 +
 
 +
== What do I do if I've been blocked? ==
 +
If you've been blocked because of misuse of our API, the first step is to join our [[Yugipedia:Discord|Discord server]] and explain what you were doing with the API. It is very likely that your requests can be changed to meet our usage guidelines here, and we'd be happy to work with anyone who needs help on the matter.
 +
 
 +
[[Category:Policy]]

Latest revision as of 02:35, 21 February 2024

Yugipedia uses MediaWiki, which offers a powerful API for automated access to our data. This API can be accessed via https://yugipedia.com/api.php, and extensive documentation can be found on MediaWiki.org. When using our API, please observe some points of etiquette, to avoid endangering the site; offending agents may be blocked without warning.

User agent[edit]

All automated requests to the API should set a descriptive User-Agent header, including the name of the service and contact information. Requesters who do not do so may be blocked at any time without warning. For more information, see the User-Agent policy on Wikimedia Meta.

Request limit[edit]

Please limit requests to no more than one per second. The content of multiple pages can be bundled together into a single request with a pipe (|), e.g. titles=PageA|PageB|PageC.

Caching[edit]

Results of requests should be cached wherever possible, and the cache should be used instead of repeatedly requesting the same resources. A good period for caching is 30 days.

Updating data[edit]

Certain tasks done via the API, such as automatically building and maintaining a card database, may require information to be updated more often than every 30 days. In these cases, instead of simply rerequesting the entire data set, you should only rerequest those resources that have changed. This can be determined by watching our recent changes feed using list=recentchanges.

Other points[edit]

In addition to these, you should assume that the points on the API etiquette page on MediaWiki.org also apply to use of the Yugipedia API; that page also has some advice on how to reduce the potential impact of requests. If you have questions, need help, or want to provide feedback, you can join our Discord server.

What do I do if I've been blocked?[edit]

If you've been blocked because of misuse of our API, the first step is to join our Discord server and explain what you were doing with the API. It is very likely that your requests can be changed to meet our usage guidelines here, and we'd be happy to work with anyone who needs help on the matter.