How to deal with items clone

[eyez]

I don't have crashes bugs (as far i know) but clone items could be a BIG problem for me and for every other server owner.
So i wanna hear from more experienced people here, what should i do about this?
There is a good way to fix or get around of this?


Option 1:

CreatureEvent - [Lua&C++]Absolute anti clon system!

This system require this creraturescript: http://otland.net/f35/creaturescript-onmoveitem-moveitem-frompos-position-cid-96742/ When you install this creaturescript just add this code and you will never worry about item clon in your server: function onMoveItem(moveItem, frompos, position, cid)...

otland.net

This is a good way? Or it should lag my server a lot?

Option 2:

Feature - Antirollback

Instructions for anti rollback 1- install gdb sudo apt-get install gdb 2- compile the src with the flag for gdb cmake -D CMAKE_BUILD_TYPE=RelWithDebInfo .. 3- put the antirollback_config file in the ot folder (next to start.sh) 4- Edit start.sh to your OT folder...

otland.net

I didn't understand what is it...
It should fix the problem?


There are other options?
What do u guys think about all of this?

 

[Azakelis]

Option 1:
Trash - will use a lot of resources

Option 2:
Trash - the data could be corrupted

There are two ways to deal with item cloning:
1. Make your server uncrashable
2. Introduce some GUID for items stored in database

 

[maikons]

Option 1:
Trash - will use a lot of resources

Option 2:
Trash - the data could be corrupted

There are two ways to deal with item cloning:
1. Make your server uncrashable
2. Introduce some GUID for items stored in database

even with guid players cound't clone some amount?
i mean, i have 40 crystal coins, i clone to got 80...

other question this guid stuff wouldn't use a lot of resources too?

(those are just questions i don't even know how to do this)

 

[eyez]

Option 1:
Trash - will use a lot of resources

Option 2:
Trash - the data could be corrupted

There are two ways to deal with item cloning:
1. Make your server uncrashable
2. Introduce some GUID for items stored in database

I'll always try the 1, but for some reason the 2 could happen...
Did u know how to do this? or there is any topic here teaching?

even with guid players cound't clone some amount?
i mean, i have 40 crystal coins, i clone to got 80...

other question this guid stuff wouldn't use a lot of resources too?

(those are just questions i don't even know how to do this)

even if it become possible to clone amounts, for me it is enough...
players would be discouraged to clone and report the failure

about the resources... it use a lot too?

 

[Marko999x]

How comes its still such a big problem with clone items?

We live in 2021
Does tfs not have a working anti clone system yet?

 

[StreamSide]

I dont really know what kind of sources you using but I can give you a few tips we used some years ago.
One of these is the item unique id, you can save this value whenever but it should be unique for any item, then you only check for the item guid when you load the data.

I can give you the diff file for sure if you interested.

How comes its still such a big problem with clone items?

We live in 2021
Does tfs not have a working anti clone system yet?

no

 

[eyez]

How comes its still such a big problem with clone items?

We live in 2021
Does tfs not have a working anti clone system yet?

2 years ago i have a lot of problems with this
idk now but i'm scared

I dont really know what kind of sources you using but I can give you a few tips we used some years ago.
One of these is the item unique id, you can save this value whenever but it should be unique for any item, then you only check for the item guid when you load the data.

I can give you the diff file for sure if you interested.



no

why it is not a problem anymore?
servers just don't crash?


i'm doing a 8.6 project using 0.4 (Fir3element/3777 (https://github.com/Fir3element/3777/tree/master/src))

what is the diff?

so somehow we will add a unique ID for every item um DB and when server starts or something we will check if there is any duplicated
right?

 

[StreamSide]

2 years ago i have a lot of problems with this
idk now but i'm scared




why it is not a problem anymore?
servers just don't crash?


i'm doing a 8.6 project using 0.4 (Fir3element/3777 (https://github.com/Fir3element/3777/tree/master/src))

what is the diff?

so somehow we will add a unique ID for every item um DB and when server starts or something we will check if there is any duplicated
right?

yeah, the code its not for 0.4 but I guess you can do something with it because its just a few lines.

 

[eyez]

yeah, the code its not for 0.4 but I guess you can do something with it because its just a few lines.

this yeah was for what i think we gonna do?
or the question that servers just don't crash anymore?

about the diff, what is it?
it is the diff codes for this system works?
could u share it here?

 

[Evil Puncker]

How comes its still such a big problem with clone items?

We live in 2021
Does tfs not have a working anti clone system yet?

he is using an ancient tfs, that is why he is facing these issues

 

[Marko999x]

he is using an ancient tfs, that is why he is facing these issues

Do I not have these problems in tfs 1.3 at all?

 

[eyez]

Do I not have these problems in tfs 1.3 at all?

if somehow it crash, i think so
but that unique id items id stuff should solve it too
@StreamSide have the code, probably for 1.3

he is using an ancient tfs, that is why he is facing these issues

i don't have this problem with this one: Fir3element/3777 (https://github.com/Fir3element/3777)
but i had with other one, i just scare to deal with this again

my server is local for now
idk what gonna happen when i open to the world

 

[eyez]

I dont really know what kind of sources you using but I can give you a few tips we used some years ago.
One of these is the item unique id, you can save this value whenever but it should be unique for any item, then you only check for the item guid when you load the data.

I can give you the diff file for sure if you interested.



no

could u share the diff on 1x so i can try to convert to 0.4?
u guys think it is a good idea to have this feature?

 

[eyez]

I dont really know what kind of sources you using but I can give you a few tips we used some years ago.
One of these is the item unique id, you can save this value whenever but it should be unique for any item, then you only check for the item guid when you load the data.

I can give you the diff file for sure if you interested.



no

@StreamSide can u share the diff here?

 

[kamilcioo]

Load players on server startup and save on server close.

 

[eyez]

Load players on server startup and save on server close.

This is isn't the default behavior on servers?
I'm scared some day a player discovery a crash bug or something...
I'm overreacting this?

 

[eyez]

I dont really know what kind of sources you using but I can give you a few tips we used some years ago.
One of these is the item unique id, you can save this value whenever but it should be unique for any item, then you only check for the item guid when you load the data.

Pls share @StreamSide

 

[Silba]

Do I not have these problems in tfs 1.3 at all?

If your server can crash then items can dupe, especially if players can crash it on purpose.

 

[StreamSide]

Pls share @StreamSide

sure

 

[Kresh170]

How do the players duplicate the items?