Changes

Jump to navigation Jump to search
→‎Other breaking API changes: + equivalent for NPC.canReceiveThisItemAsGift
Line 8,645: Line 8,645:  
| <samp>NPC</samp>
 
| <samp>NPC</samp>
 
| &#32;
 
| &#32;
* <samp>canReceiveThisItemAsGift(…)</samp>
   
* <samp>idForClones</samp>
 
* <samp>idForClones</samp>
 
|-
 
|-
Line 8,918: Line 8,917:  
Note that the second argument (<samp>name</samp>) should usually be omitted, since it'll be auto-populated from the value passed to the first argument.
 
Note that the second argument (<samp>name</samp>) should usually be omitted, since it'll be auto-populated from the value passed to the first argument.
 
|-
 
|-
|rowspan="5"| <samp>NPC</samp>
+
|rowspan="6"| <samp>NPC</samp>
 +
| <samp>canReceiveThisItemAsGift(…)</samp>
 +
| Removed. The closest equivalent is <code>item.canBeGivenAsGift()</code>, or you can check if the NPC will accept the player's held object (as a gift or otherwise) using <code>npc.tryReceiveActiveObject(Game1.player, probe: true)</code>.
 +
|-
 
| <samp>Gender</samp><br /><samp>female</samp><br /><samp>male</samp><br /><samp>undefined</samp>
 
| <samp>Gender</samp><br /><samp>female</samp><br /><samp>male</samp><br /><samp>undefined</samp>
 
| The <samp>Gender</samp> field now uses a <samp>Gender</samp> enum instead of numeric constants. For example, <code>npc.Gender == NPC.female</code> becomes <code>npc.Gender == Gender.Female</code> in 1.6.
 
| The <samp>Gender</samp> field now uses a <samp>Gender</samp> enum instead of numeric constants. For example, <code>npc.Gender == NPC.female</code> becomes <code>npc.Gender == Gender.Female</code> in 1.6.
translators
8,446

edits

Navigation menu