Idobek Posted April 28, 2005 Share Posted April 28, 2005 As you would expect, opcode #309 (Script: Set/Modify Local Variable) appears to work the same as opcode (#265 Script: Modify Global Variable) does but for local variables. However, there is one major difference: #309 will also set a global variable with the same name as the local one. There are stacks of typos in the descriptions for these, by the way. Link to comment
igi Posted June 25, 2005 Share Posted June 25, 2005 Noted thanks. There are stacks of typos in the descriptions for these, by the way. Link to comment
Avenger Posted June 25, 2005 Share Posted June 25, 2005 Are you sure about this? This seems plain wrong. Link to comment
igi Posted June 25, 2005 Share Posted June 25, 2005 I checked it today, before updating my local BG2 .dat file - it works as idobek describes, setting both the local and the global. Link to comment
SimDing0 Posted June 25, 2005 Share Posted June 25, 2005 Yeh, I'm fairly sure I remember Max mentioning this once before. Pass on precisely why they decided it was a good idea. Link to comment
hlidskialf Posted June 26, 2005 Share Posted June 26, 2005 I can confirm. I had this cause me a serious bit of confusion while testing some scripts at one point. I eventually had to change the name of the global I used because of it. (Would've been cleaner to have them the same. Cryin' shame really.) Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.