Redline data

Contains game data for Redline. The data here is published at https://redline-dao.github.io/data/ and use for each race.

Tracks

Directory tracks

Contains track data,

• tracks.csv - CSV containing all tracks metadata.
  • trackId
  • name
  • locationKey - Accuweather location key
  • country_code - 2-letter ISO 3166 country code
  • coords
  • cellCount
  • cellLength
  • sponsorURL
• {TrackId}.csv - {TrackId} is the ID of the track.
  • Contains cell info for the track

How to

Add a new track

1. Add track row in tracks/tracks.csv. Let's say we add this track,

   bora-bora,Bora Bora island,2349_poi,French Polynesia,16°30′04″S 151°44′24″W,151,100,https://example.com
   

2. Create track cells CSV with at least following headers-
   • Angle, TerrainType, Slope, Lane0, Lane1, Lane2, Lane3, Lane4, Lane5
3. Put the file in the repo with name matching the ID of the track in tracks directory.
   • bora-bora.csv

Edit an existing track metadata

Just edit track info in tracks.csv. :warning: Avoid changing the ID of the track. If you really have to, make sure to accompanying {TrackId}.csv

Edit track cells

Edit {TrackId}.csv file.

NPC bots

Directory npc

• bots.csv - One bot NFT address per line
  • raceType
  • bots - can be comma separated enclosed in quotes

Last cell should contain bots NFT IDs one will be picked at random.

The table should look like this,

Prizes

Directory prizes

• prizes.csv -
  • raceType
  • experience
  • participationXP
  • eth
  • tickets
  • nftPartSkin - can be comma separated enclosed in quotes

Last cell should contain all possible NFT (Template) IDs one will be picked at random.

Uses 1st row if race type match is not found.

Guidelines

⚠️ Editing the headers can break the code.

After editing CSV files, preview them on GitHub.

Make sure the structure looks legit and there are no errors.

For example, Errors like this show up when comma-separated values need to be wrapped in quotes.