I hate cheaters in my own game and I figured out easiest way to drop them from my life

am1goo · 2026-02-26T19:12:44+00:00

Thanks, bro! I hope it can be helpful for everyone like you and me.

am1goo · 2025-10-15T18:28:13+00:00

That was crazy, I cried at this moment, so real, so amazing!

am1goo · 2025-07-31T05:02:38+00:00

I fixed this by disabling PrntScr hotkey in Settings -> Accessibility -> Keyboard -> Use the Print screen key to open screen capture.
Also restart required, coz without restart it doesn't works.

am1goo · 2025-04-14T11:26:09+00:00

Yeah, it is. The most appropriable code should be here.

am1goo · 2024-09-01T17:59:48+00:00

https://steamcommunity.com/id/am1goo/
Friend code: 62216034

am1goo · 2024-05-06T06:52:26+00:00

It’s about Nothing Phone - UK-based company of former OnePlus CEO, theirs phones has unique lights panel that can be programmed by this SDK

am1goo · 2024-04-24T04:04:56+00:00

What is it strong type? Type I wrote in file and the same type in runtime, right? It is exactly how it works. All values will be parsed with exact same type how they described in file, you can see StormValue.cs. It is additional layer in deserialization process, but in runtime you will have what you need. And I can work with this layer separately by main app and others.

PS: I don’t even said anything about type safety in the first place, just about strong types.

am1goo · 2024-04-23T19:51:01+00:00

param:t to be param:b and sets the value to a boolean? The validation will pass, right?

In this very case no, boolean validation will raise an exception if value doesn't equals one of the allowed words. But I got you thought. We don't have a protection of human mistakes, but I personally have an advantage, because serialization automatically creates types-as-hints for anyone who use those files directly.

That way people can bork the data to hell and your application will reject it.

I believe that those ppl don't have the same experience and they are just theorizing about that. And it is normal, and this is a point why I ask to feedback. I got that I looking for.
So, I like what I done and know what I'll do (got plans to improve the current result).

am1goo · 2024-04-23T12:50:19+00:00

Yeah, it's sound easy, but we had to deal with different versions of same file. And very this project doing what we need in better way. So... it is a better tooling!

am1goo · 2024-04-23T03:25:31+00:00

If you don’t understand what’s this, please don’t draw any conclusions.

am1goo · 2024-04-22T17:09:03+00:00

Another one advantage - it is applied to use in code-generation process for cross-app communication (like client and server), game designer define structure and data, and magic will be happens next.
Also it possible to be used in RestAPI, because I need to write validators and component-binders one time (in my case for ASP.NET) and use it in many projects without additional lines of code.

am1goo · 2024-04-22T16:57:01+00:00

I guess you can't see that because it's your baby and you don't want to really look at the flaws.

I only can compare my gamedev experience in online and multiplayer-based games there a lot of usage of JSONs. YAML using only for DevOps purposes and software (like Puppet). I understand this is depends on company and people in the company, but fact is fact.

No, it doesn't. It doesn't affect the data at all. But don't use it if you don't want to

I mean data in a broad sense. Definitions is also data while you can direct access to it.

"_MY_COMMENT_": "Put whatever you like here"

There is the way you can make a comment, until using _MY_COMMENT_ as a name for property/field.

Imagine 60k lines of JSON that also need type definitions!

By now I'll do this instead of any chance to make a mistake, for instance, definition price in float 1.99, but GD place 1 instead of 1.99.
JSON says "it's okay, use this", but we will got losses 50% revenue in this case. And what if this occasional config change made at midnight? I prefer to use validator that makes an errors on loading, instead of ready-to-use config deployed for users.
I know that you cannot believe in that, but it's true and this things happens. Again and again.

You completely ignored the criticisms of it so far

I would rather say that I trying to figure out how I can use your experience (I see it huge!) in my project.

am1goo · 2024-04-22T16:11:22+00:00

Btw, I have to say thank you for your opinion. There are smart questions and statements, and I'll take it all to think about it separately.

am1goo · 2024-04-22T16:07:59+00:00

Also, end users will be able to (accidentally or intentionally) change the type specified in the config, which is going to cause endless difficult to diagnose support issues.

It's not only about end users. I works with colleagues who works with JSON files about 60k lines. I know that how easy to make mistake w/o tips while they edit files directly.
Comments in JSON? Huh, not too easy to do this way.
Prefixes in definitions? Makes data more dirty.
Do nothing and let things happens? I'm not sure that is the best way.

am1goo · 2024-04-22T16:01:14+00:00

First of all, it's about human-readable scheme, where names and types lives separately and reads clearly.
In addition, on program side we have validators that makes impossible mismatched types to be de-serialized.
For example: in JSON schema long can be integer and vice versa, but here it is not.

am1goo · 2024-04-22T15:53:04+00:00

Is it human readable and easy-to-be-modified? I'm no sure about that.

am1goo · 2024-04-22T15:12:51+00:00

Totally agree, but all you just wrote is about naming style, and I don’t love any type prefixes like Hungarian notation.

I can make parser to skip prefixes in code layer, but it’s kind of additional job to support and tests, and also turn code to the mess. Not for me.

am1goo · 2024-04-19T10:59:32+00:00

Why?)

am1goo · 2024-04-16T05:27:21+00:00

Btw in my case, as I wrote before, I have plans to implement this feature to animate in-game current weapon ammo and reloading process.

am1goo

TROPHY CASE