What's the merit in this rule? You face the potential for exactly the same problem in DECORATE. All it would take is one conflicting actor name.The rules wrote:No extra ACS allowed! Compiled global ACS could conflict with ACS in another person's mod.
We were going to change that as soon as we can finally work out the limits, so we don't end up with a monster MADE of ACS that a friend of mine has been threatening to make.solarsnowfall wrote:If the reason for this rule is to make it easier for you to compile a resource, then perhaps you should make contributors declare script numbers they use. Presumably you'll make them change any conflicting DECORATE actors. Surely asking the same for ACS scripts would not be out of line
Loosely speaking, anything that couldn't be done in DECORATE or that could be done better in ACS. Or, anything that I would like to have sophisticated control over independent of an actor's state loops. I like to take advantage of the trigonometric and positioning functions because it grants me a high degree of control over things int he 3d game-space. The whole purpose of ACS was to bring special effects into the old Doom engine.Ghastly_dragon wrote:Out of curiosity, why would you need ACS for it, also?
Considering this is a special effects contest, no it wouldn't.solarsnowfall wrote:I've got an old boss monster project that's been collecting dust, but I'm not certain it's something that would be of interest to this project. It uses a couple of maintenance scripts to perform special effects and complicated attacks.
The ACS rule for monsters was already modified. Then it seems to me that you've got a very limiting and silly concept of what special effects can be.NeuralStunner wrote:Considering this is a special effects contest, no it wouldn't.
From the two lists of rules I don't see one that pertains to both monsters and ACS use. Is it this rule?NeuralStunner wrote:The ACS rule for monsters was already modified.
Because it's not at all clear that this rule would preclude the project I described. Regardless of what the rules say, I'm disputing them.* While as per the rules, the effects have to be coded in Decorate, alternate behavior in your effect that is activated through ACS, such as states used with SetActorState or dependance on Thing_Activate in encouraged, for customizability. If you include things like this, SHOW IT IN THE TEST MAP.
No, it wasn't. ACS still hasn't been allowed, but we're working on what should be allowed.Xaser wrote:Hrm? I thought the ACS restriction was already relaxed. Why bring it back again?
Apothem wrote:trying to make effects in DECORATE is so pathetically tedious sometimes, it is just simply more efficient and faster to use ACS. It really does help A LOT with controlling an object more soundly.
Go for it thenRules wrote:While as per the rules, the effects have to be coded in Decorate, alternate behavior in your effect that is activated through ACS, such as states used with SetActorState or dependance on Thing_Activate in encouraged, for customizability. If you include things like this, SHOW IT IN THE TEST MAP.
