So since I was working on server and I some tutorials from this community I want to share what I did for some people who didn't know... I found alot of "guides" for max plus and they were all the same:
But this way it is exploitable, if you success you can drop item and client will still think that it dropped +13 lets say if +12 is max plus. And when you pick it up it stays +13 in database too.... So that is useless. So I made a trigger I don't know alot about perfomance so I just want you guys to tell me if that gonna affect perfomance alot....
Here is the Trigger on dbo._Items:
You can use ofc the same bug here but after every plus on the server same trigger will be triggered so if you want to save item you have to keep it dropped on the ground Ofcourse it is same thing to make auto query like for every 2 minutes...
Code:
[COLOR=#007700]IF (@[/COLOR][COLOR=#0000BB]Operation [/COLOR][COLOR=#007700]= [/COLOR][COLOR=#0000BB]90 [/COLOR][COLOR=#007700]AND @[/COLOR][COLOR=#0000BB]strDesc like [/COLOR][COLOR=#DD0000]'%Opt: +13%'[/COLOR][COLOR=#007700])
[/COLOR][COLOR=#0000BB]BEGIN
UPDATE SRO_VT_SHARD[/COLOR][COLOR=#007700].[/COLOR][COLOR=#0000BB]dbo[/COLOR][COLOR=#007700].[/COLOR][COLOR=#0000BB]_Items SET OptLevel [/COLOR][COLOR=#007700]= [/COLOR][COLOR=#0000BB]12 WHERE Serial64 [/COLOR][COLOR=#007700]= @[/COLOR][COLOR=#0000BB]ItemSerial
END [/COLOR]
Here is the Trigger on dbo._Items:
Code:
SET ANSI_NULLS ONGO
SET QUOTED_IDENTIFIER ON
GO
-- =============================================
-- Made by LogLoft From RageZone.
-- =============================================
CREATE TRIGGER [dbo].[MaxPlus]
ON [dbo].[_Items]
AFTER INSERT,DELETE,UPDATE
AS
BEGIN
-- SET NOCOUNT ON added to prevent extra result sets from
-- interfering with SELECT statements.
SET NOCOUNT ON;
UPdate _Items
SET OptLevel = 20 where OptLevel between 21 and 150 --20is max plus so i used 20 also it doesnt matter if it is with adv or not :)
END
GO
Last edited: