Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:

Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What color is grass?:
What is the seventh word in this sentence?:
What is five minus two (use the full word)?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: the bigg
« on: March 27, 2007, 04:29:59 PM »

I reproduced it, but yes, that one was what made me say "it is time to rewrite and/or refactor heavily WeiDU", since currently fixing bugs in the TP menu/ordering stuff is a nightmare.
Posted by: Anomaly
« on: March 27, 2007, 04:27:36 PM »

Uninstalling components seems to have issues.
[snipped]
I don't see this on the WeiDU 199 changelog. :( Does that means that you were not able to reproduce the problem, or do you prefer to wait for your major rewrite for v200 ?
Posted by: the bigg
« on: March 22, 2007, 03:25:32 PM »

Would utilities like Dos `fc' or Unix `diff' suffice to you, or you prefer to add them in WeiDU (which'd happen for 200 anyway)?
Posted by: CamDawg
« on: March 22, 2007, 12:53:32 PM »

Here's something I've been meaning to request for ages and keep forgetting. Using WeiDU's command line compare, if the files are different sizes then it will simply report the size difference. I think it'd be more useful to compare to the EOF for the smaller file and also report the size difference. For, say, an item file, the first 0x72 bytes of compare will still let me see if the size difference is due to more abilities or effects.
Posted by: cmorgan
« on: March 04, 2007, 09:22:07 AM »

Anomaly, the reference link for the reported (and fixed) problem  is
http://forums.pocketplane.net/index.php/topic,23208.msg294835.html#msg294835
Posted by: the bigg
« on: March 04, 2007, 09:17:02 AM »

I also wonder why, in all cases, if I remove on component from a mod, all the components after this one, but from the same mod, are marked as "Recently uninstalled", but not the components from the other mods installed after it. I hope this is not another issue with uninstalling, because this is a new behavior. Older WeiDU versions marked the uninstalled component as "Recently Uninstalled", and only this one.
Older WeiDU behaviour caused problems with something, or something else, so I had to change this to the new 'everything is Recently uninstalled' behaviour (cmorgan was the one who reported the problem).

Since the only machine I have with BG2 is being repaired, I'll have to delay testing & working around your own personal bug with uninstalling, sorry.
(of course, as of now the best solution would be to significantly rewrite from scratch large portions of all the TP type definition, action/patch executer and installer mammoth, but that'd be overkill in quantity of new bugs created).
Posted by: Anomaly
« on: March 04, 2007, 08:53:49 AM »

Uninstalling components seems to have issues.

I made a sample mod with 4 components. I installed all four, then I uninstalled the first one, then Q[uitted], since I only wanted to uninstall the first component.

This is what I got :

Quote
// Recently Uninstalled: ~TEST/TEST.TP2~ #0 #0 // Component I
// Recently Uninstalled: ~TEST/TEST.TP2~ #0 #2 // Component III
// Recently Uninstalled: ~TEST/TEST.TP2~ #0 #3 // Component IV
~TEST/TEST.TP2~ #0 #2 // Component III
~TEST/TEST.TP2~ #0 #3 // Component IV
~TEST/TEST.TP2~ #0 #1 // Component II

So the component II is not marked as uninstalled, is reinstalled anyway, but at the wrong time.

Please note that this happens only when one uses the Q[uit] function. If I don't use the Q[uit], this is what I get :

Quote
// Recently Uninstalled: ~TEST/TEST.TP2~ #0 #0 // Component I
// Recently Uninstalled: ~TEST/TEST.TP2~ #0 #1 // Component II
// Recently Uninstalled: ~TEST/TEST.TP2~ #0 #2 // Component III
// Recently Uninstalled: ~TEST/TEST.TP2~ #0 #3 // Component IV
~TEST/TEST.TP2~ #0 #1 // Component II
~TEST/TEST.TP2~ #0 #2 // Component III
~TEST/TEST.TP2~ #0 #3 // Component IV

I also wonder why, in all cases, if I remove on component from a mod, all the components after this one, but from the same mod, are marked as "Recently uninstalled", but not the components from the other mods installed after it. I hope this is not another issue with uninstalling, because this is a new behavior. Older WeiDU versions marked the uninstalled component as "Recently Uninstalled", and only this one.
Posted by: cmorgan
« on: February 28, 2007, 09:09:23 PM »

I was making a joke about "I resent that!" by using the "slip of the tounge" or "accidental" slip "I resemble that!". So the joke is that the person is trying to say "Hey, that is calling me something!" with "Hey, I *am* that!"

It may not translate well, sorry... I keep forgetting that we are all different native language speakers. :)
Posted by: the bigg
« on: February 28, 2007, 05:15:15 PM »

oi, I resemble that remark  ;D
In the sense that you are in the 99% or in the sense that you are in the 1%?
(Sorry, ESL here  :P )
Posted by: cmorgan
« on: February 28, 2007, 04:26:00 PM »

oi, I resemble that remark  ;D
Posted by: the bigg
« on: February 28, 2007, 11:33:42 AM »

If the MODDER flag caused WeiDU to ignore all VIEW calls, I'd be pretty stoked. :)
MODDER only works for the current tp2  ;) . You can use --skip-at-view, but since you use Windows and double-clicking I guess I can add that behaviour to MODDER too.
(and perhaps also add a --modder CLI option).
Keep in mind that 99% of modders are idiots and use NOTEPAD something from the bat files, which means that this won't work (luckily, AT_* ~NOTEPAD foo~ & variants now falls back to AT_* ~VIEW foo~).
Posted by: CamDawg
« on: February 28, 2007, 10:43:14 AM »

If the MODDER flag caused WeiDU to ignore all VIEW calls, I'd be pretty stoked. :)
Posted by: Nythrun@work
« on: February 25, 2007, 03:22:30 AM »

INNER_PATCH_SAVE is a patch, not an action: you're wanting OUTER_\(INNER\)?_PATCH_SAVE there.

Bigg: Thanks, that looks great. I'll switch over to INNER_ACTION -> COPY_EXISTING - and lose the INNER_PATCHes :)
Posted by: pro5
« on: February 25, 2007, 03:11:11 AM »

Looks like some weirdness in INNER_PATCH_SAVE parsing?

Non-parsing example:
Quote
ADD_SPELL ~Mymod/SPL/P5SPW401.SPL~ ~2~ ~4~ ~WIZARD_CHOKING_CLOUD~
    SAY 0x50 @179
    SAY 0x54 @180
    SAY 0x1be @181

  OUTER_SPRINT ~temp~ ~%WIZARD_CHOKING_CLOUD%~ 

  INNER_PATCH_SAVE ~temp2~ ~%temp%~ BEGIN
    DELETE_BYTES 0x00 1
  END
 
  PRINT ~temp2 = %temp2%~

Parsing example:
Quote
ADD_SPELL ~Mymod/SPL/P5SPW401.SPL~ ~2~ ~4~ ~WIZARD_CHOKING_CLOUD~
    SAY 0x50 @179
    SAY 0x54 @180
    SAY 0x1be @181

  OUTER_SPRINT ~temp~ ~%WIZARD_CHOKING_CLOUD%~ 
  COPY + ~Keymap.ini~ ~Keymap.ini~  // meaningless, but removes the parse error

  INNER_PATCH_SAVE ~temp2~ ~%temp%~ BEGIN
    DELETE_BYTES 0x00 1
  END
 
  PRINT ~temp2 = %temp2%~
Posted by: berelinde
« on: February 24, 2007, 10:21:47 AM »

First rule of modding: you're never done.

You could also think of it as an opportunity to make sure all the InMyArea("NPC") checks are there.