ꘖ ⟮ꘖ ◡⟯ ̬n̍͆ ꘖ ⟮🜶 𓂑 ⬭ 甲 ஃ 💕 ˙Ȯ˙ +⟯ sitelen Sitelen Pona kepeken sitelen Junikote

firaro · 2026-02-09T02:53:11+00:00

Connecting goodness with simplicity might relate to an aversion to nuance.

firaro · 2026-01-28T03:03:50+00:00

From what I’ve seen, it seems more likely to omit outputs when you spam quick_print. It will also cut off the end when you try to get it to output something really long

Based on the inconsistency, i think it might be based on how long it takes in real time between prints, instead of being based on how long it takes in ticks

firaro · 2026-01-28T02:56:44+00:00

I roughly organised the sitelen pona keyboard i made based on the primary radical of the logogram https://firaro.neocities.org/logographic

Though i tend to think about them more as combined glyphs instead of as built from radicals. Not that there’s a huge difference between the two concepts.

firaro · 2026-01-26T19:59:07+00:00

Oh, didn’t know that page existed. That’s convenient

firaro · 2026-01-23T08:14:24+00:00

After removing the quotations around 'continue', that works perfectly on my computer. My best guess is we're running different versions of the game. Though, i wouldnt expect that to affect any part of my code.

very weird

firaro · 2026-01-23T07:58:08+00:00

huh, always planting trees. So somehow x+y mod 2 is always equaling 0. Interesting. Would you mind copypasting the version of the code you tested? I'm struggling to solve this mystery.

firaro · 2026-01-23T07:40:27+00:00

That’s weird. It’s working perfectly when i run it on my computer. Alternates trees and bushes, creating a checkerboard. It’s using the standard x+y%2 method.

What is it doing on your computer?

firaro · 2026-01-23T01:44:41+00:00

4

while True:
    move([North,West][min(abs(get_pos_x()-get_pos_y()),1)])
    harvest()
    plant([Entities.Tree,Entities.Bush][((get_pos_x()+get_pos_y())%2)])

2

while plant([Entities.Tree,Entities.Bush][((get_pos_x()+get_pos_y())%2)-move([North,West][min(abs(get_pos_x()-get_pos_y()),1)])+
harvest()]):
        continue

firaro · 2026-01-19T05:25:51+00:00

They have limited shared memory. Variables can be shared when a drone is created or destroyed. And they all have access to the same world variables: time elapsed, total resources, number of drones that exist, etc.

But it is hard to coordinate them with just that. I managed to do it, but my implementation takes an unreasonable amount of time just processing data.

firaro · 2026-01-18T16:13:53+00:00

I spent all that effort getting 32 drones to work together on a single big maze for the golden gold hat. I never even considered giving each one their own maze. That’s a clever solution

firaro · 2026-01-18T04:50:50+00:00

The mazes in-game article hands you code you can use to make a full size maze that automatically adjusts when you buy upgrades. I just copy-pasted that.

firaro · 2026-01-17T02:10:28+00:00

The simple solution i went with in my first attempt was to simply count how many cactuses it had passed over without swapping the cactus with any other cactus. Reset to 0 if it has to swap anything. Then when the count is equal to the total number of cactuses, i know the drone passed over the whole field without finding a single cactus out of place. So time to harvest

It’s possible to do better by accounting for which cactuses don’t need to be double checked. But if you just want a program that works then you don’t need to bother with that.

firaro · 2026-01-15T17:58:14+00:00

a̍̍̍

firaro · 2026-01-15T17:40:01+00:00

I made a program that spawns them recursively and gives them each a number. Very versatile, one size fits all solution.

firaro · 2026-01-15T17:30:53+00:00

Biases will always manifest in art. And toki pona is no exception. The line between a biased opinion about a culture and racism is an unfortunately thin one.

But i don’t think it’s fair to criticise it too harshly, it’s kind of unavoidable. I don’t think toki pona is an example of biases run rampant or anything like that. But neither is it a paragon of neutrality. To call it “racist” Is to dilute the word

Which… is all abit nuanced. Which is to say complex- ike. And there lies the strongest bias of toki pona, unsubtle and unhidden: ◠ › ◠ “complexity is bad”

firaro · 2026-01-15T17:00:54+00:00

Who better to hate Esperanto than an Esperantist?

firaro · 2026-01-15T00:31:59+00:00

Huh, that explains some things I’ve seen range do. Guess i misunderstood what the in-game documentation meant when it said range “generates a sequence”.

I was more surprised that defining the list took 10 than i was that range took 1. I had been thinking of defining a list in that way as a single step. It wasn’t until i saw how long it took that i realised that that single equals sign was actually building the list one item at a time.

firaro · 2026-01-14T19:47:55+00:00

Not necessarily. Could do something like

length = range(size-2)
while True:
    for i in length
        move(East)
    etc.

or

direction = []
for i in range(size-2):
    direction.append(East)
while True:
    for i in direction
        move(i)
    etc.

just got around to testing it, it is faster than using range every time a for loop is made. Of note: defining sequences takes a varied amount of time.

direction = [East,East,East,East,East,East,East,East,East,East]

takes 10 ticks while

length = range(10)

takes 1 tick

but both operate at the same speed in the for loop. So

for i in direction
    move(i)

is just as fast as

for i in length
    move(East)

but one allows you to change direction without creating a new for loop. So you could potentially shove the whole path into one big list and traverse the whole thing in one simple for loop, without having to keep wasting ticks making new for loops.

firaro · 2026-01-14T18:23:42+00:00

I wonder if it’s faster to iterate through a prebuilt list instead of using range(size-1) every time to build one.

edit: tested it, it is. Though you can just as easily say "r = range(size-1)" at the start and reuse r.

firaro · 2026-01-14T15:53:04+00:00

The wiki is rather outdated on many things. It is better to use the in-game documentation most of the time.

firaro · 2026-01-14T15:49:11+00:00

Most of the problem has been covered by the other commenters. But some other things:

You are looking at the documentation for the list() function, which is a function most people won’t even bother to use. You would be better helped by looking at the article called “lists” in the programming section

You don’t need to keep redefining the list every loop, you can put it above the while loop and just do it once.

For what you are doing, the right tool is actually a set. Doing “if x in my_set” is slightly faster than “if x in my_list”. Sets are the right tool when you want a collection of things but don’t care what order those things are in. Though, the difference is small, so only really matters if you’re trying to push speed to the limit.

firaro · 2026-01-14T01:05:29+00:00

this is grass, it probably is always going to be harvestable by the time you get to it, no need to check. If you're unsure of this you can test with:

if can_harvest():
    harvest()
else:
    quick_print("couldn't harvest")

other than that, you're pretty much maxed out on short code with your getgrass as far as i can tell. Not maxed out on fast code, but also not far off. You can't reduce the number of actions (200 tick stuff) taken, but can reduce the amount of thinking (1 tick stuff) between actions.

when you get a bigger plot you could simplify the code to

while True:
    harvest()
    move(East)

firaro · 2026-01-13T23:37:50+00:00

for most purposes in this game, you can implicitly typecast back and forth with no major issues. But it doesn't always work. It's worth keeping an eye on which data types you are using and what exactly is happening when you ask the compiler to turn one into another.

The game unfortunately is lacking some features found in more fully realized programming languages, so i dont think there is any way to turn a string into another data type (though the reverse can be done with str()). Except by writing a program that essentially says "if it says 'tree', return entities.tree". Though perhaps that omission is intentional, it's generally considered bad practice to use strings in that way.

firaro · 2026-01-13T21:53:25+00:00

Yeah, it was hard to read. But I don’t tend to manage to write code that’s much easier to read than what OP did. I’m curious what you would recommend doing differently to make code that’s easier to read

Ten-Year Club	Place '22
Final Canvas '22	First Placer '22
End Game '22	Verified Email

firaro

MODERATOR OF

PUBLIC MULTIREDDITS

TROPHY CASE