iDB Community Forum

I have to have an idea for my Web Programming project by next Thursday. It has to be a web site using html (obviously), php, mySQL, and javascript. I'd like it to be something MS-related.

I was thinking of doing a selling/buying thing where you would log in, have a character profile with your character names and servers, and could submit entries for things you're selling with their stats and the price, etc. It'd be more like basil than sleepywood in that you would select the item rather than typing it yourself so that it can be truly searchable by item, stats, price, and server.

Anyone have any other ideas? Keep in mind that I'd be working on this by myself in a relatively short period of time, so it wouldn't be anything fancy, it'd just get the job done. Also, it's only a project for the class, it won't be hosted as a real web site or anything.

That actually sounds pretty cool, if you could actually make a real website like that afterwards (but strictly for iDB members) i think it would be way better than the buying/selling thread that nobody really uses

Something that would be nice it's recording the prices of the sold items, so you would have a price check (if the item has been traded through the item). Basil has that, but since it's an auction site, the prices are usually off.

If your class is management oriented your teacher might like some usage statistics and estimate the future demand/supply as well as the prices...

Some ideas:

* You could create a game, like NQII but with MS Graphics... ( Char creating, equipment, items, monters, you have all the images that you need ). I could be a Multiplayer game.

* A DB system that help you saving DROP average ratios... ( Xk monster killed, drop Xi item Xt times, average, statistics and things like that )

* A forum with a graphic interface similar to MS...

etc... etc... etc..., if you need some help, PM me

Whoa, whoa, back it up there! I have at most a couple weeks to work on this, not months. I don't have the time to design a game. It looks like I'll be sticking with buying/selling. I was thinking about how cool it would be to use it as a replacement for the buying/selling thread, but that would require getting hosting.

I'm sure there's someone here that could host it for us. Wouldn't hurt to ask around anywho I think it would be a great idea, either way, good luck with it...

Spaz Wrote:Whoa, whoa, back it up there! I have at most a couple weeks to work on this, not months. I don't have the time to design a game. It looks like I'll be sticking with buying/selling. I was thinking about how cool it would be to use it as a replacement for the buying/selling thread, but that would require getting hosting.

Any of the ideas i told you can be done in a week or less...

You need to learn to design the full project in 1 day, take all the resourcers you will need, the next day, and the last one write code until your fingers hurt...

Good luck with the project!, and again, if you need help just ask...

PS: i will look over the net if i find any free Mysql-php-hosting services...

Ok, I've been planning the layout of the database, and this is what I've come up with. Let me know if I've forgotten anything, especially in the list of possible stats for equips.

Table users:
id_user
username
login_name
[hashed] password
signup_date ?
last_login ?


Table characters:
id_char
id_user
id_server [stored as a number to save some space, 1 byte instead of 4-6]
char_name
char_num [1-6, each user is allowed up to 6 characters]
id_class
level


Table servers:
id_server
name


Table classes
id_class
name


Table equips:
id_equip
name
id_equip_type [topwear, 2-handed sword, and so on, stored as a number to save space]
beginner
warrior
mage [these five are true if useable by that class]
bowman
thief


Table equip_types
id_equip_type
name


Table non_equips:
id_non_equip
name
id_non_equip_type


Table non_equip_types
id_non_equip_type
name


Table equip_ads:
id_equip_ad
id_equip
id_user
id_server
stats price
selling [true if a selling ad, false if a buying ad]
creation_date


Table non_equip_ads:
id_non_equip_ad
id_non_equip
id_user
id_server
quantity
price_per_item
selling [true if a selling ad, false if a buying ad]
creation_date


Table equip_ad_comments:
id_equip_ad_comment
id_equip_ad
id_user
post_timestamp
comment


Table non_equip_ad_comments:
id_non_equip_ad_comment
id_non_equip_ad
id_user
post_timestamp
comment


The equips and non-equips are separated to save the space taken by all the stats.

Table non_equip_ads:
id_non_equip_ad
id_non_equip
id_char
price
quantity
selling [true if a selling ad, false if a buying ad]

Table characters:
id_char
id_user
id_server [stored as a number to save some space, 1 byte instead of 4-6]
char_name
class
level

Table adsComments
id_comment
id_ad
id_user
date (timestamp)
comment

Ah, quantity was something I forgot. I made a deliberate choice to leave out class and level for characters since it's not really necessary. Also, I'm going to add a date field to the ad tables so people could see if it's just an old one that the person forgot about.

Not sure what you mean by comments. Do you mean things like "Could you lower the price to xxx?"

sometimes, the seller/buyer will not include all the info req in the ad.

Having comments and class/level, it also allow to suggests trades (item by item instead item by mesos).

I also forgot the date value in the ads... but... char instead of user?

Table non_equip_ads:
id_non_equip_ad
id_non_equip
id_user
date
price
quantity
selling [true if a selling ad, false if a buying ad]

Table equip_ads:
id_equip_ad
id_equip
id_user
date
stats

Two other suggestions added in user's table

Table users:
id_user
username
login_name
signup_date
last_login_date
[hashed] password