Comments by Qvazzler (Top 4 by date)

This is an excellent example of what I found after your help.

I am very aware of what you are saying, meaning I should not just copy something without understanding the principles behind it. I decided to step back a bit to see if my structure really is effective to start with, and I came to the conclusion of that the picture I found above matches my structure completely, with the one exception that I have not been using a diagram rather I have been using a simple excel sheet containing the tables and variable names.

Stepping forward again to the problem I have mentioned in this thread, I'm pretty sure I have found my solution. Since explaining it doesn't seem to do any justice (I'm not exactly used to speaking in terms of programming and such with others), I'll just conclude this with that I will be creating 2 new tables, one containing the conversations that exist, and another one that contains instances of conversations belonging to users.

Well for some reason I'm having trouble finding entity-relationship diagrams for sql that are actually practical/usable on an amateur level. I think however I never used the term "entity" in my searches.

Yes, I have been picturing things over and over and over, connecting a dot to the other, thinking how the code would process it, and so on. The only thing that puzzles me is the bit about having in-game conversations.

Thank you for all your help, I believe I can go on with my planning now based on the new knowledge you have provided me with.

You're right, this is very early and I haven't gone further than to map the database.

Ah, so it really was that hard to comprehend. Well I think I'll just make a new table for "conversations" or something and link it to messages in the "messages" table.