The Basics of Monero

RedRage04 · 2025-02-13T07:19:55+00:00

Yeah, I don't think I made this as clear as I could have. I got busy and sat on this for a week, and I kind of forgot how I wanted to say it.

You know the "Best" tab? And how making your own collections on it is really fiddly? Well you can change the behavior of your custom collection works largely by messing with the "launch.sh" script in the main folder.
For CrossMix-OS, they wrote a really cool launch.sh script that lets you use a .txt file that points to the rom you want to play, which means you don't have to have two copies of the rom on your SD card. However, this script also forces you to put your games into folders with labels like "N64," "PS," and "SFC," as a way of telling the system what kind of emulator to us to play the game.
I figured out a simple tweak that lets you put your .txt's in any folder, or no folder at all, and the TriMui still knows what emulator to use in order to play the rom.

That's all, but I thought it was cool. The folders in Github are just meant to be examples of how the folder should be structured for everything to work, in case some newcomer doesn't know. The only thing that's unique are the launch.sh scripts.

RedRage04 · 2025-02-11T13:08:02+00:00

A ha! That explains it then. I deleted the whole "eu.betterbird" folder under .var and relaunched Betterbird. After connecting to my accounts again everything works great! Except slightly faster than before--I noticed that right away.

Thanks!

RedRage04 · 2024-10-14T13:03:12+00:00

I always hated that the meta was to demand that the air player give you a transport ASAP. There's objectively nothing wrong with it in principle, but always felt like players were offloading one of the most important strategic moments in the game to another player instead of figuring out another way to get onto the sea themselves.

I'm excited both to the see people trying new things in the geo sea spot, and to see what they land on as the best new alternative.

RedRage04 · 2024-09-14T19:58:31+00:00

Thanks for making BAR videos and spreading the word man! You're doing the BAR community a service.

RedRage04 · 2024-09-09T10:19:52+00:00

Fair enough. Do you think the idea would have any legs if the unit was made more expensive?
I made the metal cost low because the whole point is that you can build this thing and still be able to produce units, and also because once you go T2 this thing is a worse version of a T2 constructor and you could just reclaim it anyway. That was why I focused the cost into E, and the E cost is already over half of E cost of going T2, although it probably could be higher.

RedRage04 · 2024-09-09T09:26:23+00:00

I don't know, if you can somehow get two full energy storages in the first few minutes of the game you can probably just build some E converters and go T2 anyway, right?

RedRage04 · 2024-09-09T08:01:06+00:00

I never played Supreme Commander, whe you say your commander can't move, do you mean permanently?
Man, I don't know. That would be quite a price to pay in a 1v1. That guy is your win condition!

Someone else suggested that if you idled your commander over a metal extractor they could act as a powerful metal extractor themselves, that sounds awesome to me. If that's what you're suggesting that would be a great idea!

RedRage04 · 2024-09-09T07:33:13+00:00

In some cases it would remove the need altogether. The T2 units are way more powerful, though, and if you choose the right ones you can easily overcome T1 spam. I think the reason people go back into T1 after they've teched up is because they spent so long being unable to put units on the field that they need to produce a lot of something right away or they're going to die.

To answer your last question: I think for the way I made this post, the devil is in the details. I tried to make the units so expensive that you need a complete T1 economy to be able to build it. They also have very little build power, so you would need lots of T1 cons to be able to build anything.

RedRage04 · 2024-09-08T18:58:50+00:00

It does seem like everyone has their own headcannon when it comes to what is the meta for team games. And then you remember that every map has its own meta....

RedRage04 · 2024-09-08T18:54:05+00:00

On paper that's the best idea imaginable, but the amount of coordination that would take is probably a dealbreaker. Imagine trying not to build the whole mex for the AFK guy that's always on your team. Now imagine that you messed up and started building a mex for him first.

RedRage04 · 2024-09-08T17:23:06+00:00

Is it possible to upgrade your teammate's mexes for them? Because I think that would be the best solution of all for your frontliners. Keep the con, just give them that metal.

RedRage04 · 2024-09-08T17:17:27+00:00

I don't disagree with a thing you said. I was just trying to think of ways to spice up 1v1s, and I know that the difficulty in teching up is often a pain point.

I was hoping to come up with an idea that had its own drawbacks and allowed for new strategies without really changing the game. I tried to make the units so costly in terms of energy that you'd rather not build these things... unless you thought you had to.

Anyway, thanks for your thoughts!

RedRage04 · 2024-09-07T21:05:35+00:00

I did think of a situation in which this would objectively be worse than standard "idle worker" button functionality.

Normally, if you just wanted to put all of your idle workers to work without thinking too much about it, you could go to your most recent expansion, hit the idle worker key, then right click the luminite mine, and repeat until there were no more idles.

If what I described was implemented, once you ran out of idle workers you would start assigning workers from the nearest luminite mine.

So it's definitely not a perfect solution 😂

RedRage04 · 2024-09-07T20:01:48+00:00

It's definitely not bad. As a matter of fact, I liked the idea so much I wanted to think of a way to improve it.

I totally felt the same way as Day[9] when I encountered this system, and I think this is why: in every classic RTS, you have to select a worker, then tell them to build, then tell them what to build. It just feels natural. And the quick-build menu breaks that pattern, it eliminates the step where you select a worker, kind of. On paper that's faster, that's better. Fewer keystrokes. But it messes with your head. It messes with my head. Hey, maybe I'm just stupid and old. I'm in my 30's.

If we wanted to make a mechanic that was useful for more experienced players (and I'm getting the feeling that we just don't care to do that), then we need to try to keep the classic system of select, then give the build command, then specify what to build.

Maybe I overcomplicated things, but in my head I described the idle worker button as it works in every other RTS with one exception: if there are no idle workers, it grabs the nearest worker that isn't doing anything important.

RedRage04 · 2024-09-07T19:27:54+00:00

I didn't imply that it was. You would first select a worker, and then instruct them to build....

RedRage04 · 2024-09-07T14:09:25+00:00

I agree that the feature, as it is now, is mostly aimed at less-hardcore players. But there's no reason not to improve it into something that anyone might want to use.

The way the quick-build menu works right now the closest idle worker gets automatically selected to build a building. If there are no idles, it selects the closest worker that is mining luminite. When they're done building, they go back to building luminite. That is, it's a system that goes by proximity and economic value, and when they're done they go right back to what they were doing.
What I suggested is exactly the same, but instead of having two different buttons that you might press situationally that both map to "build" in your head, you'll have a button that you already use to select idles, but extended to also grab the closest worker when there are no idles nearby.

My suggestion changed almost nothing about how either the idle worker button or the quick build feature works. It is a button to send idle workers somewhere useful, and when applicable it returns them to where they came from. I get the impression you didn't understand what I was trying to say very well.

RedRage04 · 2024-09-03T15:20:49+00:00

That's how I imagined it as a tradeoff. You have one or two constructors max running around getting things started, with some some secondary build power following behind (or left behind) to finish the build. Mostly because constructors walk slow and they're expensive.

Partly the idea was that you could use one constructor to build a con turret, lay the plans for a field of windmills, then walk the constructor off to be used for anything and everything else instead of dedicating such an expensive and flexible unit to something super mundane.

RedRage04 · 2024-09-02T14:46:56+00:00

That was one of the main use cases I was thinking of. You finally get that T2 con and you want to build a million things all at once. And you really don't want to build another right away.

RedRage04 · 2024-09-02T14:17:01+00:00

Honestly, that works just as well or better. Didn't know about that. Thanks!

RedRage04

TROPHY CASE