Thread: 2D Multiplayer Games - Best Way To Store Items

Originally Posted by Versuprace

Most likely how RS does - which (I believe, but may be wrong) is either in an XML document or something of the sort and then unpacking the data with a java class.

Hell no, proper use of RDBMS is the best way to go

Originally Posted by S Quare Quxx

Hell no, proper use of RDBMS is the best way to go

Care to elaborate please?

Originally Posted by Jokerrr

I am making a multiplayer 2D game and I'm wondering, what would be the best way to store items and all their data?

Thanks.

Using java.util.zip.
[Only registered and activated users can see links. ]

Originally Posted by Google rapes bing

Using java.util.zip.
[Only registered and activated users can see links. ]

no .

Compression shouldn't matter for something like this, nor how it's stored beforehand, and assuming it's only loaded once at startup - just do whatever suits your needs and is easiest for YOU to work with.

Edit:
Meh.......

Code:

	private void loadSomeItemsPlz() {
		try {
			StreamTokenizer tokenizer = new StreamTokenizer(new BufferedReader(new FileReader(new File("items.txt"))));
			while (tokenizer.nextToken() != StreamTokenizer.TT_EOF) {
				int id = (int) tokenizer.nval;
				tokenizer.nextToken();
				tokenizer.nextToken();
				int price = (int) tokenizer.nval;
				tokenizer.nextToken();
				tokenizer.nextToken();
				System.out.println("loaded item #" + id + " and the price equals=" + price);
				// do what you gotta do yo
			}
			// print total amount of items loaded or something or how long it took, who cares
		} catch (Exception e) {
			// you done goofed
		}
	}

I'm personally a fan of MySQL databases to store data. But I believe you should only use MySQL if you're actually ready to release. Otherwise, I'd use some easy way to store data like .xml or .txt etc for just testing purposes because it's easier to manually edit.

Originally Posted by Mr. Brightside

I'm personally a fan of MySQL databases to store data. But I believe you should only use MySQL if you're actually ready to release. Otherwise, I'd use some easy way to store data like .xml or .txt etc for just testing purposes because it's easier to manually edit.

if you have the right tools, anything is easy to edit manually.

i choose mysql, but someone might choose some other db software. databases are meant for storing data. it is worthwhile.