Friend/Ignore Lists

EQ2Emulator Development forum.

Moderator: Team Members

Post Reply
LethalEncounter
Team: Zombie
Posts: 2717
Joined: Wed Jul 25, 2007 10:10 pm

Friend/Ignore Lists

Post by LethalEncounter » Tue May 26, 2009 2:35 pm

As I am working on getting the right click menus for players worked out, I would like to get the friend/ignore lists working too. There currently is a character_friendlist table in the database, but I would like to make it hold both friends and ignored players. Any ideas for what it should be named to properly convey the dual purpose table?

Image
Retired
Posts: 251
Joined: Sun Oct 26, 2008 10:07 am

Re: Friend/Ignore Lists

Post by Image » Tue May 26, 2009 2:43 pm

ignore and friends are completely different lists.. so I guess you would call it player_social_list or something

User avatar
John Adams
Retired
Posts: 9684
Joined: Thu Jul 26, 2007 6:27 am
EQ2Emu Server: EQ2Emulator Test Center
Characters: John
Location: Arizona
Contact:

Re: Friend/Ignore Lists

Post by John Adams » Tue May 26, 2009 3:15 pm

How about just character_community? That's the name of the dialog, and menu option. Generic, and covers Friends, Ignore, and anything else we might dream up.
You do not have the required permissions to view the files attached to this post.

LethalEncounter
Team: Zombie
Posts: 2717
Joined: Wed Jul 25, 2007 10:10 pm

Re: Friend/Ignore Lists

Post by LethalEncounter » Tue May 26, 2009 4:57 pm

lol, I like how you put my nick in the Ignore field :P

User avatar
John Adams
Retired
Posts: 9684
Joined: Thu Jul 26, 2007 6:27 am
EQ2Emu Server: EQ2Emulator Test Center
Characters: John
Location: Arizona
Contact:

Re: Friend/Ignore Lists

Post by John Adams » Wed May 27, 2009 7:16 am

:) You caught that, huh?

Actually, Image may have a nicer name concept for the table. `character_social`. I only suggested Community, because in the client, "Social" seems to be emotes and macros. /boggle

The last suggestion again, from Images post, make 2 tables - character_friends, character_ignore. Don't worry about too many tables. We're fine :) If the functionality will read the two lists separately, it might make more sense to keep them apart so World only has to look at one or the other, instead of WHERE'ing through a single table. Up to you in that respect. Any of these table ideas work for me.

Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests