SMAPI - Stardew Modding API

SMAPI - Stardew Modding API

971k Downloads

Console History

VasVadum opened this issue ยท 4 comments

commented

Basically, the SMAPI console needs to have history to scroll through. If I leave the window at its default tiny size, I have virtually no history at all. I can't scroll up to see what errors it told me about when I loaded the game. In this image below, you'll see a scroll bar, but only because I had the window maximized before it loaded all the data. If I hadn't, there'd be no scroll bar.

image

Basically, just give this thing the ability to keep history. This is on Windows 10. I had a case once where a mod was causing loading issues and I couldn't get the error because it'd disappear behind newer text too fast, and I found I could get it to keep more of the history if I extended the window height, or clicked maximize faster.

commented

@VasVadum The command buffer is a different thing, it doesn't affect scrollback. Try this:

  1. Launch SMAPI like usual.
  2. Click the top-left icon and choose defaults (not properties).
  3. On the layout tab, change the Screen Buffer Size to a larger height (I have it set to 9001).
  4. Exit and relaunch SMAPI and it'll be increased permanently.

image

commented

Ah, ok, that worked. Annoying Microsoft defaulted it to 30 and made the window small and for some reason your tool opened CMD up differently than any other time I've ever used CMD.

commented

Hi! That's a limitation of Windows itself. You can configure the scrollback limit, or check the SMAPI log file to see the full output (including details not shown in the console by default).

commented

Scrollback limit can't be increased, your modding tools here use a custom CMD window.

image

image

I set buffer size to 5x just now, in CMD. 250 lines instead of 50.

Yours, the buffer size depends on the window size. If the window defaults at that small size and I forget to maximize it, it deletes anything that falls off screen, no matter what buffer size there is. I checked the buffer size when yours loads up, it was back at 50 again while CMD in Windows, stayed at 250 as I had set it. I don't know what the difference is between the two, but I use CMD as a quick way to look at the issues, because of the colored text, it can be very helpful to me to see what I need to fix and helps me find things better.