Jump to content

Invalid_Integral

Members
  • Posts

    23
  • Joined

Everything posted by Invalid_Integral

  1. Has there been any progress on discovering whether Rakata items (belt, bracers, etc) can be reverse engineered for upgraded schematics? Usually if an item can't be reverse engineered you'll get the proc anyway but just get an error saying that no reverse engienering info could be found. Personally, I've RE'ed in total about 20 rakata bracers and belts and never gotten an upgraded schematic OR an error message. But i did finally crit the belt. I'm still going to keep trying on the bracers until I get the crit, but if someone knows for sure about the the RE then I may go back and make even more belts so I can upgrade it.
  2. Can you say anything about if and when voluntary server transfers will open up for those of us who are on servers with dwindling populations who would like to move somewhere else?
  3. Personally I like the idea of a clock-like cooldown indicator. It's hard to describe, but imagine that an ability on cooldown starts with a complete white tint covering the entire icon. Then imagine you take a clock needle at 12AM and slowly sweep it around clockwise, and as it sweeps the area it covers loses the white tint. Another issue I have is that abilities are clickable / pressable even while on cooldown, and it still flashes and looks like I pressed it. If an ability is on cooldown, the button should feel like it's disabled. Pressing it should do nothing. Furthermore, there's been certain times (pretty frequently actually) that I press the button when the ability is CLEARLY on cooldown, and it waits until after the cooldown is over and then fires the ability. This should not happen.
  4. When else would you expect them to ask you? Before you had ever seen it? It was on the PTR, but I'm sure you didn't test it out there did you?
  5. These choices are not very useful because it doesn't give you any insight on what peoples' specific problems are.
  6. 1) Bind any quickslot button to a mouse button (Mouse Button 4, Wheel Down, etc) 2) Press the assigned mouse button and verify that the ability fires as expected 3) Move your mouse so the cursor is pointing on top of the quickslot bar itself 4) Press the same mouse button from step 2 and note that the ability does not fire. Mouse bindings do not work if the mouse is hovering over a quickslot bar It is also not at all clear to people that this is what's happening, but I know that for at least 3 people I've talked to, this has fixed some of their biggest complaints with what they're calling "ability delay" (basically, keep spamming the key bind and absolutely nothing happens). This sounds like it should be a simple fix, and would impact everyone regardless of machine configuration, hardware setup, etc.
  7. Ahh yea. That's not quite the same because your base item was blue. I'm actually wondering if it's possible to take a Purple base item, RE it and get another purple item but with upgraded stats. For example, take a look at this item. The original recipe you purchase from the trainer is purple. Torhead suggests there are improved purple versions of it. So that's what I'm looking for firsthand confirmation of.
  8. Thanks, that answers my question. BTW I can't find that item on torhead, can you link it? (base item is fine)
  9. I read the OP but admittedly did not read all 100 pages of the thread. Have there been any reports of someone reverse engineering an Artifact base item and having it get a prefix with it? Of course we aren't talking about moving to a Legendary quality item here, but just getting a Tier 1 (Redoubt, Critical, Overkill) prefix from an item whose initial recipe learned from the crafting trainer was already purple? Torhead suggests that it's possible to upgrade it even into the tier 2 prefixes. http://www.torhead.com/item/3g2RUSm/rakata-combat-medics-belt
  10. This is one of those things I was hoping would be fixed after the ability delay patch. This affects everybody who binds their quickbar slots to mouse buttons. The bug is this: If you bind any of your quickslot actions to mouse buttons (wheel up, wheel down, Mouse Button 3, Mouse Button 4, etc) AND your mouse is currently positioned so that it is hovering over your quickslot bar, then you cannot fire your abilities by pressing the corresponding mouse button. You can verify this easily by going through the following repro steps: 1. Assign Quickslot 1 to Wheel Down. 2. Place your mouse cursor in the middle of the screen and move your wheel down, and notice the ability gets fired. 3. Place your mouse cursor on top of the quickslot bar but do not click any of the buttons. 4. While holding your mouse at this location, move the wheel down and notice the ability does not fire. 5. Move the mouse back to another location (away from the quickslot bar) and move the wheel down again, and notice the ability gets fired. Because of the massive number of abilities present in SWTOR and the fact that I have a limited number of fingers / easily reachable keys on my keyboard, I often play like this: 1. Plan out an ability rotation that will span the next 0-30 seconds. 2. For those abilities which can be triggered with keyboard presses of keys that are very close together and I can move quickly from one key to the next, I use the key bindings. 3. At some point in the sequence, there will be an awkward key transition (e.g. going from pressing 1 to pressing Shift+7 or something). Since I've planned out my rotation in advance, I move the mouse cursor over the corresponding quickslot button in advance, so that when it is time to execute this action I can left click it immediately to fire the action. 4. After this happens, I cannot then immediately execute other actions via my mouse bindings, since my mouse will naturally be hovering over the quickslot. Note that keyboard bindings are not affected by this bug, only mouse bindings. The obvious workaround for this is to move your mouse. However, I wanted to let people know about the cause of this annoying bug, as I know I can't possibly be the only one affected by it. FWIW, I've already filed a /bug over this, and hopefully it will get fixed soon.
×
×
  • Create New...