# Full post attached

Hey all, Shirley here... as usual. Again, STILL no v2.3.0, I know it sucks. I'm not sleeping on it though (I'm actively working on it), so don't worry. As a matter of fact, yesterday I squashed quite a few bugs, one of which I'm here to talk about.

Odds are you had no clue about any of this, but PyNori contains not just one, but TWO debug modes.

The second debug mode is called "step mode", and can be activated by adding "--step\_mode" to your run command (ex. "py game.py --step\_mode"). The difference between step mode and debug mode is that step mode runs the game "one step at a time". Every time something (aside from prints and pauses) happens, step mode describes it on screen and waits for the user to press a key before continuing the script.

This is more important than it seems. Now, I'm going to ramble about something different, but trust me when I say it's connected.

The Windows command prompt is very different from the Unix terminals used in MacOS and Linux, in the sense that it's far simpler. The Unix terminals are conceptually the same thing at first glance (a window where you send commands). However, there's a LOT going on under the hood that I have NO clue about information-wise.

This is where my "PyPause" library comes in. It's supposed to be the Python equivalent of "pause >nul" in Batch. "PyPause" is compatible with all (major) platforms, those being Windows, MacOS, and Linux, and behaves the same... at the surface. Underneath, it's a much different story.

On Windows, it's as simple as importing msvcrt and using msvcrt.getch(). But for OTHER terminals... Python has to (temporarily) mess with its attributes in order to pause the script.

Anyway, apparently the code for PyPause v1.0.0 was flawed. How so? Apparently, in certain cases, the terminal settings aren't correctly reset after a user input is captured, which can cause the terminal to hang at input() prompts.

Well, PyPause v1.0.1 has arrived, and it fixes... MOST of the issues. input() prompts don't hang the terminal anymore if things go awry, and line breaks are fixed.

All players will be forced to update PyPause starting in PyNori v2.3.0. To update PyPause, simply type "pip install -U pypause" in your terminal. The -U flag is short for Update. **To those of you installing PyPause after December 3, 2025, pip should default to v1.0.1. You do not need to update.**

And... that's about it. Could I have shortened all this to "PyPause v1.0.1 fixes some weird bugs with Unix-based terminals"? Yeah, but that's boring. This is a devlog, I'm *supposed* to yap even if you don't understand what I'm saying!

Before I go, I'd like to ask a quick question. Are you tired of step mode being absolutely INSUFFERABLE to use when Discord isn't running on your computer? Well, I finally figured out the problem, and that too has been fixed in v2.3.0. Another thing to look forward to, yay!

Okay, that's it for real. The next devlog WILL be for v2.3.0, I promise. Shirley out!

Update PyPause!