What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Buddy Team and Star Wars: The Old Republic

Status
Not open for further replies.
If it works as well as HB does I'll be MORE than happy.
 
discounts for existing customers is a very successful and valid sales tool. im getting the bot anyway but how much more happy will i be if its less than full retail if i trade in my wow lifetime, lots and hence happy customer before i even see the bot this makes me more forgiving should anything unforseen happen down the road. not that im not understanding i dont complain but you know happy customers and all that.

Don't see how it would be a successful 'tool'. It's not like they're rolling 500,000 different bots out on the factory track. They don't release bots very often, so I don't see why some people feel entitled to a discount of some sort.
 
Here we are a month in from the given release date so how we doing? Close or not even close? and dont post when its done BS. The guys working on it i think have a good feel. just looking for an update. Thanks doods keep up the great work!
 
Don't see how it would be a successful 'tool'. It's not like they're rolling 500,000 different bots out on the factory track. They don't release bots very often, so I don't see why some people feel entitled to a discount of some sort.
Agreed. Also, this market really is a small niche at best. Can't expect them to sacrifice profits that barely exist to begin with.

Sent from my Galaxy S II.
 
Here we are a month in from the given release date so how we doing? Close or not even close? and dont post when its done BS. The guys working on it i think have a good feel. just looking for an update. Thanks doods keep up the great work!
It'll be done when it's done.
When developing software you will run into unforeseen difficulties. That's what makes a deadline unpredictable. I'm glad the Buddycrew takes the stand that it'll be done when it's done. That way we can be sure that it's the best they can deliver when they deliver it.
Ultimate answer: It'll be done.... when it's done.
 
It'll be done when it's done.
When developing software you will run into unforeseen difficulties. That's what makes a deadline unpredictable. I'm glad the Buddycrew takes the stand that it'll be done when it's done. That way we can be sure that it's the best they can deliver when they deliver it.
Ultimate answer: It'll be done.... when it's done.

Did you post this to piss him off? I see no reason to do this? Inflamming someone.

He asked a legitimate question, we all know about deadline problems, anyone who has a reasonably decent job will understand. However, it doesn't change the fact.

Stop being a douche. If you don't have the answer he needs then don't post, especially not some patronizing explanation.

I probably think (although this is presumption) that he, like all of us, is itching to get his hands on it and is simply anxious.

Also to those people who say why discount? Because that is how you reward loyalty, it doesn't have to be big but is a token of thanks to those who buy your products. It's a common sales tool and one that works. It also helps people feel that they are not just another number. So don't be obtuse, think before you post ignorant statements about profit. It's clear that those who say "no, why?" lack a basic concept of product retail economics.
 
Did you post this to piss him off? I see no reason to do this? Inflamming someone.
I posted it because it's the only useful answer. "The guys working on it have a good feel". Yeah, they had a good feel a month ago that they were close but something popped up. If they now come back and say "We have a good feeling" and something pops up again, people will be complaining again. That's why "When it's done" is the only answer that should be given.

People get sad, angry, frustrated, disappointed when their expectancies aren't met. That's why the developers shouldn't give any expectancies; so that peoples expectancies don't become unreasonable. "When it's done" is only ever the right answer, even when the people working on it feel that they are close.
 
It'll be done when it's done.
When developing software you will run into unforeseen difficulties. That's what makes a deadline unpredictable. I'm glad the Buddycrew takes the stand that it'll be done when it's done. That way we can be sure that it's the best they can deliver when they deliver it.
Ultimate answer: It'll be done.... when it's done.


I think in my post i put "and dont post when its done BS" the question was directed to someone working hard on this gem not some forum trolling scrub to come in and give that same old idiot remark "It'll be done.... when it's done" if i wanted that answer i would go back to the 900+ posts and get that BS answer for myself. But to sum up what i was posting in the first place was simply is a Update from someone working on the bot.
 
Well i dont look at that thread cause i'm not applying for beta and seeing this is the offical thead i come here for info. Did bossland make you the offical forum police and ask you to post for all the dev's? i don't think so... never fear someone else will come along looking for an update and i'm sure you will be right there to pull them over and give em the old "It'll be done.... when it's done"
 
I agree it would be great to have a wee update on the eta on a release, Please no /Fanboi "It'll be done when its done" responses.

Also can we get a /Fanboi forum tag for Fanbois that would be just as mega as a swotr bot release.
 
Last edited:
Well i dont look at that thread cause i'm not applying for beta and seeing this is the offical thead i come here for info.
So basically....
You ask a question
I give you an answer
You don't like the answer so you call me names
I give you a Dev's answer
You still don't like the answer so you make up an excuse why you won't accept that answer

I answered your question because I'd rather the devs work on the bot than answer questions that have already been answered.
 
So basically....
You ask a question
I give you an answer
You don't like the answer so you call me names
I give you a Dev's answer
You still don't like the answer so you make up an excuse why you won't accept that answer

I answered your question because I'd rather the devs work on the bot than answer questions that have already been answered.

Not to 'nit pick', but he asked a question with an addendum "Don't say 'this'" and you felt the need to post what he specifically asked you not to. As for your statement of "...when it's done" is the only true response; that's pure idiocy. When releasing a product, not necessarily this one, a company releases ETAs in order to appease the waiting consumers. Even if released ETA is later pushed back, for whatever reason. If a company took the stance of never letting anyone know when they intend on releasing a product, people would simply abandon said company for better prospects. While I understand your point, and can, on some level, agree with it.

Your stance, however, on nobody asking when they could POSSIBLY (I said possibly, not DEFINITELY) expect a finished product, is pure lunacy. People simply want to be appeased and it is not for you, the non paid fan of their work, to intercept the paying customers (it is my understanding that in order for you to view and post, you must have purchased a license for one of their products) questions and impose your point of view on them. It is for the company or representatives of the company to respond to quite valid questions. As I too am curious when this product is ESTIMATED to be release, I would like to ask the question as well. And while I understand that the developers are busy, and I would like them to remain so, it is again, for them to respond to the question, not you. Thank you for your efforts in quieting the community.
 
Last edited:
If a company took the stance of never letting anyone know when they intend on releasing a product, people would simply abandon said company for better prospects.
That does explain the huge success of Blizzard. A company that never gives a deadline and only ever answers with "When it's done".
It also explains why all those other companies more often then not release buggy software just because it's not done when they said it would be done but their managers force them to release it anyway.

I'm sorry mate. I do understand where you're coming from. You're coming from the 1990s when it was totally acceptable to release buggy software just because you said it would be done. Nowadays we have moved on. Time has taught us that "when it's done" is really the only realistic answer to the question "when can I have it".
 
Actually, Blizzard does provide ETAs on their software, roughly 3 or so months in advance. It's generally done after internal QA, closed and open betas, so that the company is still closing bug tickets but a serviceable product is certain to be presented by the ETA. Other software companies, such as BioWare and Bethesda do it differently, but they still provide ETAs. Also, while writing software for a company or as part of a product, you can bet that if you don't work by deadlines, whether internal or public, there will be hell to pay.

That being said, the development environment here is less formal. I highly doubt that the team makes enough money out of this to make a living (which is why I feel it's unreasonable to ask our expect a discount). For that reason, I think forcing them to stay to a specific schedule is not feasible and very ungrateful. Regardless, there are many here who check nightly for more news, and it wouldn't hurt to get a sentence update on status, even if it's "nothing done today", much for the very same reason we check UPS and FedEx tracking sites every couple of hours, even though it's not going to make the package arrive any sooner.

Anyway, TLDR: you're right, it will be done when it's done. But that doesn't change the fact that the way you state it makes you look like an prick.

Sent from my Galaxy S II.
 
That does explain the huge success of Blizzard. A company that never gives a deadline and only ever answers with "When it's done".
It also explains why all those other companies more often then not release buggy software just because it's not done when they said it would be done but their managers force them to release it anyway.

I'm sorry mate. I do understand where you're coming from. You're coming from the 1990s when it was totally acceptable to release buggy software just because you said it would be done. Nowadays we have moved on. Time has taught us that "when it's done" is really the only realistic answer to the question "when can I have it".

Can somebody please change this track? It's becoming boring.
 
Also, while writing software for a company or as part of a product, you can bet that if you don't work by deadlines, whether internal or public, there will be hell to pay.
Yup, in the software development world we do work with deadlines. And we work with "You'll see what you get on the deadline when it's the deadline". Fixed time/fixed spec is something of the past. It's either fixed spec with "it's done when it's done" or fixed date with "what's done is done". That last one allows for much more business agility since it allows us to control the spec whilst insights change.
Anyway, TLDR: you're right, it will be done when it's done. But that doesn't change the fact that the way you state it makes you look like an prick.
It is true. I am a prick. But sometimes it takes a prick to make people see the truth.
I am the same prick with my customers but at least they know that when I say something, I'm not beating around the bush and they will get what they see. They know that if I quote them a price, it's the right price or I wouldn't quote it. They know that if I give a date, it's the right date or I wouldn't give it. Being a prick has it's advantages.
 
Update:

Testing profiles 1-10 for bugs

funky chicken melee combat still an issue (Aevitas is working on it)

UseObject tags works great now

minor profile problems that are being corrected
we're taking notes on elevators and they will have to be added to mesh
profiles need to have wonkavators (elevators that you push a button and get ported down to) - profile writer
profiles need to have taxis (flight paths) - profile writer

initial 1-10's will need said code implemented... as well as the branches implemented for quests (as we didn't get branches until we were a little bit into the 1-10's).

After funky chicken combat is fixed, i'll re-write my 1-10's while thoroughly testing them

After funky chicken is fixed, it will look a lot more promising

Funky Chicken: Think of a stupid 12 year old playing a rogue while in pvp
 
Status
Not open for further replies.
Back
Top