Development Cycle Archive

---

Animi wrote:

---

Blair wrote:

The whole thing, but in this case I was specifically referring to the HAM changes.

Blair

Producer

---

Can someone tell me WHY they are changing the HAM system? No one has given any explanation of why it's changing.

To tell you the truth, I see no need to change it. If it ain't broke (which it isn't), don't fix it.

The current HAM system is simple, intuitive and easy to understand. It makes sense for players. Why change it? What is the compelling reason behind this change, which I suspect will be nothing more than a nerf to people's combat abilities.

---

---

Everseeker wrote:

Can't say for SURE (Since I don't work there) but I am about 99.997% sure that they already use a bug tracking database (Such as PVCS) The question becomes one of.... What can the dev's let us see.

Consider the fact that such a database is probably running a couple hundred "open" items at any one time. Also consider the fact that, mixed in with the rest, are game exploits that need to be patched, and "content" that would be considered as a "spoiler" if it became widely known [For example...Bug: container under Jabba's butt does not contains a +22 Flame Thrower instead of the +2....]

---

Exactly.

Blair
Producer

---

Blair wrote:

---

Everseeker wrote:

Can't say for SURE (Since I don't work there) but I am about 99.997% sure that they already use a bug tracking database (Such as PVCS) The question becomes one of.... What can the dev's let us see.

Consider the fact that such a database is probably running a couple hundred "open" items at any one time. Also consider the fact that, mixed in with the rest, are game exploits that need to be patched, and "content" that would be considered as a "spoiler" if it became widely known [For example...Bug: container under Jabba's butt does not contains a +22 Flame Thrower instead of the +2....]

---

Exactly.

Blair
Producer

---

So the container under jabbas butt does container a +22 flamer??

How do I get jabba off it?

This isn't rocket science. Add a field to the bug tracking software that identifies whether the item can be shown externally or not. I know this involves a database change but there should be someone qualified at SOE to work on databases (right?).

FT under Jabba's butt? No chance of getting it....he wont get off.. He is to FAT.

The issue is not their methods it's the results. This company seems to have no concerns with promoting builds into production with known defects. Issues identified on TC are still reproducible in production. That's not professional. And it's why SOE has the reputation it does.

Its interesting to me how they are going to fix the HAM system so people don't kill themselves doing specials (Carbineer etc) but prevent the rest of the people from spamming specials (BH KD/Eyeshot). These are two very different directions to be fixed in one fix.

I've also read Dev comments that the new combat system is pretty much going to stop people from spamming specials? Does this mean we now get to enjoy the wonder of auto-attack instead of weaving together complex series of combat specials (spam?)?

It seems to me if they really wanted to fix Carbineers etc from killing themselves they would rescale the HAM costs for those specific cases to achieve balance instead of ripping out the entire system and replacing it with something new (and untested/balanced). This makes me think they are doing this for other reasons they haven't shared...which makes me think its going to be some kind of mass nerfing as someone previously stated.

It makes me feel less sympathy for how busy they are if they are spending time on things that people don't view as broken when there are a multitude of very obvious bugs and broken things in the game that need work. Sony needs to get serious about finishing what they have started in a quality way before redoing entire parts of the game to somehow magically achieve balance.

---

KzinKiller wrote:

Can we get a Known Issues page (or forum, if you want to keep it private from non-subscribers) for bugs/corrections that are acknowledged by the devs and are on the list of things to look at? Just a list, maybe organized by categories of profession, etc. of what you devs have recognized as things that need to be fixed, possibly highlighting the ones that are the current focus (or not...I'm sure there are people who would complain about that). Each time a new bug or problem is confirmed, it is added to the list.

Hear hear, for the millionth time.

A bug-tracking system is NOT a Known Issues page. Dinky little 5-man software operations produce Known Issues pages for their customers, there is literally no excuse for a software project of this size to not have one, in fact it is exactly BECAUSE of the complexity of the project that it cries out for a Known Issues page.

Someone in the CS organization is tasked with keeping a web page updated on at least a weekly basis (daily is better) that provides this information to customers:

A. Nature of Issue

B. Known Workarounds

C. Status of Fix

D. Estimated date for implementation of fix

The bug-tracking system is one of the resources that the Known Issues editor uses, it is not the start & end of the task.

This resources saves customers from so much unnecessary grief, and takes such a large volume of work off of the CS organization answering questions that the customer could answer for themself, that there is quite literally no excuse for not having one. Any software organization that considers themselves professional already does it ... especially one with dynamic code and thousands of customers who are regularly receiving code updates.

Release Notes, Known Issues ... this is not rocket science, this is a minimum standard of quality in the software industry that anybody serious about their job has already been doing for years.

---

Agreed.

There may be reasons to not release certain types of information (hard-core "exploits", "spoiler" info), but there is no excuse at this point not to have better documentation of SWG - and I'm not talking Friday Features.

If people are going to be banned for exploiting the system, there needs to be a way to inform yourself about the intended functions and malfunctions of the game. Good example - medium naboo houses that can be placed in a row. When you try to place a deed, the ground becomes red and green. Red means NO and Green means YES, and anyone who has placed a lot of deeds knowsit can be tough to find a spot the system accepts. Yet, we are told it's an "exploit" to do this in some circumstances, and not in others. The basic premise of the problem is this : you cannot punish people or name-call ("exploiter!") if the person doesn't have the capability to inform themselves of the rules.

"In a way that's not intended..." is not a rule - I'm sorry, but I don't have mind reading abilities, nor the desire to spend my time playing a videogame in which I have to constantly question what is and is not intended by people who I've never spoken to who live 3000 miles away.

If the Devs can't be expected to keep up with the message boards, nor can a single player to gather all the information (which is unoffical at best) to know in many cases what is and is not working as intended.

There seems to be this attitude among a certain segment of MMO vets thateverything is justified simplybecause this is an MMO - therefore we should excuse the lack of logic when it comes tostandard business practice.

Also, I think it's of note that the bug tracking system is really just a database that is selectively looked at (as has been Dev confirmed). No one is just reading the bug databasefor the heck of it - they only actually go to itto gather more information when they finally become aware of the problem (i.e. from board postings, CS calls, etc.). So adding a new bug to the database has little use unless the Devs become aware externallyand consult the DB.

Audio

---

Blair wrote:

---

smallkaok wrote:

I'm one of the younger gamers (under 18)and I must say that I envy your job.

---

I love it.

---

Sometimes, the negative things I hear from people discourage me

---

Me too. We just focus on making the best game we can. When people see nice posts they send them to the team from time to time and that helps.

Blair
Producer

---

You sir are to be commended for the work and true Labor of Love that this game must be,

I play everyday,(yes Everyday)I have three accounts and looking at a forth (for my son)I wantedto say that the level ofyour workand that of your team mates shows.Only a true fancould undertake a project like this and keep at it the wayyou all have. To look on, and replyon these boards with the level of negativity that is thrown around must be overwhelming at times. I want to say thank you for sticking it out.

Their are many that feel strongly about one thing or another and it is good to voice such views but when you are working on something like a painting or craftinga table, it is one thing to have someone say "the sky should be darker" or the table needs more legs and here is why. but when people are spending money to use the table while it is being worked onpeople tend to be more like "THIS TABLE NEEDS MORE LEGS! FIX IT NOW!" insted of seeing that if theycould help show how to make the table work biggerand better for everyone, it is easy to yell for more then it isto show how to make more possible.

It's hard to see the forest for the trees sometimes and when you are looking to cut them down vs making them grow you end up with a vacant lot, nothing left but the cold hard stone beneath your feet and nothing to growfrom the warmth of the sun.

May the force be with you Blair

ALways.

Danoran.

---

Halmet wrote:

---

Blair wrote:

---

Everseeker wrote:

[For example...Bug: container under Jabba's butt does not contains a +22 Flame Thrower instead of the +2....]

---

Exactly.

Blair Producer

---

So the container under jabbas butt does container a +22 flamer??

How do I get jabba off it?

---