Solved 1.7.2 - playEffect() deprecated?

Discussion in 'Plugin Development' started by ArthurMaker, Dec 3, 2013.

Thread Status:
Not open for further replies.
  1. Offline

    ArthurMaker

    Whaat?
    [​IMG]
    What can I use it now? :s
     
  2. Offline

    ZachBora

    Look at the javadocs and if they don't say a replacement it means you can still use it.
     
  3. The replacement to that method is to use a particuler object assosated with the effect. In case of smoke you should pass a blockface to the last param
     
  4. Offline

    ArthurMaker


    Interesting, but and the MOBSPAWNER_FLAMES and, for example, EXTINGUISH effects? What can I put in this "T"?

    ZachBora
    I saw it. But there is no information about it.
     
  5. Offline

    sgavster

    ArthurMaker I think it's because you need
    player.getWorld().playEffect(...); :)
     
  6. Offline

    ArthurMaker


    No, it gives me the same error. And I want to send it just for the player, that is why I'm using just player.playEffect().
     
  7. Offline

    sgavster

    ArthurMaker ohh. I think it gave me deprication for the player.playEffect(..) on 1.6.4
     
  8. Offline

    ArthurMaker

    This is weird, because I used to use it perfectly on 1.6.4...
     
  9. Offline

    L33m4n123

    http://jd.bukkit.org/dev/apidocs/
    and
    http://jd.bukkit.org/rb/apidocs/
    so yea. it was already deprecated in 1.6.4 ;)
     
    sgavster likes this.
  10. Offline

    sgavster

    ArthurMaker Why don't you just suppresswarning until you find a better way?
     
  11. Offline

    AoH_Ruthless

    ArthurMaker
    I don't think there is a replacement. As sgavster said, you will have to make do with with what there is.
     
  12. Offline

    1Rogue


    Because suppressing warnings is an awful idea for almost any code implementations and leads to mistakes and issues down the line.

    Rather than cover up code issues, you should either be aware that they need to be replaced or replace them with some kind of newer form.
     
  13. Offline

    ArthurMaker

    Hm, okay so...
    Thank you guys!
     
Thread Status:
Not open for further replies.

Share This Page