|Product Name||The Super Mario Sunshine Player's Guide (The Official Nintendo Player's Guide)|
|Category||Book / Magazine / Publication|
|Amazon.com||Buy on Amazon ~ 1930206232|
|Price New||49.95 US Dollars (curriencies)|
|Price Used||6.15 US Dollars (curriencies)|
|Author||Alan Averill; Jennifer Villarreal; Editor-Scott Pelland|
|Features||Used Book in Good Condition|
The Official Nintendo Player's Guide for Super Mario Sunshine is the official guide and is no longer available from Nintendo. The guide is complete with:
The game: Mario makes his debut on the Nintendo GameCube with Super Mario Sunshine. On a vacation away from the Mushroom Kingdom, Mario finds himself in a messy situation on the island of Delphino, where a Mario look alike has been causing all kinds of trouble. Explore huge 3D environments that range from a lush waterfall paradise, to an exciting amusement park complete with a rollercoaster you can ride. Mario makes use of a new water pack, which allows him to hover, launch, and rocket around levels, as well as spray enemies with. Mario has never had so many cool new moves, or looked so good in 3D.
|Similar Items||9781930206304: The Legend of Zelda: The Wind Waker Player's Guide|
9780307469076: Super Mario Galaxy 2: Prima Official Game Guide (Prima Official Game Guides)
9780761539612: Super Mario Sunshine: Prima's Official Strategy Guide
0045496950507: Gamecube Memory Card 251
0045496960896: Super Mario Sunshine
0045496960346: Super Mario Sunshine
0045496390365: Super Mario Sunshine (Gamecube, German)
9781930206144: Luigi's Mansion Official Nintendo Player's Guide
9781930206076: Paper Mario: The Official Players Guide
9781598120134: Official Nintendo Super Paper Mario Player's Guide
View 9 more similar items
|Search Google||by EAN or by Title|
The extra items are numerically indexed and provide extra text to go along with numeric values such as weights or distances or even currencies. The attributes that use these extra indexes are all numeric and take two fields. You can send the data in a single field as long as you use the same short or long text that we keep in our database.
Although the data feed API can deliver information as JSON or XML, we are using XML here because it is easier to read.
<attribute> <extra_group>Distance</extra_group> <field_name>depth</field_name> <extra> <id>501</id> <extra_short>in</extra_short> <extra_long>inches</extra_long> <seq>10</seq> </extra> <extra> <id>503</id> <extra_short>ft</extra_short> <extra_long>feet</extra_long> <seq>20</seq> </extra> <extra> <id>505</id> <extra_short>yrd</extra_short> <extra_long>yards</extra_long> <seq>30</seq> </extra> </attribute>
Looking at this example, you can see that the EXTRA portion is an array of values each with their own properties. Here is what each section means:
- extra_group - The text name representing the type of information the extra value represents. The extra elements are associated with this group.
- field_name - The field that this extra information is attached to. Multiple fields can be attached to the same extra_group.
- id - This is the unique id that identifies the specific extra element. It is unique across all extra groups.
- extra_short - The short text used to enhance the main data item.
- extra_long - The long text used to enhance the main data item.
- seq - The sequence that we use to display this element in a list. When two sequence numbers are the same we sort by the extra_long value.
This extra information is normally used in a drop down box next to the numeric data field that we want to enhance. Some examples might be:
- 12 pounds
- 15.25 US Dollars
- 354 grams
- 12.4 ounces
- 12 lbs
- 15.25 USD
- 354 g
- 12.4 oz
You see we can display the long or short version of the extra code by using the ID index.
Fields that make use of this extra information require it when pushing data back to us in the feed. You can either send the data in two fields (value and extra_id) or in a single field (value) as long as the text following the numeric portion matches the long or short version of the extra data we store for the field.
For example, if you wanted to update a field that represented distance with the value "100 yards", you could either send that data just like that in the value field value=100+yards or in two seperate fields value=100&extra_id=505 and you would get the same results. If you send an invalid extra_id or text after the number that doesn't match our accepted list, your update would be rejected.