HCF/Framework

Status
This thread has been locked.

brickoh

Premium
Feedback score
3
Posts
20
Reactions
5
Resources
0
I'm in search of a talented Development Team with a lot of experience with Spigot/Bukkit API and NMS. You also need to have knowledge of how hardcore factions work as I'm need a custom hcf plugin/base (800$ budget). Both the base (basically the framework for all plugins that will run on a network) and the hcf plugin must be custom made not iHCF/HCTeams forks or any other sources that are opened to the public. To clarify all sources will be included in the final product. You can view specific information here about the hcf plugin here https://docs.google.com/document/d/1AsSxu5VQIIG9ZocfTWPbH4u4MX7mN-lPAc5wVZoz4sk/edit?usp=sharing The base will be discussed separately in dms.
 
PebbleHost
High performance, consistent uptime and fast support. Minecraft hosting that just works.

VodkaMagician

Feedback score
2
Posts
13
Reactions
7
Resources
0
This person is not willing to accept feedback from the get-go it may be extremely difficult to work with them in the long run, especially when talking on the subject of technical implementation and infrastructure.

OP doesn't know about the limits of Mongo and is not willing to learn and adapt to change. Have caution.

Side note: If you would like argue with me about the feasibility of Mongo, please contact me in DMs and I would be happy to talk it out with you. Let's not trash this thread.
 
Last edited:

brickoh

Premium
Feedback score
3
Posts
20
Reactions
5
Resources
0
This person is not willing to accept feedback from the get-go it may be extremely difficult to work with them in the long run, especially when talking on the subject of technical implementation and infrastructure.

OP doesn't know about the limits of Mongo and is not willing to learn and adapt to change. Have caution.

Side note: If you would like argue with me about the feasibility of Mongo, please contact me in DMs and I would be happy to talk it out with you. Let's not trash this thread.

This user came and contacted me on multiple occasions everytime I've made a thread requesting developers, has wasted my time just to say 'I will not be doing this project for you'. I removed you as you said 'I will not be doing this project' as I'm not going to waste mine or your time explaining everything. Don't come and trash my thread if you aren't going to state everything fact for fact.
 

VodkaMagician

Feedback score
2
Posts
13
Reactions
7
Resources
0
Don't come and trash my thread if you aren't going to state everything fact for fact.
Alright, let's state the facts.

has wasted my time
I was completely transparent with you about my intentions when contacting you. It was your decision to interact with me past that point.

I'm not going to waste mine or your time explaining everything.
That's why you waited to remove me until after I schooled you on the problems with Mongo, and not after I told you that I would be asking for more details about your project, right?

This user came and contacted me on multiple occasions everytime I've made a thread requesting developers
"Multiple" times is pretty vague, isn't? Let's "state everything fact for fact," shall we? I have sent you messages exactly twice about two threads you have made. First, on your thread requesting web development services where I asked for more information about the website you wanted made so that I could independently practice web development and make some portfolio items. I was being forthright to you about my intentions that I was not going to be the developer you paid to do the project. I do not see that as a negative thing. The second time I contacted you for this thread in an attempt to change your mind about your choice of data persistency because of the gargantuan problems that Mongo has had, caused, and will cause your project if used carelessly.

Face the music. You were embarrassed about the fact that I was able to backup my claims about Mongo with cold hard facts and provide real examples of real times that Mongo has caused real big problems. Instead of facing up to your lack of knowledge on the subject, you decided to let your pride get the best of you and removed me for it. I'm not here to trash your thread, I'm here to inform other developers about the behavior you have exhibited to me through my interactions with you.

Perhaps next time you should address problems instead of trying to discredit or ignore them. It would have avoided this entire situation.
 
Last edited:

TheCapeHack

Feedback score
0
Posts
1
Reactions
1
Resources
0
Alright, let's state the facts.


I was completely transparent with you about my intentions when contacting you. It was your decision to interact with me past that point.


That's why you waited to remove me until after I schooled you on the problems with Mongo, and not after I told you that I would be asking for more details about your project, right?


"Multiple" times is pretty vague, isn't? Let's "state everything fact for fact," shall we? I have sent you messages exactly twice about two threads you have made. First, on your thread requesting web development services where I asked for more information about the website you wanted made so that I could independently practice web development and make some portfolio items. I was being forthright to you about my intentions that I was not going to be the developer you paid to do the project. I do not see that as a negative thing. The second time I contacted you for this thread in an attempt to change your mind about your choice of data persistency because of the gargantuan problems that Mongo has had, caused, and will cause your project if used carelessly.

Face the music. You were embarrassed about the fact that I was able to backup my claims about Mongo with cold hard facts and provide real examples of real times that Mongo has caused real big problems. Instead of facing up to your lack of knowledge on the subject, you decided to let your pride get the best of you and removed me for it. I'm not here to trash your thread, I'm here to inform other developers about the behavior you have exhibited to me through my interactions with you.

Perhaps next time you should address problems instead of trying to discredit or ignore them. It would have avoided this entire situation.
I don't know why your trashing this thread all because you hate MongoDB. In reality if hes the consumer the one looking for a product he should have all rights to believe MongoDB is superior. Even if MongoDB has some underlying issues what database doesn't lol? Maybe instead of trashing a thread try to accept that not everyone will believe in your opinion even if it has some factual statements. All of this over some stupid database argument maybe get off mcm for a while?
 

NV6

the opensource person(?)
Premium
Feedback score
8
Posts
383
Reactions
223
Resources
1
This person is not willing to accept feedback from the get-go it may be extremely difficult to work with them in the long run, especially when talking on the subject of technical implementation and infrastructure.

OP doesn't know about the limits of Mongo and is not willing to learn and adapt to change. Have caution.

Side note: If you would like argue with me about the feasibility of Mongo, please contact me in DMs and I would be happy to talk it out with you. Let's not trash this thread.
What are the limits of MongoDB you're talking about? MongoDB should be more than sufficient for something like a HCF core.
 

VodkaMagician

Feedback score
2
Posts
13
Reactions
7
Resources
0
Even if MongoDB has some underlying issues what database doesn't
It isn't about Mongo having just any run of the mill minor issues. Unless, of course, you consider severe data loss and lack of security patches to be minor.

try to accept that not everyone will believe in your opinion even if it has some factual statements
You're right. Some people will drink just the kool-aid. Take sips or you'll choke.

What are the limits of MongoDB you're talking about?
Contact me in DMs and I'll be happy to give you a list of things with reference material.
 
Status
This thread has been locked.
Top