Often MA/PPs will be slow to react to, and fix an exploit. Due to very little communication from MA/PPs, many users will see the incident as a grey area and abuse it since no acknowledgement has been made that it is an exploit. I think it would help if we could have a description of what you would consider an exploit in your system in your words. Not too vague that it could be interpreted however people wanted. I understand that it will probably be hard to cover all circumstances, but some guidelines would help clarify to your customers the difference between smart thinking and exploits. Any feedback would be much appreciated, thanks.
FWIW: My personal definition of an exploit is something which give an unintentional financial advantage.
examples:
The old auction 101 bug ( I think it was 101 bids anyway) force an auction up to 101 bids then no more could be made, resulting in that person winning the bid at a cheaper price than expected.
Back in the day, trapping mobs behind objects to avoid armour/fap/tp decay
VTOL exploiting to avoid armour/fap/tp decay
Working out how to use mining amps that were broken to still get the amplification effect but not pay the cost for that effect.
I could add more but those are what I thought of first.
Also on EF here: https://www.planetcalypsoforum.com/...ear-description-what-exploit.html#post2588683
FWIW: My personal definition of an exploit is something which give an unintentional financial advantage.
examples:
The old auction 101 bug ( I think it was 101 bids anyway) force an auction up to 101 bids then no more could be made, resulting in that person winning the bid at a cheaper price than expected.
Back in the day, trapping mobs behind objects to avoid armour/fap/tp decay
VTOL exploiting to avoid armour/fap/tp decay
Working out how to use mining amps that were broken to still get the amplification effect but not pay the cost for that effect.
I could add more but those are what I thought of first.
Also on EF here: https://www.planetcalypsoforum.com/...ear-description-what-exploit.html#post2588683