script to siege!

[daddycool.]

Maybe you need to modify the function binary date to date time,
just an idea, don't ask me how.

[l2zeo]

Originally Posted by Darth Nerd

Maybe you need to modify the function binary date to date time,
just an idea, don't ask me how.

There seems no to be problem in my thinking

[Zombe]

Originally Posted by Darth Nerd

Maybe you need to modify the function binary date to date time,
just an idea, don't ask me how.

Try this, go to that function and where it says
SELECT @v_strtime = '200' + CAST(CAST(@i_bin_time as int) as varchar(20))

Try changing the 200 to 201, since I guess the time in their binary format doesn't store decades, it is just put in the function, that its year 200X, and since we entered a new decade, it won't work anymore. No one thought that people will still play Dekaron in 2010+. So changing 200 to 201 will make it think its year 201X, and it should fix the problem of time converting.

Though the time storing may also cause a problem somewhere else, because if it cuts off millenniums, centuries and decades, it stored the time like
905172351 (9 digints), meaning 2009.05.17 23:51, but I wonder, will it now store it as 005172351 (9 digits) or 1005172351 (10 digits). If its the second case, More changes will have to be made. If it's the first case, changing that function, and maybe a few other functions like that, should fix the problem.

I hope that helps, and sorry, I cant test it myself, because my MSSQL evaluation period is over >_>

[EliteWarrior]

ANy one tested this and works?

[Decima]

it wont work . . .

[EliteWarrior]

Well i guess alot private servers out there are screwed? Why is there not one person sharing info ? This is very important!

[l2zeo]

Originally Posted by Zombe

Try this, go to that function and where it says
SELECT @v_strtime = '200' + CAST(CAST(@i_bin_time as int) as varchar(20))

Try changing the 200 to 201, since I guess the time in their binary format doesn't store decades, it is just put in the function, that its year 200X, and since we entered a new decade, it won't work anymore. No one thought that people will still play Dekaron in 2010+. So changing 200 to 201 will make it think its year 201X, and it should fix the problem of time converting.

Though the time storing may also cause a problem somewhere else, because if it cuts off millenniums, centuries and decades, it stored the time like
905172351 (9 digints), meaning 2009.05.17 23:51, but I wonder, will it now store it as 005172351 (9 digits) or 1005172351 (10 digits). If its the second case, More changes will have to be made. If it's the first case, changing that function, and maybe a few other functions like that, should fix the problem.

I hope that helps, and sorry, I cant test it myself, because my MSSQL evaluation period is over >_>

I change 2011 computer times and when did, become normalcy.
See that is not problem of that part.
Seem to become 0 problems that stick behind.
When is 2020, same problem happens.

[EliteWarrior]

Originally Posted by l2zeo

I change 2011 computer times and when did, become normalcy.
See that is not problem of that part.
Seem to become 0 problems that stick behind.
When is 2020, same problem happens.

I dont understand what you are trying to say can you clarify this in clear understandable english ?

[l2zeo]

Originally Posted by EliteWarrior

I dont understand what you are trying to say can you clarify this in clear understandable english ?

????
When changed from date of computer to 2011, error does not become.
but, when changed from date of computer to 2020 again, error becomes again.
When 0 this sticks behind, error seems to become.
Did you understand?

[skystar2003]

Originally Posted by caioc2

this is the full script to siege enjoy!


DECLARE @v_siege_no char(10)
DECLARE @guild_code varchar(10)
DECLARE @v_strDate varchar(10)
DECLARE @v_regdate varchar(10)
DECLARE @v_strChannel varchar(2)
DECLARE @i_bychannel tinyint
DECLARE @o_dwDungeonRegistTime varbinary(4)
DECLARE @o_DeadFrontTimeInfo varbinary(1000)
DECLARE @o_sp_rtn int
DECLARE @o_dwRegistTimeStart varbinary(4)
DECLARE @o_dwRegistTimeEnd varbinary(4)
DECLARE @o_dwTaxRegistTime varbinary(4)
declare @o_dwRegistTime varbinary(4)
DECLARE @v_strDate1 varchar(10)
DECLARE @i_GetDate datetime
DECLARE @v_siege_start_date varchar(14)
DECLARE @v_siege_start_time varbinary(4)
declare @guild_name char(20)
set @i_GetDate=getdate()
--// ??SELECT @v_siege_start_date = CONVERT(VARCHAR(10), DATEADD(d, 15-DATEPART(dw, @i_GetDate), @i_GetDate), 112) + '210000' ^EG\iO2X
--// ???SELECT @v_siege_start_date = CONVERT(VARCHAR(10), DATEADD(d, 7-DATEPART(dw, @i_GetDate), @i_GetDate), 112) + '210000' ,lA.C%4au~
--// ?????SELECT @v_siege_start_date = CONVERT(VARCHAR(10), DATEADD(d, 8-DATEPART(dw, @i_GetDate), @i_GetDate), 112) + '210000' VvFC -r,=G
SELECT @v_siege_start_date= CONVERT(VARCHAR(10),GetDate()+1,112)+'210000'
--//???? &[NG]V!Oc
SELECT @v_siege_start_date = CONVERT(VARCHAR(10), DATEADD(d, 15-DATEPART(dw, @i_GetDate), @i_GetDate), 112) + '210000'
SELECT @v_siege_start_time = SUBSTRING(@v_siege_start_date,4,1) * 100000000
+ SUBSTRING(@v_siege_start_date,5,2) * 1000000
+ SUBSTRING(@v_siege_start_date,7,2) * 10000
+ SUBSTRING(@v_siege_start_date,9,2) * 100
+ SUBSTRING(@v_siege_start_date,11,2)
SET @guild_code = '001'
SET @guild_name = '<color=green>LoLz'
SET @v_siege_no = SUBSTRING(dbo.FN_DateToShortStrDate(GetDate()), 3, 4) + '0001'
INSERT
INTO GUILD_INFO(guild_code, guild_name, guild_Level, bystate, bychannel)
VALUES (@guild_code, @guild_name, 3, 1, 1)
INSERT
INTO SIEGE_INFO(SIEGE_NO, CHANNEL_NO, GUILD_CODE, GUILD_NAME, DWSTARTTIME, BYREGISTTIMEFLAG, DEFENDER_INFO, SIEGE_TAG)
VALUES (@v_siege_no, 1, @guild_code, @guild_name,@v_siege_start_time, 1, 0X0000, 'Y')
EXEC SP_SIEGE_START_TIME_U @guild_code,1,0x01,@v_siege_start_time output,@o_dwRegistTime output,@o_sp_rtn output
set @v_strDate1=dbo.FN_BinDateToDateTime(@v_siege_star t_time)
declare @P1 varchar(13)
set @P1=NULL
declare @P2 varchar(33)
set @P2=NULL
declare @P3 varchar(25)
set @P3=NULL
declare @P4 varbinary(4)
set @P4=NULL
declare @P5 varbinary(4)
set @P5=NULL
declare @P6 varbinary(4)
set @P6=NULL
declare @P7 varbinary(4)
set @P7=NULL
declare @P8 varbinary(4)
set @P8=NULL
declare @P9 varbinary(4)
set @P9=NULL
declare @P10 varbinary(4)
set @P10=NULL
declare @P11 varbinary(2)
set @P11=NULL
declare @P12 varbinary(2)
set @P12=NULL
declare @P13 varbinary(2)
set @P13=NULL
declare @P14 int
set @P14=NULL
declare @P15 int
set @P15=NULL
declare @P16 varbinary(4)
set @P16=NULL
declare @P17 varbinary(996)
set @P17=NULL
declare @P18 varbinary(996)
set @P18=NULL
declare @P19 varbinary(1000)
set @P19=NULL
declare @P20 int
set @P20=NULL
exec SP_SIEGE_INFO_R 1, @P1 output, @P2 output, @P3 output, @P4 output, @P5 output, @P6 output, @P7 output, @P8 output, @P9 output, @P10 output, @P11 output, @P12 output, @P13 output, @P14 output, @P15 output, @P16 output, @P17 output, @P18 output, @P19 output, @P20 output

how i use it ?

[EliteWarrior]

Wait a sec is this a edited a siege script?

@i_GetDate), @i_GetDate), 112) + '210000' ^EG\iO2X 
--// ???SELECT @v_siege_start_date = CONVERT(VARCHAR(10), DATEADD(d, 7-DATEPART(dw, @i_GetDate), @i_GetDate), 112) + '210000' ,lA.C%4au~ 
--// ?????SELECT @v_siege_start_date = CONVERT(VARCHAR(10), DATEADD(d, 8-DATEPART(dw, @i_GetDate), @i_GetDate), 112) + '210000' VvFC -r,=G

the getdate number is 210000 wasnt it before less?

[l2zeo]

Originally Posted by skystar2003

how i use it ?