Skip to content

Bug in 1.3/request for 2.0: opcode 181 (EDIT - not actually a bug, please ignore)

[Deleted User][Deleted User] Posts: 0
edited March 2016 in The Road to v2.0
The user and all related content has been deleted.
Post edited by [Deleted User] on

Comments

  • Avenger_teambgAvenger_teambg Member, Developer Posts: 5,862
    Param2 = 0 can't equip
    Param2 = 1 can't use

    special = string to be printed when unusable
  • The user and all related content has been deleted.
  • PeccaPecca Member Posts: 2,178
    edited March 2016
    Param2 - "can't equip" prevents scrolls from being put into quick item slots but not from scribing. Param2 - "can't use" doesn't seem to do anything. Question is, what is the intended behavior of "can't use" parameter.
  • The user and all related content has been deleted.
  • [Deleted User][Deleted User] Posts: 0
    edited March 2016
    The user and all related content has been deleted.
  • PeccaPecca Member Posts: 2,178
    @subtledoctor: param=0 works for me (in both 1.3 and 2.0). The spell you attached here uses param=1.
  • The user and all related content has been deleted.
  • SethDavisSethDavis Member Posts: 1,812
    you mean I might not have to get back into 2013 Seth's brain? *crosses fingers*
  • The user and all related content has been deleted.
  • Avenger_teambgAvenger_teambg Member, Developer Posts: 5,862
    edited March 2016
    Pecca said:

    Param2 - "can't equip" prevents scrolls from being put into quick item slots but not from scribing. Param2 - "can't use" doesn't seem to do anything. Question is, what is the intended behavior of "can't use" parameter.

    You can say, that the can't use part is a bug. But we don't use this feature in the official campaign. It could be reported as a bug, but it might be considered low priority by our QA/managers.

    But hey, this is still better than vanilla :D
  • The user and all related content has been deleted.
Sign In or Register to comment.