I think it is quite surprising that anybody would want a removal of a feature, but "innovations" often come surprisingly.
From my opinion, --automate should not be restricted to strings above 27000, because if you take a look at the strings below, you will find that there are many strings which are not for bg1 but for bg2. So automate-min is useless. When starting out my own bg1in2, i thought that most strings with StrrefNr < 27001 were bg1, but i was wrong.
BTW., when reviewing --automate, couldn't the implementation of the automate for creature-sounds be brought back on the agenda? I know it is in the ToDo, but for quite some time now.
Though i seem to want the removal of a feature, it is just a removal of a restriction of a feature.
automate-min
Started by WelloBanir, May 09 2003 07:32 AM
2 replies to this topic
#2
-jcompton-
-jcompton-
-
- Guest
Posted 09 May 2003 - 08:28 AM
I don't understand. Can't you simply define a different value for automate-min, or not use it at all?
#3
weimer
-
- Member
- 1569 posts
Posted 09 May 2003 - 02:59 PM
Fine, I have added CRE sounds to automate.
Just specify --automate-min 0 if you don't want to use it. I can't remove it general.
Just specify --automate-min 0 if you don't want to use it. I can't remove it general.
