I have the awesome PizzaTime, which is simply a brilliant table. But unfortunately, it has some issues. And as far as I understand, the technical support is left to us players. I haven't found discussions about issues with the gameplay itself, such as how does the PizzaTime follow the assumed rules and mechanics. Let me know if I have missed something relevant, especially if there is generally improved script already available! Otherwise, I welcome the community to share improvements here.
My Table Info says version 1.0 revision 53, the script says myVersion = "0.64", and the filename says pizzatime-65.vpx The latter number corresponds to the Version declared on the download site, why I think my script is the newest official one. One of the bugs I found was the misbehaving selection of the modes: the mode lights wont turn on and off appropriately when switching back and forth with the flipper buttons. There were a few typos and illogical lines in the script, and I think I have now managed to fix them, see the code below. However, as the ball drains, or the 40 second timer ends during the Pizza-Party mode, the mode selection light stays on, why my current code does not work if the mode selection appears again. While I am trying to find how to appropriately shut down the modes including the mode lights I post here the updated part for the mode selection script. If tried, remember to backup the original script.
See my further posts. The issue is not as clear as it seemed to be. Storing the mode progress is further screwing things under the hood!
sub modepick DisableFlippers=True modepickin=1 select Case mcycle case 0 playmedia "pizzaparty.jpg","modes",pBackglass,"",25000,"",1,3 ' (name,playlist,channel,cinematic,length,nextitem,audiolevel,priority) NextMode = 0 L43.state=rst L35.state=rst rst = L34.state L34.state=2 case 1 playmedia "timebomb.jpg","modes",pBackglass,"",25000,"",1,3 ' (name,playlist,channel,cinematic,length,nextitem,audiolevel,priority) NextMode = 1 L34.state=rst L39.state=rst rst=L35.state L35.state=2 case 2 playmedia "deathorglory.jpg","modes",pBackglass,"",25000,"",1,3 ' (name,playlist,channel,cinematic,length,nextitem,audiolevel,priority) NextMode = 2 L35.state=rst L40.state=rst rst=L39.state L39.state=2 case 3 playmedia "threepizza.jpg","modes",pBackglass,"",25000,"",1,3 ' (name,playlist,channel,cinematic,length,nextitem,audiolevel,priority) NextMode = 3 L39.state=rst L41.state=rst rst=L40.state L40.state=2 case 4 playmedia "badtown.jpg","modes",pBackglass,"",25000,"",1,3 ' (name,playlist,channel,cinematic,length,nextitem,audiolevel,priority) NextMode = 4 L40.state=rst L43.state=rst rst=L41.state L41.state=2 case 5 playmedia "pizzalove.jpg","modes",pBackglass,"",25000,"",1,3 ' (name,playlist,channel,cinematic,length,nextitem,audiolevel,priority) NextMode = 5 L41.state=rst L34.state=rst rst=L43.state L43.state=2 end Select end Sub
Another issue I have noticed. The idle light show can stay on during the gameplay if a new game is started too quickly after the previous one is finished (final ball is lost and start button is pressed promptly). By the way, I observed this same behavior with the Jpsalas's Zelda table. Does these two tables have something bug-related in common? It would be even nicer to fix possible root issues of many tables at once.
Edit: the code snippet above seems to screw the strings. But the code should be okay as no true new lines were presented, I think.
Edited by gamerplayer861, 16 March 2024 - 07:03 AM.