berelinde Posted July 15, 2010 Share Posted July 15, 2010 You should be able to use ConTEXT. Many modders do. Make sure you have "smart quotes" turned off. Link to comment
baldur46233 Posted July 15, 2010 Author Share Posted July 15, 2010 You should be able to use ConTEXT. Many modders do. Make sure you have "smart quotes" turned off. Erm, where would I find the "smart quotes"? Also, I don't know how to not make my coding 'slanted'. Link to comment
berelinde Posted July 15, 2010 Share Posted July 15, 2010 Hopefully, someone who does use ConTEXT can stop by and help you out. I've never used it, so I don't know how to set up the preferences. Link to comment
baldur46233 Posted July 15, 2010 Author Share Posted July 15, 2010 Hopefully, someone who does use ConTEXT can stop by and help you out. I've never used it, so I don't know how to set up the preferences. Is that the only problem on my banter file? The slanted coding and smart quotes? Can I also have your opinion on which text editor is better? Link to comment
berelinde Posted July 15, 2010 Share Posted July 15, 2010 I haven't seen your whole banter file, so I couldn't tell you. And I've only ever used Crimson Editor, so I have no basis for comparison. Sorry. Link to comment
baldur46233 Posted July 15, 2010 Author Share Posted July 15, 2010 I haven't seen your whole banter file, so I couldn't tell you. And I've only ever used Crimson Editor, so I have no basis for comparison. Sorry. I've only created this one banter and thanks for your help anyway. Link to comment
Ipsy Posted July 15, 2010 Share Posted July 15, 2010 I'm using ConText with the WeiDU highlighters That should be fine, no? I use the same, and it works fine for me Plus it helps me catch stupid typos like CHAN instead of CHAIN. IF ~InParty(Myself)~InParty(“Minscâ€) !StateCheck("Minsc",CD_STATE_NOTVALID) !StateCheck(Myself,CD_STATE_NOTVALID) CombatCounter(0) !See([ENEMY]) Global(“M#DracoMinscâ€,â€GLOBALâ€,0)~ Now you've got an extra tilde on the first line. As I said--tildes always come in pairs. Link to comment
baldur46233 Posted July 15, 2010 Author Share Posted July 15, 2010 I'm using ConText with the WeiDU highlighters That should be fine, no? I use the same, and it works fine for me Plus it helps me catch stupid typos like CHAN instead of CHAIN. IF ~InParty(Myself)~InParty(“Minscâ€) !StateCheck("Minsc",CD_STATE_NOTVALID) !StateCheck(Myself,CD_STATE_NOTVALID) CombatCounter(0) !See([ENEMY]) Global(“M#DracoMinscâ€,â€GLOBALâ€,0)~ Now you've got an extra tilde on the first line. As I said--tildes always come in pairs. BEGIN ~M#DraB~ CHAIN IF ~~InParty(Myself) InParty(“Minscâ€) !StateCheck("Minsc",CD_STATE_NOTVALID) !StateCheck(Myself,CD_STATE_NOTVALID) CombatCounter(0) !See([ENEMY]) Global(“M#DracoMinscâ€,â€GLOBALâ€,0)~ THEN ~M#DraB~ DracoMinsc1 Is it supposed to be like this? Link to comment
cmorgan Posted July 15, 2010 Share Posted July 15, 2010 nope... Ispy pointed it out... IF ~~In Only needs one tilde! Link to comment
baldur46233 Posted July 15, 2010 Author Share Posted July 15, 2010 nope... Ispy pointed it out... IF ~~In Only needs one tilde! Gaah, I make such stupid mistakes, but I thought they had to be in pairs? So, is this better? IF ~InParty(Myself) Link to comment
berelinde Posted July 15, 2010 Share Posted July 15, 2010 Yes, that looks right. "Pairs" here means pairs per coding "phrase." IF ~triggers~ THEN BEGIN state SAY ~string~ IF ~triggers~ THEN DO ~actions~ TRANSITION END ~triggers~, ~string~, and ~actions~ are all coding "prhases." Link to comment
baldur46233 Posted July 15, 2010 Author Share Posted July 15, 2010 Yes, that looks right. "Pairs" here means pairs per coding "phrase." IF ~triggers~ THEN BEGIN state SAY ~string~ IF ~triggers~ THEN DO ~actions~ TRANSITION END ~triggers~, ~string~, and ~actions~ are all coding "prhases." Oh, that makes sense now. Thank you. I've run into yet another problem though...*sigh* It says: WARNING: cannot verify trigger ~InParty(Myself) InParty(“Minscâ€) !StateCheck("Minsc",CD_STATE_NOTVALID) !StateCheck(Myself,CD_STATE_NOTVALID) CombatCounter(0) !See([ENEMY]) Global(“M#DracoMinscâ€,â€GLOBALâ€,0)~: Failure("lexing: empty token") It installs, but again, it says with warnings. Link to comment
berelinde Posted July 15, 2010 Share Posted July 15, 2010 You still have slanted quotes in InParty("Minsc") and in the Global() trigger. Link to comment
baldur46233 Posted July 15, 2010 Author Share Posted July 15, 2010 You still have slanted quotes in InParty("Minsc") and in the Global() trigger. Oh okay, I shall fix that then. It worked!!! But now I have new problem... [trigger list near line 11, column 5 of Draco/M#DraB.d] PARSE WARNING at line 13 column 1-38 Near Text: ) [stateCheck] argument [CD_STATE_NOTVALID] not found in [state.IDS] [trigger list near line 11, column 5 of Draco/M#DraB.d] PARSE WARNING at line 14 column 1-37 Near Text: ) [stateCheck] argument [CD_STATE_NOTVALID] not found in [state.IDS] And I do have this on my Tp2: APPEND ~STATE.IDS~ ~0x80101FEF CD_STATE_NOTVALID~ UNLESS ~CD_STATE_NOTVALID~ I'm just prone to problems and mistakes it seems. Link to comment
cmorgan Posted July 16, 2010 Share Posted July 16, 2010 Check to make sure that line is *above* the dialog compile line... that can have an effect Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.