Talk:ACS

Category:New features

Of course, technically ACS pre-dates doom's source code release (in Hexen), but it is still a 'new feature' to doom, and since that's the primary focus of this wiki, I think it belongs. -- Jdowland 18:59, 16 Jul 2005 (UTC)

"Note that a script is defined somewhat like a function in C, aside from the oddity that it does not have to be terminated after the bracket with a semicolon like all other statements."

This is also the case in C. Function definitions do not have semicolons after their closing brackets, and if a semicolon exists, it will be interpreted as an empty statement at the top level. Some reminders on function definitions vs declarations: [1] 71.58.109.233 21:09, 23 September 2007 (UTC)

Mixes ZDoom and Hexen

This is written as if it were for a ZDoom wiki; it needs to start with Hexen's specific data and then add ZDoom (or other) implementations below in a section name something like "Use and expansion in source ports". There is a more or less understandable reason for the article's current state, it was taken from the ZDoom docs, but it's not well integrated to this wiki as it stands. Who is like God? 15:57, 6 May 2008 (UTC)

"Bumping" discussion to note this is still a problem 5 years later. No mention of Eternity or other ports that support ACS and, in some cases, the same extensions as ZDoom. --Quasar 17:35, 31 July 2013 (UTC)

I've edited the article to be more specific to ACS0. I've probably went way too technical, but I'll leave it to someone else to sort that out. If we would like to go further in the direction of documenting the byte code format here, a more or less complete reference is available in my ACC++ manual's byte code section and appendix B: https://bitbucket.org/Blzut3/acc/src/tip/docs/manual.odt?at=default I have no problems with any of the information there being reproduced here. Blzut3 01:55, 1 August 2013 (UTC)

need to tie this to BEHAVIOR article etc

• this article should indicate that compiled ACS goes into a BEHAVIOR lump (one per map), link to BEHAVIOR.
• document the ACS bytecode as well as the raven "front end" language (and agree on terminology for that)
• point out alternative ACS compilers (David PH's?)

-- Shambler (talk) 09:06, 13 May 2018 (CDT)

Needs refactor IMO

Writing GDCC code has its own peculiarities, so its seems the aforementioned BEHAVIOR, Hexen, zdoom, and even code examples, would better suited to their own pages. I have an interest in ACS and some ACS code experience, but little wiki refactoring experience. I'd like input on how to restructure this subject before diving in, but I am willing to attempt it.

-- Mistersector (talk) 16:05, 15 July 2024 (PST)

What is "GDCC code"? What do you have in mind in terms of restructuring? Note that the wiki is not the place for full-blown tutorials and examples, at least not the main encyclopediac articles. But we do have an old old, little maintained section for such content, which may be suitable for your plan. --Xymph (talk) 05:56, 16 July 2024 (CDT)

@Xymph: User is referring to the Game Data Compiler Collection, which includes a ACS compiler,GDCC-ACC. It is one of the three ACS compilers currently on the market (ACC, BCC and thus GDCC) - https://github.com/DavidPH/GDCC. However, i am not sure what the request is for. --Redneckerz (talk) 06:40, 16 July 2024 (CDT)