[RELEASE] Poultry, yet another GM tool! (Zoidberg reincarnated)

[marekrndr]

Poultry 2.0.3.4

• Code cleanup and optimizations
• Interface & text fixes
• Character query context menu fixed
• Added a bigger map to teleport control
• Added the world map NPC/character loader feature
• Added the Horizen map NPC/character loader feature
• Character list 'Detailed' context menu item fixed
• Minor adjustments to database connection method (startup only)

Poultry 2.0.3.3

• Context menu added to saved skills list
• Code cleanup and optimizations
• Interface fixes
• MonsterResource editor feature added
• Resource editors have epics after the label now, the labels show which epics I've tested and built them on. To have a missing epic supported, please contact me.

[calangaoo]

RE-up the icons please!

[YuhaBah]

Trying to connect to gameserver, but after starting connection, its going to eternity, but if i press "Cancel" the program is crit and exit.
Connection to DB - SUCCESS!
I try to put different ports on gameserver like 8841, 4502 etc ( and other, gain from Port Scanner) but take same result.

[Azreil]

Tries to connect auth.dbo.accounts but in the db it is listed as auth.dbo.account. refuses to connect because of this.

[vweegit]

Originally Posted by Azreil

Tries to connect auth.dbo.accounts but in the db it is listed as auth.dbo.account. refuses to connect because of this.

You can work around this by using a synonym:

create synonym Accounts for dbo.Account

[thefear511]

Originally Posted by vweegit

You can work around this by using a synonym:

create synonym Accounts for dbo.Account

is this a sql query?

[ThunderNikk]

Yes and it does work.

For new queries written inside the SQL window with the synonym name it will say that it is an invalid object name and invalid column name but it still does execute the query written under the synonym anyway.

[vweegit]

Originally Posted by thefear511

is this a sql query?

Yes, it is, sorry. I should have made that clear.

Originally Posted by ThunderNikk

For new queries written inside the SQL window with the synonym name it will say that it is an invalid object name and invalid column name but it still does execute the query written under the synonym anyway.

Interesting - SSMS does not give me those errors. It added 'Accounts' to the auto-complete context menu, even.

[ThunderNikk]

Originally Posted by vweegit

Interesting - SSMS does not give me those errors. It added 'Accounts' to the auto-complete context menu, even.

I just ran the query and then I wrote and added a query all without restarting server manager.

I will try it again tonight because it will have been closed and reopened and see if I get the same issues.

[thefear511]

Originally Posted by vweegit

Yes, it is, sorry. I should have made that clear.



Interesting - SSMS does not give me those errors. It added 'Accounts' to the auto-complete context menu, even.

wow! this makes so many stuff work xd many tools i had were compiled using the table name Account while other version of the game people like had the tablen mae Accounts making old tools not working xd thanks tho.

[vweegit]

Originally Posted by thefear511

wow! this makes so many stuff work xd many tools i had were compiled using the table name Account while other version of the game people like had the tablen mae Accounts making old tools not working xd thanks tho.

No problem. I'm surprised it hasn't been shared before: SQL server has allowed synonyms since SQL 2005. I've used it practically since my first day with PServer software when - it was either Poultry or Glandu's auth tool, I forget which - threw an error for that particular table.

Originally Posted by ThunderNikk

I just ran the query and then I wrote and added a query all without restarting server manager.

I will try it again tonight because it will have been closed and reopened and see if I get the same issues.

Hmm. Shouldn't require a restart, the synonym should immediately affect the project. I suppose there could be some goofy version dependency, but I can't recall ever seeing this issue with any version of SQL server, though I'm sure I probably missed a version or two somewhere along the years.

[ThunderNikk]

Figured it out...

In the top left window where it has a selection of available databases if auth is selected or you start the query with...

Use auth

then it works fine but if you try to direct to the auth database in the query it does not recognize the synonym in the written query or give you context menus but it executes it fine.

example

select * from auth.dbo.accounts where account like '%name%'

only works if auth is selected in the available databases drop down

but

Use auth

select * from dbo.accounts

works with context and no errors on invalid dbo

[vweegit]

Originally Posted by ThunderNikk

Figured it out...

In the top left window where it has a selection of available databases if auth is selected or you start the query with...

Use auth

then it works fine but if you try to direct to the auth database in the query it does not recognize the synonym in the written query or give you context menus but it executes it fine.

example

select * from auth.dbo.accounts where account like '%name%'

only works if auth is selected in the available databases drop down

but

Use auth

select * from dbo.accounts

works with context and no errors on invalid dbo

Glad you got it. I was going to have you query the auth DB sys.synonyms to make sure the synonym was applied there. SSMS defaults to applying the query against whichever DB you have selected, which tends to make me lazy.

You are correct:

use auth
create synonym Accounts for auth.dbo.Account

or

use auth
create synonym Account for auth.dbo.Accounts

Would be the proper syntax, depending on your circumstance.

Another handy snippet, you can check against a DB to see what synonyms you have created.

use auth
select * from sys.synonyms

This will show you varied information on the synonyms you have created.

[tanos77]

where can download icons. Link its down

[ThunderNikk]

Please check the dates on threads before posting.

This tool is no longer supported