Hi,

I need some help with quests database design. Here is the table for Aion



I've checked a lot of games, and they presents similar tables for quests.

Let's say we have 100 quests in the game and 1000 registered characters. I see 3 options to work with the table:

1) For each player add 100 quests, ie, 1000x100 = 100000 rows... Problem: slow queries.

2) Limit only a few quests at same time for each character, for example 5. 1000x5 = 5000 rows... Problem: How to know what quests were completed?

3) Limit 1 quest only. Same problem than 2).

Some advice?

100'000 rows is not that big, use database indexes, it will be as fast as the wind!

Just an example. Imagine 150 quests and 50k registered users. That can't be fast...

Lineage 2, aion, wow, etc have millions of users. It must exist an optimal solution.

Just an example:
1. imagine char's inventory which contains 100 items. 50k chars make the table grow to 5'000'000 records and you can't throw away any item, because players will complain "Where's my item???"
2. imagine char's stats, including HP/MP, position, name etc. summary (for example) we have 30 stats per char. Although table will not contain more rows than chars count, the table will be very wide. And again players will complain if you take something away.

What database do you use?
Databases are not to be installed on home PC (where at the same time your server, client, visual studio etc runs), they work VERY fast with millions of rows on the server.

---

Just look at the screenshot.

P.S. no indexes on table and home PC running 10+ applications at the moment

Thanks laugan.

I'm not totally convinced but I will implement this big table. I hope you have reason.

My database is MySQL and it will run on a Rackspace cloud server.

If someone have another way to do this, please let me know.