[FIX] Character starting kills (120000)

you must search at the PS_GameData -> dbo.chars go modify mode then to k1 -4 and look where is the 120000 kills change to 0.

That´s it

set default value K1,K2,K3,K4=0

Who's had this glitch? o.O

this glitch was by a friend ^^ and for few min a member ask me how he can change this too per PN ^^

Ahh I c, i've never heard of this bug, well now I have, but not before this.

This glitch i had on my EP5 test server, it's pretty annoying when everyone starts at rank *. Good way of fixing, thank you.

When i change 120,000 to 0 I click the X and it goes back to 120,000. Or if i change it to 0 and click excecute it dosen't work also clicking Cntrl+S dosen't work.

Im new to this so can you help? :\

Change 120,000 to 0 then press enter. Thats it

Quote:

PS_GameData -> dbo.chars go modify mode then to k1 -4 and look where is the 120000 kills change to 0

That just changes the characters kills its not a permanent solution, Is there anyway to change ever new characters kills to 0 ?

Thanks,

Quote:

Originally Posted by -Furious- That just changes the characters kills its not a permanent solution, Is there anyway to change ever new characters kills to 0 ? Thanks,

I think you need to change the K1 column in PS_GameData.dbo.Chars to default to zero instead of 120000.

How about editing the stored procedure for character creation and changing it there?

I know this thread is ancient and the last post is a month old, but I came across because I also had the starting kills at 120k. Im using sql 2005 standard edition, and there was no modify mode. There was however an edit mode, but edit mode is just like scripting the table to a new sql command editor.

You can easily change the default of k1 back to 0, however you still need to execute the sql script. This technically, and practically, can not be done because you are trying to create a table that already exists.

If you have not fixed this prior to letting people on your server, then i believe a backup of all characters in your db is going to be required. This is because, you would have to add a DROP TABLE PS_GameData.dbo.Chars a line above.the CREATE TABLE command, thus eliminating all data in the table. After creating another character, the starting kills were successfully back to 0.

Replace:

GO
CREATE TABLE [dbo].[Chars]

With

GO
DROP TABLE PS_GamaData.dbo.Chars
CREATE TABLE [dbo].[Chars]

Im only doing a test server so I only wiped my own 1 toon. No big deal if your still testing, however doing this after people are on your server could be a bigger task than your looking forward to.

Quote:

Originally Posted by Veritas Aequitas I know this thread is ancient and the last post is a month old, but I came across because I also had the starting kills at 120k. Im using sql 2005 standard edition, and there was no modify mode. There was however an edit mode, but edit mode is just like scripting the table to a new sql command editor. You can easily change the default of k1 back to 0, however you still need to execute the sql script. This technically, and practically, can not be done because you are trying to create a table that already exists. If you have not fixed this prior to letting people on your server, then i believe a backup of all characters in your db is going to be required. This is because, you would have to add a DROP TABLE PS_GameData.dbo.Chars a line above.the CREATE TABLE command, thus eliminating all data in the table. After creating another character, the starting kills were successfully back to 0. Replace: GO CREATE TABLE [dbo].[Chars] With GO DROP TABLE PS_GamaData.dbo.Chars CREATE TABLE [dbo].[Chars] Im only doing a test server so I only wiped my own 1 toon. No big deal if your still testing, however doing this after people are on your server could be a bigger task than your looking forward to.

You should be able to avoid that situation by checking the "Prevent saving changes that require table recreation" option here:
[Only registered and activated users can see links. Click Here To Register...]

I'm not sure if the location in SQL Server 2005 Express for this option is different, the screenshot is from Sql Server 2008 Express R2.

thanks for that info abrasive ^_^ was something i didnt even think about lol

Edit: SQL 2005 Standard Edition SP4 does not have the prevent saving changes option. It has been removed.

I cant edit the file with 2005 SQL, how did you edit it or what did you use to edit it?