|Colour Crafter||Remote IWuvAard Database Access|
I don't own the data contained in these tables. It is, to the best of my knowledge, all owned by Aardwolf and distributed only at the pleasure of Lasher. It has been built up into these databases by many more people than just me, and I don't feel that I have any particular right to impose conditions on it's usage. However, I do have some requests, if you make use of it. You're not required to follow them, but I would appreciate it.
As a final note, if you do take this access and run with it (in scripts or webpages), please let me know what you are doing. I'm curious to see what people come up with. Also, if you would like your script hosted on IWuvAard for people to download, feel free to ask. I'm fairly certain that something could be arranged.
Where are the speedwalks?
They are coming. The speedwalks table is not currently designed in such a way that makes it easy to export anonymously. I take Lasher's requests seriously, and I have to be sure that any speedwalk added through the website is validated by an administrative user before it becomes accessible to everyone - through the website or through anonymous access. This requires changes to the speedwalks table and to the speedwalks section, changes that I will make in the future. I can't promise when - I am busy these days. But it will be coming. :)
What about write access?
There have been some ideas suggested in regards to allowing write/update access to anonymous database users. Obviously this has important concerns that need to be completely addressed before such access is enabled. At this point, I'm afraid that all actual updating of data in the database must be done through the webpages at IWuvAard - this ensures a certain data consistency. If you want to have your scripts call the webpages at IWuvAard with data (POST or GET), feel free to ask me if you need help figuring out how they work - I'll help as much as I can.
This database contains the working data for IWuvAard. Anonymous read-only remote access to some of the tables has been enabled in order to help support the creation of client-side database-querying scripts.
Read-only login name: 'guest'
Read-only password: 'iwuvaard'
Example MySQL database connection command-line:
mysql -u guest --password=iwuvaard --host=iwuvaard.ipdaily.net iwuvaard
Example PHP database connection code:
dbh = mysql_connect ("iwuvaard.ipdaily.net", "guest", "iwuvaard"); mysql_select_db ("iwuvaard", $dbh);
Example PERL database connection code:
use DBI; $dbh = DBI->connect("dbi:mysql:database=iwuvaard;host=iwuvaard.ipdaily.net", "guest", "iwuvaard");
Explanations of the accessible tables, what they are used for, and their specific column types/names follow. Table keys are bolded and underlined in the tables below.
This table is fairly obvious - it contains the same information as the areas command on Aardwolf displays. The only extra field is 'virtual', which is used in the speedwalks section of IWuvAard. 'Virtual' areas are areas that are not actually in Aardwolf, but are in IWuvAard to facilitate the grouping of speedwalks (i.e. the 'Shops' virtual area). For any queries dealing with this table I suggest excluding anything that is flagged as a virtual area.
This is a simple 'mapping' table. It maps damage names such as 'slime' (an alias) to 'acid' (the actual dtype).
This beast of a table contains all the information from the IWuvAard equipment section. I'm not going to explain every field, as I think the majority of them are pretty clear on their own. 'equip_id' is a numerical identifier of the specific piece of equipment (only in the IWuvAard database, not in Aardwolf itself). 'submitted_by' is the ID of the user that submitted the piece of equipment to the databased. 'updated_on' is a timestamp for the last date that this piece of equipment was updated/edited on.
This table contains the mobdeaths data. This is basically a straight import from various invocations of the mobdeaths command in Aardwolf. Mob name and mob level are self-explanatory; area_id is a reference to the area that this mob can be found in (see the iwuvaard.areas table).
This table contains a list of socials. I believe that it is pretty self-explanatory - the 'social' field is the name of the actual social, s_id is the numerical ID of the social (not in Aardwolf, only in the database), add_time is the timestamp of when the social was added to the database. Fields 1 through 7 contain the relevant line from the shelp command on Aardwolf. The 'creator' field contains the name of the social creator/author, if it is known.