Advertisement Bulletin Board

[Tim_Rocks]

Originally Posted by Supaman771

Quantity

My bad.

Um, if you push the search button it sorts by gun name instead of account. After making it, I kinda like the search window better. I fixed the typo though.

[WillaWonka]

Do it as account name/community name so we don't have to see a load of Graal1234567s

[Tim_Rocks]

Originally Posted by WillaWonka

Do it as account name/community name so we don't have to see a load of Graal1234567s

I'll give it a shot, The way I have it set up, it might be an issue. But I'll try and do it, most likely i'll have it formatted like this, Tim_Rocks (Graal123456). If that doesn't work, I'll just have to modify the DB table and include a row for community names (which is probably what I'm going to do)....

[cbk1994]

Originally Posted by Tim_Rocks

I'll give it a shot, The way I have it set up, it might be an issue. But I'll try and do it, most likely i'll have it formatted like this, Tim_Rocks (Graal123456). If that doesn't work, I'll just have to modify the DB table and include a row for community names (which is probably what I'm going to do)....

You shouldn't show the Graal###### at all. It's never necessary for players to see those (with the exception of players who haven't chosen a community name).

[Tim_Rocks]

Originally Posted by cbk1994

You shouldn't show the Graal###### at all. It's never necessary for players to see those (with the exception of players who haven't chosen a community name).

Well that's how I have it set up right now anyway.. So I'll just leave it, I suppose.

[bloodykiller]

as long as it's in alphabetical order so we'll find ppl with no problems

[jkldogg]

Graal#s are extremely annoying and not needed.

[salesman]

Originally Posted by Tim_Rocks

If that doesn't work, I'll just have to modify the DB table and include a row for community names (which is probably what I'm going to do)....

There's no reason to change your tables to store redundant data. I know there is already a table that stores every player's account/community name, and updates the community name if it has changed.

[Tim_Rocks]

Originally Posted by salesman

There's no reason to change your tables to store redundant data. I know there is already a table that stores every player's account/community name, and updates the community name if it has changed.

Well, I'm just sticking with community name, I'm not doing any of that extra un-needed stuff. I suppose if they update their community name the previous community name already in the DB will just be stuck in there... Unless a staff deletes it.

[cbk1994]

Originally Posted by Tim_Rocks

Well, I'm just sticking with community name, I'm not doing any of that extra un-needed stuff. I suppose if they update their community name the previous community name already in the DB will just be stuck in there... Unless a staff deletes it.

Uhm, you should not be storing the community name in the table at all unless you're using it in addition to the account. I hope you're keeping in mind that some players don't have community names, and that they can change. The account should be used as an internal identifier. There are already functions available for getting a community name from an account (DB_Names.getCommunityName or something like that iirc) that you should be using.

[bloodykiller]

/lookup "account name" or /lookup "community name" tells u both

[salesman]

Originally Posted by cbk1994

Uhm, you should not be storing the community name in the table at all unless you're using it in addition to the account. I hope you're keeping in mind that some players don't have community names, and that they can change. The account should be used as an internal identifier. There are already functions available for getting a community name from an account (DB_Names.getCommunityName or something like that iirc) that you should be using.

could use a JOIN operation to get community names in a single query. Assuming the table that stores updated accounts/community names is called 'accounts':

NPC Code:

---

SELECT bulletin_table.account[, other_rows_you_need], accounts.communityname FROM bulletin_table

    LEFT JOIN accounts ON bulletin_table.account = accounts.account;

---

My SQLite is a bit rusty, but I'm pretty sure the syntax is correct and that it would work without explicitly defining any primary/foreign keys.

[bloodykiller]

yah i agree with sales the npc code looks good id say, gj

[Tim_Rocks]

Well, here's what I changed tonight (not much), but I fixed the search to find things a little better.



What I'm working on now is limiting your options a little, I'm going to make it so it loads all the items from your inventory, removes spam and or crap.

[jkldogg]

Keep up the good work! =]