MantisBT - Zandronum
View Issue Details
0002746Zandronum[All Projects] Bugpublic2016-06-03 20:592018-09-30 22:35
Fused 
Dusk 
normalmajoralways
closedno change required 
3.0-beta 
3.0 
0002746: NamedRequestScriptPuke is completely broken
Under no circumstances does NamedRequestScriptPuke work in 3.0.
Load the wad and a print message appears instantly.
One is shown for a numbered script, and one is supposed to show for the named script.
The latest build (160519-2047) also has this
No tags attached.
? MAP01.wad (1,948) 2016-06-03 20:59
/tracker/file_download.php?file_id=1817&type=bug
Issue History
2016-06-03 20:59FusedNew Issue
2016-06-03 20:59FusedFile Added: MAP01.wad
2016-06-04 19:12DuskAssigned To => Dusk
2016-06-04 19:12DuskStatusnew => assigned
2016-06-04 19:12DuskProduct Version => 3.0-beta
2016-06-04 19:12DuskTarget Version => 3.0
2016-06-04 19:41DuskNote Added: 0015010
2016-06-04 19:41DuskStatusassigned => feedback
2016-06-04 20:14FusedNote Added: 0015012
2016-06-04 20:14FusedStatusfeedback => assigned
2016-06-04 20:40FusedNote Edited: 0015012bug_revision_view_page.php?bugnote_id=15012#r9052
2016-06-04 20:41DuskNote Added: 0015014
2016-06-04 20:41DuskStatusassigned => resolved
2016-06-04 20:41DuskResolutionopen => no change required
2018-09-30 22:35Blzut3Statusresolved => closed

Notes
(0015010)
Dusk   
2016-06-04 19:41   
It appears that your compiled ACS is screwed up. It does not call NamedRequestScriptPuke in the first place. When I compiled the script, the resulting ACS works fine.

Looks like something's wrong with the way your code is being compiled. Where did you get your acc? Can you share your zspecial.acs?
(0015012)
Fused   
2016-06-04 20:14   
(edited on: 2016-06-04 20:40)
If I remember correctly, I went to the bitbucket page to add it manually, so what I have is the same.
'https://bitbucket.org/Torr_Samaho/acc/commits/e329377d9c203e552e11bbee53c630265923ac13 [^]'
-126:NamedRequestScriptPuke(1,4)

EDIT: After some chatting it turns out my version of acc was actually broken in a way. After downloading a fresh up-to-date compiler this issue was fixed.

(0015014)
Dusk   
2016-06-04 20:41   
Discussion on IRC yields that changing the compiler to a build Sean provided causes the problem to go away. So it indeed is due to a faulty compiler.

We should get an official acc build up to avoid confusion like this.