Creature Handler Archive
Thread: Publish 7: Major (CH-related) Features
the reason for a 30second timer in the wild is that you cant pull a vehicle and just scoot off. if you want your vehicle out and ready that is a different story and you are stuck to that general area. being able to just whip a vehicle out at will would diminish the game.
personally i dont mind a 30-sec timer if i dont have to lug friggen tents around. i would prefer a 15 second timer or no timer. but i know why there is a timer and i wont puch for that. i am looking forward to this since i can now use vehicles and mounts as needed without having to cart crates of tents around.
- People who like to take acondescending attidude andcall others "children" are usually children themselves
- Get it through your thick head that TH did not use the type of intellectual argument (I hate to call it that) that you were making. His [TH] justification was simply torestrict CH acting as "poke" handlers calling their pets and surprising someone in PvP. That is a INSANE argument.
Message Edited by SomeUser on 02-20-2004 05:03 PM
Vezek [quote]There is a 30 second delay after you call for a vehicle/mount/pet/droid before it will generate[/quote]
Am i reading this right? So when we access our datapad, call our pets, it takes 30 seconds for them to come out?
IF thats the case, that is retarded.
Nikay wrote:
[quote]There is a 30 second delay after you call for a vehicle/mount/pet/droid before it will generate[/quote]
Am i reading this right? So when we access our datapad, call our pets, it takes 30 seconds for them to come out?
IF thats the case, that is retarded.
Bleh, quote did not work...
DeneziB wrote:
Players never had the ability to call a pet anywhere, anytime. A camp was always required, which still required time in itself to craft.
As for the reasons ... here's a situation I thought of which would make the ability to call a pet anytime anywhere unfair:
"What if I'm out hunting on Dathomir and I see a Jedi leveling up XP on some rancors. He has a TEF, so he cannot attack me until I attack him first. I race up to him on my speeder, jump off quick and then immediately whip out my AT-ST, immediately give it the command to attack to start the engagement. Do you think it is fair for me to surprise a Jedi with a TEF by pulling out a walking turret that can easily pierce through his composite? It isn't."
Having a 30 second timer would prevent this type of unfair gameplay.
There are many more situations like this which will come to light if a 30 second timer is removed. Why can't people see this?
Calling a camp vs. waiting 30 seconds without one ... the time difference is minimal -- from 6 seconds longer of a wait to not even waiting at all.
oh, good grief. I didn't read all 5 pages of posts, so I know I can't be saying anything different than what's already been said.
The 30 sec delay. It's aggavating but not devastating. Though I've wasted a lot of freakin time gaining xp in scout/ranger skills so I could make tents. I want those skill points back!
New mounts. I only need one mount and I don't foresee trading in my brackaset. And hardly anyone buys mounts any more, so here are 2 more for people not to buy. (Though am glad, seriously, for those who wanted the newmounts. At least someone got something they wanted).
Not being able to call pets, etc. during/right after combat orwhile mounted. This is new? What am I missing here? We can't do any of that now.
So, with all the probs CH has, this next great patch is giving us a 30 sec delay most don't want, 2 mounts that most won't use, and restrictions on calling pets that are already in place. *HEAVY SIGH*
DeneziB wrote:
As for the reasons ... here's a situation I thought of which would make the ability to call a pet anytime anywhere unfair:
"What if I'm out hunting on Dathomir and I see a Jedi leveling up XP on some rancors. He has a TEF, so he cannot attack me until I attack him first. I race up to him on my speeder, jump off quick and then immediately whip out my AT-ST, immediately give it the command to attack to start the engagement. Do you think it is fair for me to surprise a Jedi with a TEF by pulling out a walking turret that can easily pierce through his composite? It isn't."
Having a 30 second timer would prevent this type of unfair gameplay.
How does 30 seconds change this. I see the jedi, I call the pet, I wait 25 seconds, move in and do the same thing. The fact is, under the present stupid PvP system, you have no way to know if I'm out sampling DNA or hunting Imps or Rebs. You have no way of knowing if the novice tailor is a TKM or Commando until they attack you. And it's almost impossible to find out anything about a PC unless they're overt.
Come up with a better one.
i didnt take the time to read all the posts so maybe this was said already but i have a question
Does it take 30 seconds everywhere or just when not in a camp or city?
another thing i like the whole thing about the bantha and cu pa why is everybody bit&#ing about it its pretty cool
"What if I'm out hunting on Dathomir and I see a Jedi leveling up XP on some rancors. He has a TEF, so he cannot attack me until I attack him first. I race up to him on my speeder, jump off quick and then immediately whip out my AT-ST, immediately give it the command to attack to start the engagement. Do you think it is fair for me to surprise a Jedi with a TEF by pulling out a walking turret that can easily pierce through his composite? It isn't."
Having a 30 second timer would prevent this type of unfair gameplay.
Yeah, I have to admit I find this a very unconvincing argument. By that logic, it should take 30 seconds for a pistoleer to equip his Krayt FWG ... and NO, I'm not suggesting it should! Either!
All I want is for them, just once, once please, to fix the freaking bugs that are already in the game. Just once. No more freaking publishes that do freaking nothing. Just fix what is already broken before you freaking bring in something else that will break. IS THAT SO FREAKING HARD???
Regrettably, this will never happen. Why? Not because it couldn't be done and not because it takes different resources than they have today.
Why? Because the Marketing Department would never let it happen. The Marketing Department wants glitzy new features that they can talk about in advertising, at trade shows, in interviews with reviewers. They want "Space Expansion" ... "Droid Invasion" ... "Imperial Crackdown" ..... stuff they can make pretty PowerPoint slides of and go "Ooooooooooo" during meetings while they watch it. Stuff they can sell.
Nobody ever made a dime selling a product with the slogan "Not nearly as broken as it used to be!"
So no, as long as Marketing & Sales are running the show (and we know they have been ever since the Beta was so prematurely terminated and this product was shoved out the door kicking, screaming and several months too early), bug fixes will always have the lowest priority. They will fix only as much as they think is necessary to keep you paying a monthly subscription, while they add content as fast as they can to try to sell new box-set CD's at the game store.
Do I think this is a successful long-term strategy? No. I think SOE's reputation as a development organization is being completely trashed by the low quality of the code in this game. Personally, I'll never buy another game produced by this development team, or SOE. Not because they're bad people, but because they obviously work for people who think that Quality is Job 1,000,004.
Message Edited by KzinKiller on 02-20-2004 04:33 PM
Honestly, I don't think being able to call pets, vehicles, mounts, etc. anywhere without the 30 second timer would really have that big an impact on the game. That whole sneak attack on Jedi with an AT-ST example is dubious at best, since Jedi of a certain level, from what I understand, have unlimited burst run or at least enough to leave those big, dopy mechs in the dust.
The main issue I see 'with' the 30 second timer, as mentioned before is the Pet-Autostoring Bug. Imagine running a mission and your pets Auto Store in the middle of combat. So you get yourself a little distance from the enemy, as not to aggro them, and call your pets again. You wait 30 seconds and return, only to discover whatever progress you have made on that mission is lost and you have to start all over again, (ie. Layer Revitalized, Enemies Respawned)
Although this method might be a good way to get XP, if your trying to make some money and your spending anywhere from 30 minutes to an Hour on a 10k mission because of this problem, then you might find yourself a very rich man( that is if frustration beyond the boundaries of sanity could be measured in credits).
We're not talking about calling apet in a metropolitan area. We're talking about calling a pet in the wilderness.
A jedi is out hunting blurrgs on Endor. I see him. I sneak up to him on my swoop. I jump off the swoop 10 meters away from him. I INSTANTANEOUSLY call my AT-ST out and make a first strike against him by commanding my AT-ST to attack. The BENEFIT of having a 30 second timer is that a person cannot sneak up on a jedi like that and kill him.
A TKM is fighting 2 commandos. He's got both of them down to less than 2/3 health. Both have 100 health left. One runs west, another runs east. He can only chase one of them so he chases the one east, while the one headed west fires off a final burn DOT, /peaces, calls out a speeder and runs away, robbing the TKM of a DB, and only turns his speeder around when the TKM's health is down to 1. Then he just fires off one shot from his LP to incap the TKM. The problem is that he is exploiting an internal game mechanic to control a combat situation. If he wanted to run away as a strategy, he should have his vehicle already out. To counter the runaway strategy, the TKM would have to have the opportunity to destroy the getaway car. The BENEFIT of having a 30 second timer is that the second person wouldn't of been able to run away and allow his DOT to eat away at the TKM.
There are quite possibly many, many other permutations of ways that a person could exploit calling a pet, vehicle, droid, anywhere, instantaneously. Most of which will come to light if the opportunity were presented to the game's 300,000 participants.
I dare you to try to rationalize the above situations and try to warp it into some kind of argument that says those are somehow balanced. They are not balanced, and they are not fair.
There are only 8 professions in the game capable of setting up camp to call pets. The BENEFIT of having a 30 second timer with the camp restriction lifted is that 24 OTHER professions can now call pets anytime, anywhere. Do you really want to shut out 24 other professions?
SioBabble wrote:
There is no 30 second timer now, in fact no timer at all if you call out a creature pet, a droid, a faction pet, or a vehicle in a metropolitan area.
What are the benefits you speak of? Specify them. Explain how, with the current situation in metropolitian areas, there is some sort of pressing need for a 30 second delay from time to call to the pet or vehicle materializing in the world. Provide examples.
You are not doing this. You are making assertions with no concrete examples to back them up.
Your arguments are as unconvincing as those of Thunderheart.
This is lame. You're not unintelligent, DeneziB. You can do better than repeat the platitudes of Thunderheart.
DeneziB wrote:
There are only 8 professions in the game capable of setting up camp to call pets. The BENEFIT of having a 30 second timer with the camp restriction lifted is that 24 OTHER professions can now call pets anytime, anywhere. Do you really want to shut out 24 other professions?