48 replies to this topic

[the bigg]

Use the Linux version of weidu instead: http://www.weidu.org/~thebigg/weidu ; instructions are available from any other mod available on Linux.

[Leomar]

The author of those files deserves a slow, painful death for using spaces or special characters in file names.

Yepp, we will report that to the modauthors.

I've uploaded a new version. Can you test that (no modded game available ATM).

Thank you very much, we will test it, too.

Greetings Leomar

[the bigg]

First - there's a typo in the IF block for moving files from prod back to override, where one of the backslashes is reversed (and because the windows FOR command requires the TP2 to use the EXACT keyword, it breaks).

Switched both to \s (although it works either way in XP).

That part was easily fixed, but apparently WeiDU 21100 doesn't parse %COMPONENT_NUMBER% in arguments to AT_UNINSTALL, so it passes it straight to the OS, which predictably doesn't handle it properly and doesn't move the files out, leading to unpredictable but probably ugly consequences for installs and uninstalls beneath it in the stack (I didn't check, because since I .

Fixed.

I wonder how it happens that over 8000 people downloaded this and nobody ever noticed.

[the bigg]

Was said before already. For now, you can replace %COMPONENT_NUMBER% with 0 in the tp2 anytime before executing uninstall (it should work even if you do the change after installing Gen Biff but before uninstalling it).

[the bigg]

sed -es/COPY_EXISTING/COPY/g -i generalized_biffing/generalized_biffing.tp2

I really should update the package with that fix...

[the bigg]

Updated. Meaningful only to Linux users who couldn't install because of the problem above.

[pacek]

The Bigg,
I have a recurring problem, namely creatures with certain scripts (so far have identified SCS2's DW#Range script) do not function. See posts:
http://forums.gibber...ndpost&p=182728
http://www.shsforums...post__p__509191
So I thought the problem had gone on my last install but it's reared its ugly head again. Where you come in is that I uninstalled generalised biffing and voila! Fixed! Any ideas?

Attached Files

•  Weidu.log   30.89K   168 downloads

[the bigg]

I've played multiple games with both scs(ii) and gen_biff without the problems you described, so something else is the ultimate cause. I don't have the time, willingness or means to figure exactly what mod is the culprit.

[pacek]

I've played multiple games with both scs(ii) and gen_biff without the problems you described, so something else is the ultimate cause. I don't have the time, willingness or means to figure exactly what mod is the culprit.

What can I say? Please consider the case of JELGRA.CRE: Mods affecting it are Fixpack and SC2. The only script it has is DW#RANGE from SCS2. Everything functions like it says on the box until I install GenBiff. Now all creatures with DW#RANGE are totally useless. I really don't mind if you don't want to deal with this: I'm not seeking the solution so much as reporting a problem. Its just I seem to have exhausted all other possibilities, and the only solution I have right now is "Don't install GenBiff".

[Miloch]

Very odd. I can reproduce the hostile grey ooze doing nothing on a similar install (BWP with SCS2 and GenBiff installed - though the creature is jelgra01.cre).

[pacek]

Very odd. I can reproduce the hostile grey ooze doing nothing on a similar install (BWP with SCS2 and GenBiff installed - though the creature is jelgra01.cre).

Apologies, its Jelgra01.cre here too.

[DavidWallace]

Miloch/Pacek: is there any other bcs file in the override (before biffing) whose first 8 letters are "dw#range"? I recall Pacek accidentally sent me "dw#ranged.bcs" a couple of weeks ago, which I wondered about at the time...

[Miloch]

Indeed, there is a dw#ranged.bcs file in the override (an invalid name both for the engine and for biffing, being > 8 chars). Would that not explain it?

(Quite a few other such files that seem unnecessary to "transport" to the override e.g. dw#random.bcs, dw#purple.bcs, etc.)

[the bigg]

Currently gen_biff only biffs files whose names fall under 8.{biffable extension} and completely ignores the rest. Any suggestions on how I should handle these broken files?

Edited by the bigg, 14 March 2011 - 01:26 AM.

[Miloch]

Any suggestions on how I should handle these broken files?

Delete them? Actually I would be interested to hear why DavidW is pushing these files to the game (on top of that to be >8 char filenames which couldn't possibly be interpreted). I'm not trying to be an arse here (seriously), just trying to understand why we end up with compiled scripts that don't actually get interpreted.

I know both of you lads have derided my raised eyebrow at cluttering up the override folder, but I was never off on that to prove a point (aside from being 'why'?). In this case, there are a bunch of dw#123456.bcs scripts that will never get compiled either by the engine or by GenBiff. I have to ask why they are there.