posting exploits on the bugtracker not allowed?

[Akeera]

a few days ago I have written a bugreport about an exploit which makes it possible to rank up in repair skills very fast. on the following day I couldn't find the report anymore on the bugtracker. so I wonder now if it is not allowed to post such things on the bugtracker?

I also searched the bugtracker reports for details about this exploit and couldn't find anything. and the few experienced players I have spoken about it ingame didn't know anything about this exploit.

I am not complaining. I am asking how to behave in such cases.

[peeg]

Heya Akeera!

I guess you're talking about FS#2511.
This report was set "private" after you opened it, so that no-one but testers, devs and you can see it anymore. This is done to avoid spreading exploits via the tracker.
Shortly after you reported the exploit it was fixed and will not be "available" anymore after the next update

It's allowed and highly encouraged to report every exploit you find while playing! We're just making sure that reported exploits don't get even more known

Greetings

EDIT: Also keep in mind that only open bugs are included in the tracker's search by default - This could explain why you weren't able to find it anymore.

[Mordraugion]

If you do find an exploit inform a GM immediately via /petition (this will prevent you being accused of using an exploit when we find it) and either open a bug report with a "Exploit please make private" request or ask the GM's to do so

[Akeera]

understood 

[Prolix]

I am guessing that this was different than the expected behaviour in regards to stacking damaged weapons with undamaged ones to give an endless supply of damaged weapons. I seem to recall reporting that a long time ago and being told it was expected due to the stacking system. Is that no longer expected behaviour? I haven't tried it in a while.... thing do progress

[Caarrie]

Is that no longer expected behaviour? I haven't tried it in a while.... thing do progress

No that has not changed, just it has been reported already by a dev for a few other reasons and we are trying to deal with it as soon as we find someone that can fix it.