Dev Zach/hydra technologies report

Scammer's profile link: Dev Zach
Amount scammed: 75 usd and a serious amount of time gone to waste
Discord ID + Unique Discord ID: Screenshot - 896e23f21ad3f926e5c72dd6d639b5bc - Gyazo
Proof that it's their Discord: Screen capture - 4b9c0c50a9b64f4e7eeecb23022a0f3c - Gyazo
Explanation of the trade: Paid 65 usd for a custom ticket bot, and a 10 usd add on

How they scammed/trade sreenshots:

About 5/6 months ago (i can't even remember how long it was exactly) i paid for a custom ticket bot via Hydra technology. This ticket conversation was actually deleted as the order was already marked as completed which it wasn't.
So i needed a custom ticket bot for my discord server, basically it was really simple it needed a claiming part and a permission part (so it's almost similar to the standard discord ticket bot which you can use for 5 usd a month)
We did some testing around 2 months ago with his developer @Apple6 where we did some basic testing and he asked some basic questions. I had never seen the entire ticket bot or tested the full version of the ticket bot done.
At some point after the testing i noticed that the ticket bot did not have any numerations, so it would contain basically the customer's name for example: luckycharm and when another similar ticket is opened it also contained luckycharm instead of luckycharm 001.
I mentioned to Zach how i did not notice this when testing and he told me that this could only be a add on so not a customization of the ticket bot since this wasn't mentioned with testing.
Screenshot - a0c958b293fc27158bf746d2fce84d44 - Gyazo
Screenshot - 3edf3313f5e2c2c9237cc90af8edcdde - Gyazo
Screenshot - 5f76fdab2d6c25b3fd1018e09aab7ca9 - Gyazo
Screenshot - 56bb8a6bff0b3179995e59f6eefe5cc4 - Gyazo
I mentioned how i needed the numeration for accounting purposes. Without this the both is basically worthless. Zach first said he would just add random numbers to the ticket. Then it was all of the sudden too much work and it had to be done outside of Hydra Technology, which i had to agree too because no other option was given and without numerations the a ticket bot with a discord of 500+ members was useless.
Screenshot - 50b36c6dc372124a5b3ad586b96a3450 - Gyazo
Here it is shown that therefore Zach wasnt taking any responsibility anymore which was fine, however the original ticket bot was never set up and the additions would take another month or so while i was already waiting 2-3 months.

So then i agreed with Apple. We will push the bot live as it is, without numerations and then the numerations will be added at some later point. Then Apple mentioned how that ticket bot was already up and running for weeks.
Screenshot - 9e9cc8d59e750d4d848e505091703fd2 - Gyazo
Which it never was. I then started to push them in order to make them deliver since it was already such a long time ago that i did my original request. Zach even had to "Demote/fire" his own worker in order to had him get motivated to actually finish the ticket bot, it is also shown that Apple did not even know how use "Linux" which proves the case that this bot was not completed at all.

Screenshot - b51ecf719be63a7ebf1f7cf6d1f908cd - Gyazo

Here Apple is it stating how he wants to put the bot live without me having any confirmation that it works to my desires. Remember i own a discord with 500+ members with open outstanding tickets which would need to be closed.
Screenshot - 038b9425f7532d1713b6dd5eb8c44f6a - Gyazo
Screenshot - 08789d124e6e7f33cebe3a135c9fc717 - Gyazo


When the guy Apple got demoted/fired things finally started moving, however i expected to just test the final version to see if things are in place, and then implement it but of course this was far from true. It looked like the ticket bot had to be made from scratch again. They needed all the information again from my part which i already provided 2 months ago when we did the really simple testing.

Information provided 2 months ago:
Screenshot - 4fd967d647b888f8951637557e42604f - Gyazo

Information asked a few days ago with more conversation:
Screenshot - 6763befafb8937cf3999f27c9893d138 - Gyazo
Screenshot - 7999d9196eb950505aa3c0332c329153 - Gyazo
Screenshot - 9c27bc89f10e6114184279a77a0aaeb6 - Gyazo
Screenshot - 300c32e8860510449ecf79e474b83756 - Gyazo
Screenshot - 8239d5b6244e5069cfdc2b929f362f4a - Gyazo

So then with the "actual testing" or however you wanna call it there were still things never touched upon. For the first time i could see the archive channel, which was basically just archiving not done with any information about ticket number or anything but just with random numbers being placed. It was already 100% clear that i had a 500+ discord server and that i needed stuff for accounting purposes, so i asked if this could be changed similar to the original ticket bot.

Screenshot - b652a47c5a47b579a437fd28f0239096 - Gyazo
Screenshot - ff3a8fa6b3a5d6cb5f2ec3c8dabb1041 - Gyazo

The reply was that we got to this part. However that was never true, we only talked about the option to delete/save transcript i never saw how it was actually saved in the transcript page since the first time we did bare testing.

Screenshot - a8c81dccdb5e3758290f1c4cf97b6b73 - Gyazo

So the bottom line is this:

I paid 75 usd for a ticket bot with simple numerations, the numerations would not even be delivered when the bot was "pushed live" because they didn't want any issues with a report, and they made me agree with it being outside of Hydra Technologies. Apparently the ticket bot was up and running for weeks, however when i actually wanted to implement it they needed all the information i already told them 2 months ago. Then they want to push the bot on my server without me having any confirmation that all the changes are there that i mentioned 2 months ago, as can be seen from the conversation there were bare changes made and it looks like its being written from scratch again.
Then when i see the archiving part (which i never seen before how it looks) this is all of the sudden also something that is a later add-on to a CUSTOM ticket bot.

 

[Dev Zach]

Hey Lucky Charm,


I apologize for the delay and the issues you've been having with us and I'm sorry it had to be taken to this point on Sythe. We will take this as a learning opportunity for the future. This is a very weird situation as Lucky told me multiple times that this bot was completed on my end.

Spoiler: Proof of Completed

He also knew there were going to be no more additions between me and him:

Spoiler: No More Additions

Now he's coming to me saying he needs these new additions before we release or he wants a full refund or he's reporting me on Sythe.

Spoiler: New Demands

As he also mentioned in his report he knew that I wasn't liable for any additions outside of the original order:

Spoiler: Outside of Hydra

I am very conflicted at what to do here. I'm trying to release the bot but there are new demands each time we try to release. If mods have any advice how to proceed here it would be greatly appreciated.


Thank you for your time,

Dev Zach

 

I feel like there is a lot of miscommunication with you and your worker which i can understand since i am not dealing directly with you.
But yes, you wanted me to say that the order was marked and completed just because you wanted the thing to get finished and didn't want to risk a sythe report. That's why you suggested that the order was marked and completed and the later add-on was supposed to be done.
But please enlighten me: How was the order marked and completed and the bot up and running for weeks when i needed to provide all information again?
You mentioned yourself a couple of times that if Apple delayed even further you were going to write it from scratch.
Screenshot - 99fb49703dceeb03d70754279dee4d71 - Gyazo

It is also remarkable how when an order is delayed i would be the victim of now having my desired customization's. So basically delaying and order will also lead to a decrease of quality for the customer. Do you think that is fair? You guys wanted to push the bot live as it is, and then when i did testing i see completely nothing done as i requested, i need to provide all information again, and when i see the archiving (which i never seen before) i need to pay for that extra, and it should be done outside Hydra Technologies.

It seems like you're trying to take the easy way out of things and doing your absolute best to try and have nothing to do with it.

This is you're worker and this original order which was never completely tested was done within Hydra Technology.

It seems like your worker Apple has been saying different things to you then actually going on, which implies all this miscommunication. For instance, two weeks ago he mentioned how all the changes (including the numerations were to be done after the weekend)
Screenshot - a347bd6bbfb1458cd7d5d473e7bc6695 - Gyazo
However after the weekend, and two weeks after still no changes. I tried to set multiple appointments with this guy which he could never meet. If you have to fire your worker in order to get him motivated he should not be in your team. You're the one that is in the end responsible for his actions. Which you are trying to avoid as much as possible.

I suggest that you either refund the 75 usd or that you deliver the bot with all the desired customization's within a week, which is even more then fair amount of time suggesting this is length out for around 5-6 months now. Hopefully this will not happen again with your service in the future.

 

@Lucky Charm what were the original terms of the project? imo, if a project is started and you realize that you want 'add ons' its up to them if they want to do it or not. The original terms should/would have been stated like this, "working ticket system bot that includes, numerizations, x, x, ect." or did you only ask for a working ticket system

 

Well the transcript was deleted. I ordered a custom ticket bot. And i feel like wanting things similar to the original standard discord ticket bot is not an add-on to a customized ticket bot to my preferences. We never discussed those parts, the first time we did testing we did not even go over everything, and for me it wasn't clear that the tickets wouldn't be numerated. The second time testing i saw the transcript for the first time, which i want similar to the standard discord ticket bot, however that is to be an add-on as well and to be done outside of Hydra Technologies...

 

Well the transcript was deleted. I ordered a custom ticket bot. And i feel like wanting things similar to the original standard discord ticket bot is not an add-on to a customized ticket bot to my preferences. We never discussed those parts, the first time we did testing we did not even go over everything, and for me it wasn't clear that the tickets wouldn't be numerated. The second time testing i saw the transcript for the first time, which i want similar to the standard discord ticket bot, however that is to be an add-on as well and to be done outside of Hydra Technologies...

Normally when you are starting a project, the customer declares what they want at the start of the project, so that they can get an accurate quote. When additions are requested after starting the project, its not apart of the original price/project. Dev Zach took the project as far as I know a "working ticket bot system" though what that contains is not known, but as far as I'm concerned if he provided a 'working ticket bot system' then that should be all he should have to provide, right? if something else was added into the original agreement then let me know, but if this was the case i'm not sure what you want here. If the 'fired' dev that was working on the project said he would do additions, then that would be on him, as the original project was taken by Hyrdra, though i believe that original project has been completed?

 

Normally when you are starting a project, the customer declares what they want at the start of the project, so that they can get an accurate quote. When additions are requested after starting the project, its not apart of the original price/project. Dev Zach took the project as far as I know a "working ticket bot system" though what that contains is not known, but as far as I'm concerned if he provided a 'working ticket bot system' then that should be all he should have to provide, right? if something else was added into the original agreement then let me know, but if this was the case i'm not sure what you want here. If the 'fired' dev that was working on the project said he would do additions, then that would be on him, as the original project was taken by Hyrdra, though i believe that original project has been completed?

Yes that is the case, however we agreed that i would get a customized ticket bot to my preferences. Because it got length out so much they needed all my information again which i provided months ago, then when i mention how some things are not the way i like they say: its not the original order.
So how does that work?
1) They need all the information again ( my original order ) which they seem to forgot
2) Some things that weren't touched upon are then said to not be within my original order. However how do they know when they forgot?

So please enlighten me @Dev Zach What was my original order? My original order was a customized ticket bot to my preferences. Please also sent a copy of the original ToS that you had which i agreed upon not the new one.

 

Probably Zach has the transcript as well where the order information is discussed?

 

[Dev Zach]

Hey LuckyCharm,

Below is the markdown format of our ToS from 8/23/2019 that you agreed to.

Spoiler: ToS

# Python Dev Co. Terms of Service

*Last modified: 08/23/2019*

## Introduction and Acceptance of the Terms

Welcome to **Python Dev Co.** ("Company", "we", "us" or "our")! By accessing and using this service (the "Service"), you ("you", "your") accept and agree to be bound by the terms and provision of this agreement. This means you shall be subject to any posted guidelines or rules applicable the services provides, which may be posted and modified from time to time, which we may do for reasons that include, but are not limited to, complying with changes to the law or reflecting enhancements to the Service. If you object to the changes, your recourse shall be to cease using the Service. All such guidelines or rules are hereby incorporated by reference into the Terms of Service ("Terms").

>ANY REQUEST OF THIS SERVICE WILL CONSTITUTE ACCEPTANCE OF THIS AGREEMENT. IF YOU DO NOT AGREE TO ABIDE BY THE ABOVE, PLEASE DO NOT USE THIS SERVICE.

## Rights to use the Service

The Service provides a personalised and on-demand software app ("App") development including, but not limited to, a Discord bot or a website. Subject to your compliance with these Terms, the Company grants you a limited, revocable, non-exclusive, non-transferable, non-sublicensable license to use and access the Service solely for your use, unless the Company specifically allows any other party to take part of Service's order. You agree not to (and not to attempt to):

* Use the Service for any use or purpose other than as expressly permitted by these Terms;
* Copy, adapt, modify, prepare derivative works based upon, distribute, license, sell, transfer, transmit, stream, broadcast, attempt to discover any source code, publicly display source code, reverse engineer, decompile, disassemble, or otherwise exploit the Service or any portion of the Service, except as expressly permitted in these Terms.

The Company reserves the right to modify or discontinue, temporarily or permanently, the Service (or any part thereof) with or without notice. The Company reserves the right to refuse any user access to the Service without notice for any reason, including but not limited to a violation of the Terms. If you violate these Terms, the Company reserves the right to issue you a warning regarding the violation or immediately terminate or suspend any or all orders or jobs for the Service.

## Intelectual property rights

All rights, title and interest in and to all materials that are part of the Service (including, but not limited to, designs, text, graphics, pictures, video, information, applications, software, music, sound and other files, and their selection and arrangement) are, as between the Company and you, owned by the Company. However, a license ("Usage License") can be purchased which gives you the permission to use said materials.

## Usage License

A Usage License must be purchased in order for you be able to use a requested App and its materials. The Company will not be hold liable in any circumstance for any damage caused by ill use of said App or the its related materials and we may permanently terminate or temporarly suspend your access to the Service, including any or all pending orders and/or jobs requested in the eventuality of a violation of these Terms.

## Rules of conduct and usage

The Service provides a personalised development of Apps. The Company has no obligation to monitor your usage of any App after the acquisition of a Usage License for it. The Company may also terminate or suspend your access to the Service at any time, with or without notice, for any reason. You acknowledge that any misusage of any App is neither endorsed nor controlled by us. The Company will not under any circumstances be liable for any activity using any App. As a condition of your use of the Service, and without limiting your other obligations under these Terms, you agree to comply with the restrictions and rules of use set forth in these Terms as well as any additional restrictions or rules (such as App-specific rules) set forth in the Service. As an example, you agree not to use the Service or any App in order to:

* orchestrate a scamming operation;
* make another app based on an App's materials such as source code, graphics or music.

These rules of use are not meant to be exhaustive, and we reserve the right to determine what conduct we consider to be a violation of the Terms or improper use of the Service and to take action including termination or suspension of your access to the Service.

---

If you have any question about these Terms, please reach out to us via Discord Direct Messages to any certified developer.

Concerning your transcript, my bot should have DM'd you a copy.


Kind Regards,

Dev Zach

 

@Lucky Charm let me know when you read the transcript and any concerns you have, if possible, send me ss of the portion where he/you states the additions are allowed, the terms of the original contract, and ect

 

@Lucky Charm

 

I have no copy of the transcript sent to my discord. I cannot find it.

@Dev Zach what are you proposing in this situation on how to solve it?

 

check your discord for the transcript

 

Screenshot - ad638562784b152dce822a9f0a13e379 - Gyazo
Screenshot - 89331c98abe5d9594eacb4d5da632dd6 - Gyazo
Screenshot - de6bb2e17b7b157d7b9b594c422a59ee - Gyazo

Here it is stated that it is customized to my preferences "basically a replica of the tickettool"

Numerations added to different tickets and numerations done within the archiving tool, are already part of the standard discord ticket bot.

Furthermore i mentioned how i was already using the standard ticket bot, and that the price was a bit too steep therefore.
However Apple suggested to go over the specs and mentioned how much "extra's" i would be getting.

 

@Lucky Charm , @Dev Zach will be getting in contact with you, or you can contact him in regards to adding the numbers to the end of the transcript. though this will be the end of the work from hydra. anything else will need to be paid for

 

the users are attempting to fix this

 

Zach wanted to add in the features but they weren't the same as the original ticket bot i am currently using. He tried to do some changes by himself since Apple was too afk but it wasn't to my desires. I asked if he could partly refund but he told me no.

That's a 75 usd gone to waste without a working ticket bot and a shit ton of time Spent.
Thanks HydraTechnologies.

 

This has finally been sort of resolved, though not as @Lucky Charm wanted it. Issues arose when the 'buyer/customer' @Lucky Charm wanted a specific bot, but only mentioned he wanted it similar to the original ticket bot. @Zach and his team completed the majority of these functions, though @Lucky Charm was not happy with it all so this report was made. The report did do some good for @Lucky Charm , but as he stated many times he only wanted a refund, which wasn't going to happen due to the coding that was already completed. This report forced zach to add two more functions, ticket numbering, and proper archiving. After completing these functions, @Lucky Charm still wasn't happy as it was missing a $claim function for workers to claim a ticket. This function is a premium function of the bot and must be paid for, so I felt that it was not necessary for Zach to compile more code into this bot. If you order a a product and ask it to be created similar to a original product, you should get that similar normal product.
TLDR; If you buy a standard basic version of a car, your going to get that stand basic version, no one is going to add in the premium features for free. If you want the 24 inch rims, you have to ask specifically for it, pay extra, or else you will get your 10 inch rims.