Sudden Error: "Arguments supplied, but parameter list not present"

[StValentines]

I've been working on this visual novel for a while now, and this error just showed up out of nowhere.

Code: Select all

I'm sorry, but an uncaught exception occurred.

While running game code:
  File "game/script (Singh Romance).rpy", line 880, in script
    label danisinghknow_done:
Exception: Arguments supplied, but parameter list not present

-- Full Traceback ------------------------------------------------------------

Full traceback:
  File "game/script (Singh Romance).rpy", line 880, in script
    label danisinghknow_done:
  File "C:\Users\thaiu\OneDrive\Desktop\renpy-7.3.5-sdk\renpy\ast.py", line 855, in execute
    values = apply_arguments(self.parameters, renpy.store._args, renpy.store._kwargs)
  File "C:\Users\thaiu\OneDrive\Desktop\renpy-7.3.5-sdk\renpy\ast.py", line 154, in apply_arguments
    raise Exception("Arguments supplied, but parameter list not present")
Exception: Arguments supplied, but parameter list not present

Strangely, I can barely find anything about this specific error online, and I have no idea what it means.

But what's worse, this is now happening on {i}every single label in the game. [/i] I can load previous saves and it's fine, but I don't want to risk this being some unseen bug that hides until the game releases or something, so I'd love to figure out what it means.

I've tried restarting the game, deleting the .rpyc files, and deleting persistent data. Nothing solves this issue, and even if I roll back to previous choices, this error shows up as soon as I hit other labels (even though it didn't hit them before).

Any idea what this might mean and if it'll be a problem in the long-term?

UPDATE: Going through the game again, it worked fine until I came across an actual error and, when I tried to rollback, it started doing this again. It seems to be doing this again whenever I have to go back from an error?

[trooper6]

What is the code where the error happens? It would be useful to post that code where the problems show up including the some lines before and after where the error shows up.

[Remix]

As in, show the code near: line 880, in "game/script (Singh Romance).rpy" which should be label danisinghknow_done:

The error implies though that you are calling that label and passing arguments to it without coding the label to accept those arguments...
I'd look through your script for danisinghknow_done and check for any arguments...

[StValentines]

As in, show the code near: line 880, in "game/script (Singh Romance).rpy" which should be label danisinghknow_done:

The error implies though that you are calling that label and passing arguments to it without coding the label to accept those arguments...
I'd look through your script for danisinghknow_done and check for any arguments...

What is the code where the error happens? It would be useful to post that code where the problems show up including the some lines before and after where the error shows up.

I can do that, but as I said in the post, the issue isn't with this specific label. I got through this label fine on the first time through, but had another unrelated error a little later. It was only when I rolled back that this (and every other label, not just this one) got this error. I keep rolling back, and I keep getting this error with every label I come across, despite having gotten through them without issue before.

But here's the code:

Code: Select all

menu danisinghknow:

    "Just luck, I guess.":
        jump danisinghknow_luck

    "I like spending time with you.":
        jump danisinghknow_like

label danisinghknow_luck:

    SN "32 years of bad luck is quite enough for me."
    SN "I appreciate this sudden change."

    DA "Happy to do my part."

    jump danisinghknow_done

label danisinghknow_like:

    $ danisinghliketime = True

    SN "It’s a bad practice."
    SN "I’m not worth the effort."

    DA "I don’t know about that."

    jump danisinghknow_done

label danisinghknow_done:

    $ danisinghliketime = False

    "We sit in silence for a moment, avoiding each other’s eyes."

    SN "Well. I should... probably sober up."
    SN "It was nice seeing you, Ms. Saldana."

    DA "Yeah. Thanks for taking time for me."

It's the same basic dialogue choice system as always. Menu choices jump to labels, after the content of each label it jumps to another label to continue past the choice. All properly labeled and spelled correctly and indented. It works on every other label in the game, and it even works on this label until I try to roll back after an error, at which point I have to restart the entire game to play it normally. It's a very weird set of circumstances, and I don't know what to make of it. Hell, maybe a player would never run into this. But I figure I should try and figure out what the deal is.

[trooper6]

The only thing I see with the code you’ve provided is that your menu isn’t indented properly. Menus should be inside a label. Yours is fully outdented as if it were a label, which it isn’t.

But what it the other part of the code? The part that throws the initial error? The one you keep trying to roll back from?

[strayerror]

Is it possible you've recently started using as variables, names like _args or _kwargs? Having either set globally could potentially cause this, as can be seen by running the demo code below. If it is the case, it's worth remembering that variables with a leading underscore (_) are reserved for Ren'Py's use, and seeking to use alternatives in your own code.

Code: Select all

label start:
    $ _args = ('bar', 'qux')
    jump foo

label foo:
    'Nobody here but us trees!'
    return

_______________________________________________________________

Also, just a quick PSA/heads up on this point:

Menus should be inside a label. Yours is fully outdented as if it were a label, which it isn’t.

This doesn't seem to hold true and named menus as top level structures were specifically called out in one of Tom's recent public Patreon articles (Aug 2019) discussing older Ren'Py features. Which isn't to say that it definitively isn't the cause, but if it does turn out to be the problem, it may well be worth trying to report it as a bug (again, if it can be confirmed as the cause). :)