Development Cycle Archive

so what? you thought slicing a single item 5 or 6 times as allowed? you basically have to weigh 450 pounds and jump through some pretty tiny fiery hoops to get this to work...well you have to try pretty hard to figure it out anyway.

banned, with good reason. wanna not get banned? stop exploiting, stop duping, stop cheating...

'Nuff said.

---

Vercin_getorix wrote:
Ok, I am game.

Until the players receive a clear explanatory statement from the development team about specific exploits as they are identified, the permanent banning of unwarned players is misguided and despotic.

'Nuff said.

---

Put mission terminals like AO,Sliders for:

A) Difficulty

B) Distance

C) Creature or NPC

D) Ranged or Melee

E) Agressive or Passive

Its no point in keeping the "One armed bandit" terminal model (unless you really like clicking hundred times before mission?)

---

TolaGarf2 wrote:

Thunderheart, I would like to bring up an issue about the "almost" forgotten daily server reboots..

What is the purpose of this still? Clearly the servers should be able to run at least 5-7 days without a restart. It seems to me that this has justgotten routine for the tech-guys.

I realizethis is done in the hours where the most of the playerbase is offline, but keep in mind that there are thousands of European players on the US serversin the hours when the server reboot happens. This is getting very annoying and it feels completely unnatural to me (and a lot of other players I would assume). And of late, it seems the reboots takes longer and longer, sometimes up to two hours (Bloodfin is extremely slow with the loading process)! This can't be right?

The game has been out for like 7 months now, and still this is done on a daily basis. If there is a reason for these daily server reboots, please atleast explain to us why this is still happening and when we can expect thisto stop.

Thanks.

---

suspend permadeath until you fix Jedi bugs

1. Since the vehicle publish, the "Find and Track" option on seeker driods causes a crash to desktop if you take a shuttle while the droid is still seeking. I will continue CTD until the droid looses it's target. For investigation 4, this is up to 8 times. More for a Master BH.


2. Using the "Find and Track" option on seeker droids does not decrease the droid count in inventory.Once a BH makes Investigation 3, he/she does not need to purchase seeker droids. If the "Find" option on the seeker droid is used, it does use the droid.


3. The "Find and Track" option on probe droids does not work. The probe droids always looses the target after the first find.


4. BH probe and seeker droids do not return feedback on Jedi Missions.

I have buged all of these but I thought I would through it out in this discussion. I have not been playing my BH that much due to the new problemof number 1, causing CTD.

I am not a member of a player association, but it would be cool if clothing and armor can have "guild emblem" for it's members.

Skill tapes require a minor but quick fix, as there has been an increase in skill tapes due to chests etc now working this is becoming more of a problem.:

1) Skill tapes dont stack properly, they only use the higest value. This does not seem very sensible as you can't add 2 +1 items onto the same piece ofclothing, but you can add them onto seprate clothings to give the totalaffect.

2) Skill tapes with more then 1 skill on them are bugged. This is definatly a bug as there is no way of getting the other skills on the skill tape, this really needs to be fixed. (just to clarify you only gain the benifit of the highest skill on the tape)

these are 2 similar and simple to fix problems.

i would like to see the gcw evolved so that player cities are attacked on a larg scale by the opposing faction. i think this would add a real battlefield secanrio to each area and allow player cities to test their defenses.

tinnmorus

tkm/mf

starsider

---

jexra wrote:
I would ask the devs to examine the average starting FS character and determine if their current skills give them a decent chance of surviving a BH attach. Not win a battle against a BH at this early stage just a fair chance to flee.

---

You do have a chance of surviving. Run. Or Bribe me. Claiming once again that the Bounty Hunters have the 'I Win' card, with so many other professions in this game way more powerful, is too much.

It's time we started looking at the facts, rather than the tons of statements like this, made by many who aren't even FS.

Recommendations to correct Jedi Bounties, and Jedi exploits:

1 - A Jedi Bounty is permanent. This removes any possibility of the FS player logging off (exploit) to clear the bounty. Every one I've identified so far uses this exploit.

The bounty, then, is permanent...until either the Jedi player or the Bounty Hunter is killed. This clears the mission.

2 - BH droid usage. To avoid obvious BH exploits, the arakyd probe droids will only return the planet location, at coordinates 0,0. Only 1 seeker can ever be used per mission. Once that seeker stops returning a waypoint, no further seekers can be used to pursue the bounty.

This way the bounties are pursued using the technology available, but only to a limited extent. If the Jedi escapes from the initial pursuit, odds of survival increase dramatically.

3 - For both the Bounty Hunter and the Jedi, a /bribe command is instituted. Even at a distance, or other planets, /bribe Bounty Hunter Name allows the Jedi to buy their way out of being killed, as an option. Same for Bounty Hunters on the hunt.

4 - All Bounty Hunters, accepting the same Jedi's bounty, have a TEF versus each other. This allows BHs to duke it out for the rights to claim the bounty, and increases the chance of the Jedi's survival by producing a situation where the BHs involved are not all concentrating on the Jedi target. This is consistent with the EU.

5 - Remove Jedi armor wearing abilities. This one is obvious.

There is an ongoing request from the BH correspondent to have the NAME of the Jedi bounty target removed from the missions. This is a very simple solution which allows us full usage of our droids. However, if a BH can send droids out indefinitely, with no other drawbacks to the mission, there is no way we can miss the target, name or not.

Instead I recommend the above.

(optional)

6 - Temporary solution to Jedi logging off. Ifa Jedi has a JEF on them from a bounty, they cannot log off to clear the mission from the BH chasing them. Instead, they remain in the geometry for 30 minutes after logging.

All this exploit is doing is causing BHs to lose a lot of money in travel tickets, only to find their target logging off and the mission disappearing. This exploit must be corrected. If a player intends to gain a bounty on them, then they should be prepared to remain in the game to face the consequences. Otherwise, they are simply leveling-up their characters without fear of these consequences effecting them.

7 - A player that has both a Bounty Hunter and Jedi, who is exploiting the system to gain massive credits for the Bounty Hunter and/or level him/her up, should face permanent banning as a possibility.

The exception to this rule should be players who work directly with the design team/CSR and are known for testing the bounty procedure, and the combat balance.

The credits, however, should be removed for collection of any bounties of these players to avoid a free pass to a large fortune.

Regardless of what is done, it must be remembered that many Jedi players are exploiting the system, to avoid Bounty Hunters who may be griefing them. Obviously, a change is required here that will balance the system, and make it fair for both parties involved.

As to the original 'quote', I would direct DEV to this thread, to testing of Bounty Hunter versus Jedi Guardian in combat. The results should be enlightening, and prove this quoted poster wrong. We simply do not want a galaxy full of Jedi. Seriously. Unfortunately, there is little we can do about it, since eventually they will learn how to survive and level-up. This will create a significantly large population of Jedi on each server, which is something I assumed we wanted to avoid, based upon statements made int he past.

Combat test link:

http://forums.station.sony.com/swg/board/message?board.id=jedi&message.id=212953

good luck....