Jump to content

Silhou

3rd Party Developers
  • Posts

    165
  • Joined

  • Last visited

Everything posted by Silhou

  1. Hey! Our apologies for making you wait. All the fixes need to go through a lot of processes before implementing, including internal testing, that's why it's taking some time. Our apologies on more time and thank you for your kind patience.
  2. Hey! Thank you for fixing it
  3. Hey! Yes, tracked it already. Thank you!
  4. Hey, @Snappy! Thank you for reminding us about this one. There was unfortunately a period when the reports didn't get proper feedback, our apologies. But all of the bugs were tracked anyway, so don't worry about that. This one is in the internal bug tracker as DCSF14-354 and is being looked at by the developers' team. Thank you once again for your kind patience
  5. Hey! Tracked internally as DCSF14-444. Thank you once again.
  6. Hey @Biggus! Thank you very much for creating the report. I'll add your information to the tracked issue for the dev team to investigate why the previous fix didn't work.
  7. Hey Snappy! Thanks a lot for your report. I've tracked it internally as AJS37-362.
  8. Hey! Thanks for the heads-up on this. It's already tracked internally as AJS37-338.
  9. Hey, @Snappy! Tracked internally as AJS37-361 for the team to look if bug or not. Thank you.
  10. Hey! Tracked it as AJS37-358, thank you.
  11. Hey! Tracked this one internally as DCSF14-435. Thank you.
  12. Hey @Lau! Thank you for the heads-up on this and sorry I've not replied to you back then. But I tracked this issue as DCSF14-404 when you reported it. It's greatly appreciated! The team is looking into this.
  13. Hey. Tracked this as DCSF14-434. Thank you!
  14. Hey! Thanks a lot, @Snappyand @TOViper. Tracked as AJS37-357.
  15. Hey, @bonesvf103! This one is known and tracked already, but thank you for the heads-up on this. The dev team is looking into it.
  16. Hey @nikoel! Don't worry, the dev team is looking into this.
  17. Hey @Snappy! Thank you for the heads up on this. I've tracked a bug report AJS37-356 for this issue. The dev team will look into it. @MYSE1234thank you too very much. It's greatly appreciated!
  18. Hey! Thank you. I added it to the internal report.
  19. @Snappythis one is tracked too as AJS37-351 Thank you once again!
  20. Hey @Snappy! This one is tracked now as AJS37-350. Thank you for your report!
  21. Hey, @Snappy! Tracked this one too as AJS37-349. Greatly appreciated!
  22. Hello @Snappy! Thank you very much for your detailed report. I've tracked it internally as AJS37-348. The team will look into it when able.
  23. Hey @Shaman! This one is known and tracked, but I added your report to that. Thank you very much, greatly appreciated
  24. Hey! I've already did, thank you
×
×
  • Create New...