Randomly can't target with shift+click.

[omega-red]

Since i updated the game def.

[brine]

is that the only thing that's not working, or are there others? When you say randomly, does it mean it only works some of the time, or at some point it stops working and won't work again until you restart OCTGN?

[Gadget2020]

I get that too - and it does seem random, only one card. You can sometimes move the card to the exile zone or your hand and then back to the table and it clears so you can [shift]-click again. If it happens, no-one can target the card - even passing control won't fix it. Most of the time you can swap target and attachment - it works, but that puts the attachment above the intended target.

I don't know if it's fixed in V3.0.10/11, but there was a glitch where if an opponent attached a card to one of yours and you then played a card that shifted the target, the attachment would remain glued to the table (rather than move with the card)

[drilus]

This is an mtg problem. Not something to do with octgn itself. The problem stems from attaching cards to one another. If you move a creature to the graveyard while being attached it screws up targeting. Brine might have more insight, but best thing to do is make sure everyone is running the same version of MTG.

[brine]

Yeah but the actual act of targeting a card through shift clicking is done internally through OCTGN, I have no control of it and it isn't part of the python API.

[drilus]

The actual function is, but it still relies and data being sent to it. I suspect something happens to the cardID during attachment.

I'll see if I can replicate this to happen every time. At current I believe it's only during online play with friends.

[db0]

I've seen this happen in Android:Netrunner as well. At some random point, a card wouldn't be targeted anymore.

[brine]

are they specific cards? Is it specific to the individual game, or is it consistent across multiple hostings?

[db0]

I've only seen it once. OTOH, I've seen something just as weird (db0/Android-Netrunner-OCTGN#48) happen more consistently, and I'm trying to figure out if maybe that's related.

[brine]

I just noticed, if you try shift-clicking a card to target it, but your mouse is hovering over top of a marker/counter (either the icon or the number beside it), it won't register the target. You actually have to have your mouse hovering over an empty part of the card.

[db0]

Actually, now that you mention it, I remember that this was the issue for me as well. I did in the end manage to target the card by zooming-in and shift-clicking on the edge of the card to avoid the markers. I had forgotten that.

[kellyelton]

need to find a way to consistanly reproduce this

[brine]

I'm preeeetty sure it was due to the user trying to target over top of a marker icon

[kellyelton]

Interesting, I'd have to look into the targeting code to see how I'd go about fixing that.

[drilus]

I don't think this is related to a marker icon.

[brine]

its easy to test, if you stick a card on the table and put a marker on it, try shift-clicking over the marker to target it. As long as your mouse is pointed over the marker image or the text showing the quantity, it won't target

[drilus]

This bug happened to me with cards that had no markers.

Still, I haven't seen this issue for a while.

[db0]

I see it now and then. It's rare but it happens

[db0]

Here's an example of it happening: Check 43:25

[bringerofdoom]

This is and has been a relatively common problem for me too. I have also witnessed several other players having the same issue. This problem has transcended many updates and it is still around in the new version. As random as ever and it is indeed not the same problem as the one with clicking on counters/markers. For example I could have two indentical basic lands in a stack and I could target one, but not the other. I have no idea what the logic behind this could be. I have once witnessed an opposing player doing some kind of seemingly random exiling shenanigans and it seemed to fix it. I have tried various ways of moving the card around myself, but have not had any success making it targetable.

[brine]

i wonder if theres something in the logs that could explain the cause

[Capitoste]

This happens and has been happening almost in every MTG I played, either to me or to my opponent. It is a "random" bug, since it is not card related (it can happen to every permanent), and a particular card that has the problem may work perfectly the next game you play with it. The only workaround is creating a clone card of the original permanent. The cloned cards always will accept shift+click on them.

[BenMatteson]

hmm, I think this probably got fixed with the ghost cards issue. I'm closing this unless somebody's noticed it recently.

[cameris]

It still occurs sometimes.

[BenMatteson]

darn... ok, I think I might still know what's doing it at least.

[BenMatteson]

hmm... and your sure it's not that you're clicking on some marker that's on the card when this happens? because I can't get it to act up the way I thought I would... if you can come up with some sequence of actions that makes it happen that would be ideal.

[cameris]

No markers and I have no idea why it happens or howto reproduce it. it's like one in 20 games. Sry, that I can't be of more help.

[kellyelton]

Is this still happening?

[Capitoste]

In my experience, yes. From time to time some random cards become untargeteable with no particular reason, , and you are forced to clone it (the clone is targeteable) BlackBerry de movistar, allí donde estés está tu oficin@

-----Original Message----- From: Kelly Elton notifications@github.com Date: Wed, 20 Aug 2014 09:15:52 To: kellyelton/OCTGNOCTGN@noreply.github.com Reply-To: kellyelton/OCTGN reply@reply.github.com Cc: Capitostepirindolo@msn.com Subject: Re: [OCTGN] Randomly can't target with shift+click. (#568)

Is this still happening?

---

Reply to this email directly or view it on GitHub: https://github.com/kellyelton/OCTGN/issues/568#issuecomment-52801868

[PranjalBishtNX]

Yeah, this still happens.

[szefo09]

Reproduction steps:

• Place 2 cards on the field.
• Target card nr2 with card nr1
• delete card nr2

Card nr1 should be untargetable now, because it has flag TargetsOtherCards still set to True.