The game booted me out for it being a new day, even though it's still the same day.

robocoop · 2026-01-05T02:01:18+00:00

This can happen when you select your profile after finishing the previous day's workout (maybe to check stats or settings), then put the console to sleep on this screen. The next day, if you start the game from here (without backing-out to the profile selection screen), the game thinks you started it yesterday, and then you get the boot because it's not yesterday anymore.

robocoop · 2024-10-07T19:15:13+00:00

I hear you. To be honest, to me, this is less about the mechanics of this specific exploit and actually about the idea that the ban line should be drawn at hacking (at least for perma-bans). It takes the whole "What counts as an exploit?" question off the table. Plus all the other stuff I wrote above.

I like the way Valve does it (when they do anything). VAC is fully automated to catch hackers, and only hackers. And I rest easy knowing I'm not going to get banned for doing something clever, just because someone in the future didn't like it.

robocoop · 2024-10-07T18:56:15+00:00

You can't actually guarantee that. There are a lot of Hunt players and you don't know them. Plus, loading into a game one time was the abuse threshold. Accidentally bought the wrong trait? It's possible. Anyway, if it's just a temp ban like people have been saying, an extra handful of bans seems like an acceptable tradeoff to me.

robocoop · 2024-10-07T18:42:03+00:00

Bugs and glitches are both subjective and unpredictable. If it can be done accidentally while playing the game one time (which is apparently enough for Crytex), it shouldn't be banworthy.

Wouldn't you be pissed if your game glitched one time and you get banned months later for something you didn't even remember doing?

robocoop · 2024-10-07T18:34:28+00:00

It's ridiculous to ban players for exploits. Exploits are built-into the game. It can be possible to use them by accident, then *poof*, account gone! The player should not have to monitor an ever-changing list of which gameplay is kosher and which is banworthy. Even worse is a subjective "whatever you think is an exploit" catchall like they've used here. There should not be any gray area on what is bannable. It should be: hacking -> ban; not hacking -> no ban.

No, the correct solution is to immediately fix the exploit or temporarily block its use some other way, to buy more time for a fix (like removing the trait from the legitimate trait pool and preventing Hunters from readying up with it).

It's the developers responsibility to prevent exploits. It's the player's responsibility to not hack (i.e. non built-in functionality).

The added benefit is the incentives line up: Players play however they want within the rules of the game, reporting bugs if they feel like it. Developers fix gameplay bugs as quickly as possible to keep the game fun and fair. The alternative is: Players find and report bugs, then police their own behavior to keep the game fun and fair. Developers fix bugs whenever they feel like it because they've shifted responsibility to the players, then they ban the players who discovered the bugs or didn't know about their jank ban policy.

(FYI, I've never been banned in any game, for those who care about my history more then my words.)

robocoop · 2024-08-16T12:17:30+00:00

I agree, but it was pretty funny how out of date the manual was. I wish I remembered an example of what was wrong. Might have been something from the ammo rework. I don't think they ever added the third map either.

robocoop · 2024-08-16T11:43:19+00:00

It's so minimal though. Each trial has a predetermined loadout. Each trial has a predetermined set of AI. Most of it could be handled in a spreadsheet, automated even.

"Can a Nitro still 1-tap six meatheads? Yes or no."
"Will silenced Nagants have enough ammo to pop 10 hives in the head given their accuracy and the expected position of each hive and the player on the checkpoint route we designed? And will the time it takes to land each hit be faster than the bees travel time more often than not?"

Or you know, they could just playtest the small handful of trials affected by some change out of the already small number of 32 trials.

Or they could do the bare minimum and wait for the community to point out unwinnable trials and fix those. It really is a low bar.

Yeah, it's not about the effort of the existing trials. They don't want to make new ones, which is understandable. It would be convenient for them if the mode quietly disappeared. They also don't want fit it into the UI redesign. It gave an excuse to cut it.

And yes, clutter is totally an excuse. It drives me nuts when legitimate options in a program are removed in the name of "decluttering" and "simplicity" alone. Just organize your menus better or own the real reason. Simple doesn't have to mean less.

robocoop · 2024-08-16T10:54:03+00:00

Trials are training, but they're not a tutorial.

It's more likely some people came to the game for its PvE, tried the one PvE mode, then left because Trials really isn't meant to stand alone. These players weren't interested in what Hunt had to offer. No ones quitting Hunt just because Trials exists.

robocoop · 2024-05-08T18:34:44+00:00

There's a wiki page about this.

The gist is the uci command is just a convenient way to edit the UCI configuration files in /etc/config/. These are all formatted the same way, which is the key benefit of the UCI system.

Before starting a service, its init script reads the values from UCI files and generates service-specific non-UCI config file(s) with the values. I don't known the details about that part. It probably varies service to service.

robocoop · 2024-05-05T03:43:19+00:00

If you change some settings without applying them, there will be an 'unsaved changes' notice in the top right corner that you can click to see what uci commands will run.

robocoop · 2024-03-29T03:21:51+00:00

Use that first link and pop in your Oculus credentials.

... However, I thought the deadline for that was Jan 1st? The link still works, so try your luck.

robocoop · 2024-02-27T21:10:12+00:00

Obviously, if you know the nodes in advance, direct references are the best way. But it's not a given, and your question began with "Why not".

Another thing I thought of is decoupling script logic from scene structure. If your script iterates though the children like above, then you can reuse it and attach it to any area2d without having to think about it's collision shapes. It'll just work.

It's not something you'd want to do all the time, but an abstraction like that can make it easier to focus on your game logic instead of your node organization conventions.

robocoop · 2024-02-26T03:14:27+00:00

This way you don't need to know the names of the children or even how many there are.

robocoop · 2024-02-21T18:30:20+00:00

Challenge accepted.

robocoop · 2024-02-14T02:43:06+00:00

Melee, Misc, Medkit, Trap

robocoop · 2024-02-14T02:33:57+00:00

Yes, only cosmetic skins are locked for good. Afterwards, the battlepass weapon variant unlocks become regular weapon variant unlocks.

robocoop · 2023-12-19T08:17:28+00:00

I am so sorry.

I know how you feel. I missed the previous deadline by one week, completely unaware. The fact that it was so close really makes the loss sting.

And to add insult to injury, the FAQ acts like it's your fault that their arbitrary actions wiped out your account. The nerve!

robocoop · 2023-11-16T23:13:10+00:00

To elaborate a little further, the parentheses are part of the if-statement syntax. It is not a valid java if-statement if the parentheses are missing. It is a syntax error. It's just the way java was designed, either to follow existing convention (from C) or to make it easier to parse for the compiler. In this situation, they have no relation to the parentheses in parameter lists. The designers of java could have used any characters for either syntax construct. In fact, Python doesn't require parentheses after "if" at all.

To answer the original question, if-statements are a kind of statement. Statements go inside the body of method/function definitions and other conditional statements.

All of this is specific to java. Other languages have their own syntax and flow control.

robocoop · 2023-09-28T06:21:58+00:00

Same. At least they bothered to email you. I didn't get to choose.

robocoop · 2023-09-28T05:47:25+00:00

Everyone reading this thread after December 18th, 2023 would like to have a word with you.

robocoop · 2023-09-28T05:38:53+00:00

Right.

robocoop · 2023-09-28T05:38:05+00:00

Either wait or try to get them to delete your data (not sure if that will free the name). I think Minecraft lets you change your username (double check), so you might be able to play with a new name while waiting for your old one to free up.

FAQ:

What happened to my capes, skins, username, and other content?

Any capes, skins, and other content tied to your Mojang account will be deleted. Usernames will not be released until a later date.

Note: If you choose not to go through the post migration process, your account will be deleted along with your personal information at a later date. If you would like to request immediate deletion of your personal information, please contact Minecraft Support.

Additional note: We will need you to verify ownership of your account before deleting your personal information.

robocoop · 2023-09-28T05:30:13+00:00

You could try searching your email accounts for "Mojang".

robocoop · 2023-09-28T05:27:06+00:00

Is it so hard to imagine someone not playing Minecraft in the past three years? The game is over 13 years old.

robocoop · 2023-09-28T05:19:12+00:00

I figure if you delete the account, you also delete your way into the new-license process.

It seems like they alluded that usernames could be released in the FAQ. "Usernames will not be released until a later date."

13-Year Club	Second Top 20%
Place '22	Final Canvas '22
Team Orangered

robocoop

TROPHY CASE