forsakenlegacy

Well, I'm planning to make a browser based game which would run using php + mysql.
The concept is obsolete in the question so I'll spare you the details.
The game I want to make will have a map, of 50 x 50 blocks.
原帖地�: TechSpott - Computer and technology forums http://www.techspott.com//showthread.php?p=3818
That is a total of 2500 blocks. Players can navigate through the map, etc, etc.

I want to ask, how do I implement the map? do I make 2500 entries into my database? do I use OOP? (or after i've made 2500 entries, how do I arrange them into a square?)

I'm really excited about this and any suggestions would be nice
Edit: I'm going to use css. My brother does designing and will do the graphics and lay-out of the website
@ the array reply

I thought of that. But without a database it would merely impossible to keep track of what block each player was on. Let on the other stuff I thought about. I just wanted to know how to implement it in SQL

Angie

are you using tables or css div?

I would use css div's then flot them left.

querythe database and echo out all the div's have a containing div_wrapper which holds 50 entries per row.

HTH

lansingstudent09101

Communication with a database is slow (relative to accessing data in memory), consider putting the map into a php file that you can require_once to bring it in. If you're not going to ever have the user write the map itself, this will speed up the game significantly.

User's positions can be stored in the database (or in the session and read back to the db on save).

Think of DB access as a necessary evil. It's like driving to the store to get food. You can do it, but you don't want to do it when you're starving. You always prefer to go to the kitchen and grab something. Memory is your kitchen, the db is the store.
原帖地�: TechSpott - Computer and technology forums http://www.techspott.com//showthread.php?p=3935

Without a database, it may be difficult if you want to know where every player is. The MAP however doesn't need to be in the database, simply a player table and that can be as simple as

PlayerID PlayerName X Y

Nigel

Your probably best starting off with a table with simply x and y as it's primary key. It's probably best to hold just the information relevant to that square in this table and it's worth creating a PHP class to manage access to it ( just keeps things tidy IMHO ).
Then you can have a table ( or probably a set of tables ) which relate to each player. A player table can hold their basic information, other tables can be used if you need to store multiple items ( perhaps a history of moves if you wanted ). Again if you created a PHP class - then you can keep access simple - and change your mind when you work out a better way of solving the problems.
As pointed out - memory is faster to sun things, so if this was an issue then it could be worth reading in details to memory variables. But always write any changes back to the database, saves anything being lost if anything goes wrong with the server.

Ratchetr

If you have 2500 blocks in your database, put an index column in the table. Start the indexes at 0. So you will have blocks from 0...2499.

From an index, you can compute the row and column of a given block:
row = index / 50
col = index % 50

From a row and col, you can compute the index:
index = row*50 + col

You can move N, S, E or W with simple math:
N - index = index - 50
S - index = index + 50
E - index = index + 1
W - index = index -1

Of course, you have to test first to make sure you aren't falling off an edge.