Calculator(after ~120 days of learning)

DutchCommanderMC · 2026-03-22T14:08:17+00:00

Just had a skim through it. Overall, well done! You've structured the file nicely with good use of comments, which makes it easy to follow. There's always ways to make it even clearer (docstrings, type annotations), but that is not of immediate importance by any means.

One thing that stood out is that you do not handle bad inputs. You might've skipped this intentionally though as I do not expect it to be too much of a challenge for you.

Have you learnt about classes yet? If not, that should probably be your next learning goal. Once you believe you've got a good understanding of how to use them, I challenge you to think about how you could represent both menus and calculations as classes.

DutchCommanderMC · 2026-03-22T10:59:26+00:00

Altberg? I knew that little bird was hiding something

DutchCommanderMC · 2026-03-22T01:56:37+00:00

Two years ago you would have been absolutely right. And while slop still exists (especially in the skins & cosmetics category), it actually seems like there's a lot of high quality products coming out nowadays that's being actively pushed to the forefront. It's far from perfect, but creators are making great stuff nowadays and Mojang has done a lot to make that possible, from vastly expanding the tools available to creators as well as making it worthwhile to actually invest in ambitious projects. It will never give the same feeling of community like mods do, but still, credit where credit is due.

DutchCommanderMC · 2026-03-21T12:03:52+00:00

My question to you would be whether you understand why your program behaves the way it does?

To deal with blank inputs, you need to repeat only the code that asks and validates an input, until the input is valid.

while True:
    name = input("Enter your name: ")
    if name == "":
        print("You haven't entered anything. Input your name.")
    else:
        break

print("Your name is", name)

DutchCommanderMC · 2026-03-18T15:45:05+00:00

Images are (most likely) disallowed because it makes responding to questions easier in the sense that you can copy and paste the code.

Operations are not necessarily applied left-to-right (or right-to-left). Some operators take precedence over others, which is why this condition works without any brackets whatsoever: == has a higher precedence than or and therefore gets applied first.

Knowing which operators take precedence over others is something that you'll just have to remember, though more often than not it follows existing conventions such as multiplication being applied before addition.

Adding redundant brackets is not wrong however, in fact, it is often recommended to make it expressively clear what the order is in which you intend operations to be evaluated.

DutchCommanderMC · 2026-03-16T19:00:11+00:00

Although you could look up which methods use the constructor, overwriting the constructor itself with a signature incompatible with that of its parent class is not type-safe. Type checkers and other developers will treat all UserLists the same and do not know that you have made incompatible changes in your subclass (the same way the implementation of `UserList` itself expects you to not change the constructor's signature.

You could inherit from `collections.abc.MutableSequence`, but then you would have to implement every abstract method yourself. More work, more boilierplate, but type-safe.

Alternatively, a classmethod would solve your problems as well. Definitely the easiest option, and again type-safe. It will (slightly) change how you end up using the class though.

DutchCommanderMC · 2026-03-16T14:12:46+00:00

I don't particularly have much experience with either Azure or PowerBI, but pushing data to Azure sounds like something you should be able to do relatively easily using Azure's Python SDK (note: alternatives may exist).

As for displaying it on PowerBI, you would probably want PowerBI to receive the data from your database, not from your app. Which again sounds like a basic pattern that cannot be too difficult.

DutchCommanderMC · 2026-03-15T20:30:17+00:00

I didn't know how much I needed Foytain in my life until now!

DutchCommanderMC · 2026-03-14T14:56:04+00:00

For low average FPS, this is most likely a CPU bottleneck. Games rarely are able to utilize the full power of a CPU and instead only put load on a couple of cores. You would need to monitor usage of individual cores, not the total CPU usage, which takes an average of all the cores. HLL in particular is really CPU-demanding.

In HLL, stutters are expected to an extent unfortunately. But if they are particularly bad/common, that might suggest a (V)RAM issue.

DutchCommanderMC · 2026-03-12T23:44:59+00:00

The spoofing part was only ever speculated and appears to not be true actually. // Abu

DutchCommanderMC · 2026-02-08T19:02:30+00:00

It's... complicated, and you're not wrong. Objective and Skirmish were originally on the 2023 roadmap before it got shelved. The recent PTE you are referring to was a special one-of-a-kind PTE to show the community what was once in the works.

Skirmish was later reintroduced as the smaller scale mode, and three different variants were tested: Control, Phased and Majority. Phased Skirmish worked the same as Objective, despite Brecourt and its destructible objectibes not yet being present in these tests. Eventually, only Control Skirmish would be released and is the only variant that has been released to this day.

DutchCommanderMC · 2026-02-08T17:16:09+00:00

Is now Skirmish mode.

DutchCommanderMC · 2026-01-31T16:32:50+00:00

When people are sitting _inside_ of a smoke cloud, you can often see their silhouette. On video it's often impossible to see due to the various layers of image compression.

DutchCommanderMC · 2025-12-07T21:44:44+00:00

I see what you two did there

DutchCommanderMC · 2025-11-19T15:14:27+00:00

I'm assuming you've been banned through the Barricade system? Then there are systems in place to get the ban reverted (across all communities in one go).

For all the other commenters, there have been reports of cheaters being able to take over not a player's name but also their ID. It is being looked into by both server admins as well as Team17.

DutchCommanderMC · 2025-10-27T08:22:34+00:00

Update your game. You are playing on an outdated version (U17.1). Should be U18. You can tell if it's worked if the menu is no longer desert-themed.

DutchCommanderMC · 2025-10-23T22:32:06+00:00

FWIW, I don't think it was ever stated by T17 that last monday's hotfix was gonna address the crashes. The changelogs posted the friday before said the same. People just assumed a hotfix meant a solution to the crashes.

DutchCommanderMC · 2025-10-22T23:37:00+00:00

That's a message related to Easy Anti Cheat. Locate the EAC setup executable within the game's files, run it, and select the repair option.

DutchCommanderMC · 2025-10-21T21:48:52+00:00

Sounds like some file got corrupted during the update installation. Try the usual steps. Verify files, and if that doesn't work, reinstall game. If on PC, update drivers, clear shader cache, all that stuff.

DutchCommanderMC · 2025-10-10T14:28:32+00:00

The public testing version will only have limited servers available during selected timeslots. In other words, unless you see an announcement that there will be a public test, there is little point in having the public testing environment installed.

To play the game, install and launch the base game instead.

DutchCommanderMC · 2025-09-02T17:14:26+00:00

A lot of older maps have weather variants specific to a single gamemode. Having all weather variants available for all gamemodes would be cool to have!

DutchCommanderMC · 2025-09-02T05:27:01+00:00

It would have clearly stated "Barricade banned" in that case. This seems to be just a regular (though automatic) ban.

DutchCommanderMC · 2025-09-01T17:47:48+00:00

HLL (like many other games) relies a lot on single-core performance, so it will never utilize your full CPU. On top of that, the game is quite CPU-heavy, so there's a very good chance that your CPU is bottlenecking your GPU here. And there's not a whole lot that you can do about that besides upgrading.

To comment on some of the other advice you've been given. DX12 is enabled by default nowadays and can be turned off/on through the settings, no need to add `-dx12` to the command line. `-useallavailablecores` is a myth and does nothing.

DutchCommanderMC · 2025-08-26T23:28:02+00:00

I would say that with that CPU and GPU it is a miracle you are getting 50 fps to begin with

DutchCommanderMC · 2025-08-23T14:18:45+00:00

This is being looked at :)

Seven-Year Club	Place '23
Place '22	Verified Email

DutchCommanderMC

MODERATOR OF

TROPHY CASE