next »

[Etheryal]

I've already created a semi-finished budabot plugin, that cache's the xml you have publicly available, and re-caches it if it notices any differences.  This should hopefully take some stress off the site, from bots constantly trying to contact it with each !boss lookup.  I'm not sure how you're backend database is setup, but instead of account creation, couldn't submissions just be submitted from the public, but make sure thats its moderated, ie. checked before finally submitted.

So, all submission would go into a temp db, and you/moderators, would "ok" the submissions, which could automatically be deleted from the temp db and inserted into the real boss db?  Dunno if that makes things any easier.

[dastof]

Eth; I'm going with your temp DB, and image verification. Thanks.

I'm done with the security/exploit aspects, and would appriciate ideas on layout for the page.

[dastof]

http://unimob.dastof.com/test/ - is where I am atm.

"Live" on the page is just my live test database, so feel free to play arround.

For now you can only edit current entries, and only with items that has already been added to the db.

If there are entries in both the live and temp DB, you will be able to switch between them at the top of the page.

Submited entries will always be loaded into the temp db, no matter if you read from live or temp db.

Future:
ITEMS
Items will be added seperatley, before or after you change add a new unique mobs entry. New item entries will be in a temp db. You'll be able to add items from the temp db when you edit/add uniques, but they won't show up on live until confirmed.

UNIQUES
New entries will be handled like edited ones, but nothing will be pre-filled.


ideas are welcomed as always.

EDIT: You can now add new mob entries to the db.

[Etheryal]

Nice work!

Just reporting in from the tests:  Both the add item form (at the bottom) and the find item form (at the top) return a "No input file specified" message.  As I understand it (correct me if I'm wrong), you are only able to add bosses for now.  I'm assuming you have a list of bosses in one table, and a list of items in another table, with a field in the boss table listing holding data for items that are related to that boss (not sure if you are using the unique id's of the items db to link them up, or if you are using the AOID of items.  To get the ball rolling on the items linkup (with bosses) [again, I'm not sure how your items db is situated, so this may not work at all], it may just be easier to load that entire items db that people rip after each patch and use that to work from.  It could easily be updated by modifying the rips people put out to just update the items in your database, or you could just run diffs between the databases and add any new items (though I recommend the first option, since FC can make changes to items at their discretion).  I know this would significantly blow up your db, but it may not be that bad (talking about +1-2 MB of data), and to offset that: when parsing the items DB, you could skip perks/implants/etc. (same way its done for ingame bots), and all the other non-item stuff, which should bring the size back down.

^ I figured that using pre-made rips of the *full* items db (minus all the junk/non-items stuff) would be easier on you since 1. lots of people already do the rips on their own, and you could just use one from a trusted source (saving you the trouble of updating patch after patch), and 2. it would save on waiting for people to update your db. (Ie. Heck, I wouldn't want to be the lucky fella that gets to add all the new Xan drops to your DB.  Its a lot of time on the users part, and it will be hard enough to begin with to even go to the site and get them to submit boss data, let alone fill out entire loottables. So that's why I suggested using a full rip straight from the AODB).  Once that's available, the user could simply just check off the items he wants to add to a boss (or search for them), rather than having to enter them one by one (qls, low/high item ids, etc).

In the boss db, you would just store the AOID of the item that it drops, along with drop rates (which you already do) and any additional information you want to store about a boss, and that particular item.

That's just my 2 cents, but you actually already have a setup that looks like you spent a lot of time on, of which I don't want to screw up or have go to waste.

^ Disregarding all that stuff: The add boss page looks like a great start.  Also, the xml that you have posted: does that get generated at run-time/the time it is accessed, or is it just that new xml is generated/made available every 24 hours/at some other interval?

[Llie]

FYI, I attempted to add "Customized Desert Reet 1000" to "Notum Soldier" and found the input sanity checker disallows the value of "PH" in spawn time (requires a numeric input) so the "spawned by place holder" value prevents updating of this record.

[dastof]

Thanks for all the input. I'll take another crack at it when I get home wednsday.

[Llie]

Can I recommend that you include a "PFID" field that lists a playfield ID number that is compatible with the /waypoint command?  This will make it possible to get little mission marker clickys as part of bot output.

[veremit]

Just had an enquiry regarding the bot plugin for Vhabot, a possible missing boss - "Astypalia" location: From inferno east, close to Phatmos a heckler boss.

If someone could check this out, that'd be great. Thanks!

[dastof]

Sorry for the slow progress, but I'm finding myself short of time...

Trying to make some easy to use items management based on Vhab's Central Items Database xml output, but like I said.. time shortage.

If someone else feels like continuing this project, I'll send you the files. Otherwise I'll just keep poking it in what little spare time I have.