You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Imagine a field comprising of a face-up Necrovalley(s) and G.B. Hunter(s) with their effects active, and any Pendulum monster with an effect that includes setting a scale from the GY (including itself); I will use Majespecter Draco - Ryu for this example.
Problem
If Ryu gets destroyed or Tributed, sent to the GY (since it cannot go to the Extra Deck due to G.B. Hunter's effect), and then activates its ② monster effect, Necrovalley currently does not negate that effect, despite Ryu trying to move itself from the GY to a different place, i.e. its owner's Pendulum Zone.
Expected behavior
Necrovalleyshould negate that effect, as well as similar ones, provided that by the time it activates, the Pendulum Monster Card(s) to be placed into a Scale(s) is in the GY.
Suggested solutions
For Pendulum Monster effects which places a Scale(s) from the GY 1st, if not only:
Make sure each Pendulum monster's scale-placement effect script runs the below 2 lines after that effect's target, if it does not already do so (e.g. Performapal Five-Rainbow Magician already places itself into a Scale from the GY):
local c=e:GetHandler()
if c:IsLocation(LOCATION_GRAVE) then Duel.SetOperationInfo(0,CATEGORY_LEAVE_GRAVE,c,1,0,0) end
i.e., in Ryu's case, the whole target function's body should look as follows:
if chk==0 then return Duel.CheckLocation(tp,LOCATION_PZONE,0) or Duel.CheckLocation(tp,LOCATION_PZONE,1) end
local c=e:GetHandler()
if c:IsLocation(LOCATION_GRAVE) then Duel.SetOperationInfo(0,CATEGORY_LEAVE_GRAVE,c,1,0,0) end
Otherwise, stipulate aux.NecroValleyFilter() for the card(s) in question during the effect's operation, e.g. Odd-Eyes Venom Dragon's ② monster effect operation should look like this:
local c=e:GetHandler()
if not c:IsRelateToEffect(e) or Duel.GetLocationCount(tp,LOCATION_MZONE)<1 then return end
Duel.Hint(HINT_SELECTMSG,tp,HINTMSG_SPSUMMON)
local g=Duel.SelectMatchingCard(tp,c45014450.penfilter,tp,LOCATION_PZONE,0,1,1,nil,e,tp)
if g:GetCount()>0 and Duel.SpecialSummon(g,0,tp,tp,false,false,POS_FACEUP)>0 and aux.NecroValleyFilter()(c) then
Context
Imagine a field comprising of a face-up
Necrovalley
(s) andG.B. Hunter
(s) with their effects active, and any Pendulum monster with an effect that includes setting a scale from the GY (including itself); I will useMajespecter Draco - Ryu
for this example.Problem
If Ryu gets destroyed or Tributed, sent to the GY (since it cannot go to the Extra Deck due to
G.B. Hunter
's effect), and then activates its ② monster effect,Necrovalley
currently does not negate that effect, despite Ryu trying to move itself from the GY to a different place, i.e. its owner's Pendulum Zone.Expected behavior
Necrovalley
should negate that effect, as well as similar ones, provided that by the time it activates, the Pendulum Monster Card(s) to be placed into a Scale(s) is in the GY.Suggested solutions
Performapal Five-Rainbow Magician
already places itself into a Scale from the GY):local c=e:GetHandler()
if c:IsLocation(LOCATION_GRAVE) then Duel.SetOperationInfo(0,CATEGORY_LEAVE_GRAVE,c,1,0,0) end
if chk==0 then return Duel.CheckLocation(tp,LOCATION_PZONE,0) or Duel.CheckLocation(tp,LOCATION_PZONE,1) end
local c=e:GetHandler()
if c:IsLocation(LOCATION_GRAVE) then Duel.SetOperationInfo(0,CATEGORY_LEAVE_GRAVE,c,1,0,0) end
aux.NecroValleyFilter()
for the card(s) in question during the effect's operation, e.g.Odd-Eyes Venom Dragon
's ② monster effect operation should look like this:local c=e:GetHandler()
if not c:IsRelateToEffect(e) or Duel.GetLocationCount(tp,LOCATION_MZONE)<1 then return end
Duel.Hint(HINT_SELECTMSG,tp,HINTMSG_SPSUMMON)
local g=Duel.SelectMatchingCard(tp,c45014450.penfilter,tp,LOCATION_PZONE,0,1,1,nil,e,tp)
if g:GetCount()>0 and Duel.SpecialSummon(g,0,tp,tp,false,false,POS_FACEUP)>0 and aux.NecroValleyFilter()(c) then
Duel.MoveToField(c,tp,tp,LOCATION_PZONE,POS_FACEUP,true)
end
The text was updated successfully, but these errors were encountered: