Bounty Hunter Archive
Thread: Publish 20 :: Things to make it work
Page 1 of 2
OhBuggah
Wed Jul 13, 2005 3:52 pm
#1
1. Have seeker droids display the Jedi's name. This will ensure that low level paddies don't get ganked, nor gank squads formed since there will be a substantial delay between getting the mission and receiving the first seeker update. This will also allow us to monitor if the Jedi goes offline, circumventing the foreseeable exploit with Jedi regularly disconnecting to throw off tracking droids.
2. Have an option that disables all duel requests so that EVERYONE who tries to duel you receives the same "cannot duel" message. The current /duel exploit allows a Jedi to know he's your mark even before you do, eliminating the element of surprise that really is our only good weapon against high level Jedi. They could even just pull up your radial menu and see that "duel" is not an option on the menu to find out. When they do that they don't tip you off that they know. Besides, I tire of being spammed of numerous duel requests whenever I get near a group of Jedi -- even when I don't have a mission on any of them.
3. Mission terminals should display how long a Jedi has been idle. This will solve the problem of cantina-sitters who are AFK inside private structures. A bounty hunter will not get a mission on a Jedi who is idle for 30 minutes. It is such a waste of time (15-20 minutes) and buffs (10k credits a pop) to finally track down a mark to find he's in a private structure.
4. Allow seeker droids on Kashyyk to display which zone (Rryatt Trail, KKowir Forest, Myydril Caves, etc.) and instance (1, 2, 3, 4, etc.) the Jedi is in. Knowing the waypoint isn't such a big deal, but knowing the general area will help immensely. Certainly the programmers can write a small script to display this basic information without wasting time on figuring out how to make waypoints work with the current instance system?
If they just did these 4 simple things, Publish 20 will come across just fine.
Dreadzyn
Wed Jul 13, 2005 5:01 pm
#2
All very good ideas but, #4 is the best.
OhBuggah wrote:
1. Have seeker droids display the Jedi's name. This will ensure that low level paddies don't get ganked, nor gank squads formed since there will be a substantial delay between getting the mission and receiving the first seeker update. This will also allow us to monitor if the Jedi goes offline, circumventing the foreseeable exploit with Jedi regularly disconnecting to throw off tracking droids.
2. Have an option that disables all duel requests so that EVERYONE who tries to duel you receives the same "cannot duel" message. The current /duel exploit allows a Jedi to know he's your mark even before you do, eliminating the element of surprise that really is our only good weapon against high level Jedi. They could even just pull up your radial menu and see that "duel" is not an option on the menu to find out. When they do that they don't tip you off that they know. Besides, I tire of being spammed of numerous duel requests whenever I get near a group of Jedi -- even when I don't have a mission on any of them.
3. Mission terminals should display how long a Jedi has been idle. This will solve the problem of cantina-sitters who are AFK inside private structures. A bounty hunter will not get a mission on a Jedi who is idle for 30 minutes. It is such a waste of time (15-20 minutes) and buffs (10k credits a pop) to finally track down a mark to find he's in a private structure.
4. Allow seeker droids on Kashyyk to display which zone (Rryatt Trail, KKowir Forest, Myydril Caves, etc.) and instance (1, 2, 3, 4, etc.) the Jedi is in. Knowing the waypoint isn't such a big deal, but knowing the general area will help immensely. Certainly the programmers can write a small script to display this basic information without wasting time on figuring out how to make waypoints work with the current instance system?
If they just did these 4 simple things, Publish 20 will come across just fine.
Hnglka
Wed Jul 13, 2005 5:03 pm
#4
OhBuggah wrote:
1. Have seeker droids display the Jedi's name. This will ensure that low level paddies don't get ganked, nor gank squads formed since there will be a substantial delay between getting the mission and receiving the first seeker update. This will also allow us to monitor if the Jedi goes offline, circumventing the foreseeable exploit with Jedi regularly disconnecting to throw off tracking droids.
2. Have an option that disables all duel requests so that EVERYONE who tries to duel you receives the same "cannot duel" message. The current /duel exploit allows a Jedi to know he's your mark even before you do, eliminating the element of surprise that really is our only good weapon against high level Jedi. They could even just pull up your radial menu and see that "duel" is not an option on the menu to find out. When they do that they don't tip you off that they know. Besides, I tire of being spammed of numerous duel requests whenever I get near a group of Jedi -- even when I don't have a mission on any of them.
3. Mission terminals should display how long a Jedi has been idle. This will solve the problem of cantina-sitters who are AFK inside private structures. A bounty hunter will not get a mission on a Jedi who is idle for 30 minutes. It is such a waste of time (15-20 minutes) and buffs (10k credits a pop) to finally track down a mark to find he's in a private structure.
4. Allow seeker droids on Kashyyk to display which zone (Rryatt Trail, KKowir Forest, Myydril Caves, etc.) and instance (1, 2, 3, 4, etc.) the Jedi is in. Knowing the waypoint isn't such a big deal, but knowing the general area will help immensely. Certainly the programmers can write a small script to display this basic information without wasting time on figuring out how to make waypoints work with the current instance system?
If they just did these 4 simple things, Publish 20 will come across just fine.
I agree wholeheartedly with your ideas. Unfortunately i think number4 is beyond the ability of the devs at this time and I doubt that they will bother investing the time to work it out. this is the reason they disabled the seekers on Kash.
TheGreatFreyr
Wed Jul 13, 2005 5:22 pm
#5
i dont see why they can't give u the name once ur on the same planet as ur mark or like within 2k of him
HyprHypo
Wed Jul 13, 2005 5:24 pm
#6
Um about the duel thing, it should just say you challenge so and so to a duel. and tell the BH he has been challenged
ShaikeRamjet
Wed Jul 13, 2005 5:26 pm
#7
Hnglka wrote:
OhBuggah wrote:
I agree wholeheartedly with your ideas. Unfortunately i think number4 is beyond the ability of the devs at this time and I doubt that they will bother investing the time to work it out. this is the reason they disabled the seekers on Kash.
/sigh Why would someone create something, and sell it, that they could not fix?
OhBuggah
Wed Jul 13, 2005 5:30 pm
#8
HyprHypo wrote:
Um about the duel thing, it should just say you challenge so and so to a duel. and tell the BH he has been challenged
That would work also.
If a Mark /duels you his side system message says: "You have challenged Maura to a duel". Then on the Bounty Hunter's end she'll be the only one who gets the "You cannot duel someone you can already attack" error message if she accepts.
This is such a simple thing to do that they should've done in the first place. It's unfortunate that the Devs lack any foresight when they make substantial changes to the game that can only be described as hacks, not programming.
Hnglka
Wed Jul 13, 2005 5:32 pm
#9
ShaikeRamjet wrote:
Hnglka wrote:
OhBuggah wrote:
I agree wholeheartedly with your ideas. Unfortunately i think number4 is beyond the ability of the devs at this time and I doubt that they will bother investing the time to work it out. this is the reason they disabled the seekers on Kash.
/sigh Why would someone create something, and sell it, that they could not fix?
why does chat break on every third or 4th publish? Why did the devs state that the reason seekers werent working was the instancing? Why are products recalled from the shelves every day?
poor planning and testing is why in this case 
OhBuggah
Wed Jul 13, 2005 5:46 pm
#10
Hnglka wrote:
Why are products recalled from the shelves every day?
To play devil's advocate here ...
...Products are recalled from shelves because recalled products usually have some sort of real danger to the public, and by recalling them limits the amount of liability the company has if someone is hurt.
If SWG is broken nobody will die and nobody will sue since SOE is not liable for anything, especially since no one can ever die from a malfunctioning video game.
Hnglka
Wed Jul 13, 2005 5:50 pm
#11
OhBuggah wrote:
Hnglka wrote:
Why are products recalled from the shelves every day?
To play devil's advocate here
Products are recalled from shelves because recalled products usually have some sort of real danger to the public, and by recalling them limits the amount of liability the company has if someone is hurt.
If SWG is broken nobody will die and nobody will sue since SOE is not liable for anything, especially since no one can ever die from a malfunctioning video game.
LOL yes i understand that you are playing devils advocate. My point was a little more obtuse. Why was the product ever released at all? poor testing and quality control
FeartheLettuce
Wed Jul 13, 2005 6:48 pm
#12
great ideas... every one of them.... someone needs to make sure tanks reads this
BrendanK
Wed Jul 13, 2005 8:56 pm
#13
good ideas, but asking for waaay to much..
This is SOE we're dealing with here..you don't actually think they'd give this much sh1t to BH's do you? They're too busy tweaking the Jedi system....
again.
This is SOE we're dealing with here..you don't actually think they'd give this much sh1t to BH's do you? They're too busy tweaking the Jedi system....
again.
Page 1 of 2