Hello everyone. It was quite a long time since my last post (over 3 years!), isn't it? Anyways, I think that I plan on getting back to PICO-8 and try to make a game. Again. I already have an idea in my mind what I will make so it would be pretty much impressive, especially after so much stuff that was discovered and added in this amazing fantasy console.
Also Picotron looks really interesting even at such early state. Though, I currently have neither money (not that I'm broke, just I barely became 18 and don't have too much time and energy even for part-time) and patience (few last years kinda damaged my mental health, I think) and time (because I have final exams to prepare for and pass, since I want to go to university) to afford it.
Also I want to change my PFP from Mortis to something else. And maybe should try to make a REAL game for Steam release.
Oh, and my English got majorly improved as well since then!
Anyways, thanks for reading.

A simple CGoL in a 32x32 grid.

Controls:
Use the mouse to select the cell
LMB - activate/deactivate cell
Z - switch between activate/deactivate mode
X - play/pause the simulation
Up/Down - increase/decrease simulation speed

yet_another_cgol

by manumendo

Cart #yet_another_cgol-0 | 2025-01-29 | Code ▽ | Embed ▽ | License: CC4-BY-NC-SA

3

If you're unfamiliar with the Game of Life, here are some cool patterns you can make in it:

The pulsar

This is called Penta-decathlon

You can even make these... spaceships? Just google it

Or you can scribble whatever you want and see what happens

[ Continue Reading.. ]

hello guys! I have used Pico-8 alot but i never made an account, but now's the time! Unfortunately i cannot publish my own games until i buy Pico-8 on my laptop one day, so this post and later ones will be on my tablet!

What i do with this account:

all i do is just give a short but good review of the games that i bookmarked on my tablet! Literally that's all i do, ok?

• item 1

  Inicializar o tabuleiro vazio (8x8)

  tabuleiro = criar_tabuleiro(8, 8)

Gerar as primeiras 3 peças

pecas = gerar_pecas_iniciais()

Variáveis de controle

pontuacao = 0
fim_do_jogo = False

• item 2
  def criartabuleiro(linhas, colunas):
  return [[' ' for in range(colunas)] for _ in range(linhas)]

def exibir_tabuleiro(tabuleiro):
colunas = 'ABCDEFGH'
for i, linha in enumerate(tabuleiro):
print(f"{colunas[i]} " + " ".join(linha))
print()

• item 3
  def gerar_pecas_iniciais():
  pecas_possiveis = [
  [(0, 0), (0, 1), (0, 2)], # Linha reta
  [(0, 0), (1, 0), (2, 0)], # Linha reta vertical
  [(0, 0), (1, 0), (1, 1)], # L
  [(0, 0), (0, 1), (1, 1)] # T
  ]
  return [random.choice(pecaspossiveis) for in range(3)]

• item 4
  def posicionar_peca(tabuleiro, peca, linha, coluna):
  if not verificar_espaco(tabuleiro, peca, linha, coluna):

[ Continue Reading.. ]

• item 1

  Inicializar o tabuleiro vazio (8x8)

  tabuleiro = criar_tabuleiro(8, 8)

Gerar as primeiras 3 peças

pecas = gerar_pecas_iniciais()

Variáveis de controle

pontuacao = 0
fim_do_jogo = False

• item 2
  def criartabuleiro(linhas, colunas):
  return [[' ' for in range(colunas)] for _ in range(linhas)]

• item 3
  def gerar_pecas_iniciais():

  Definir os formatos das peças (por exemplo, L, T, quadrado, linha)

  pecas_possiveis = [
  [(0, 0), (0, 1), (0, 2)], # Linha reta
  [(0, 0), (1, 0), (2, 0)], # Linha reta vertical
  [(0, 0), (1, 0), (1, 1)], # L
  [(0, 0), (0, 1), (1, 1)] # T
  ]
  return [random.choice(pecaspossiveis) for in range(3)]

• item 4
  def posicionar_peca(tabuleiro, peca, linha, coluna):
  for (dx, dy) in peca:
  if tabuleiro[linha + dx][coluna + dy] != ' ':
  return False # A peça não pode ser colocada aqui (colisão)

[ Continue Reading.. ]

Feature Suggestion: Cart Forking and Collaboration

I wish there was a way to track when a cart from the BBS is improved or modded or altered, linking it back to the original in some way. This could function like a "fork," showing all variants and allowing users to see the evolution of a cart over time.

With this feature, we could collaboratively work on adding features and fixing bugs, even through small individual contributions. Over time, these efforts would add up, leading to polished and feature-rich games and software.

Isn’t that the beauty of open-sourcing carts? A system like this would make it easier for the community to come together and create something truly amazing!

Feature added:

• Added more shading on sprites
• Added "wasd" + "e" + "space" as optional keyboard control

source: https://www.lexaloffle.com/bbs/?pid=151689#p

YO

i wanna get back into gamedev sometime this year, or at least try to, and this little thing seems the perfect way to start that journey.
unfortunately i dont know how to change my username, so this accounts name will forever reflect a 12 year old pipo, one with foolish ambitions and thought they wouldnt be a girl in the future lol
this is just me yammering. i wont post much and its unlikely anyone will see this but, sometimes its nice to talk out in the void

This Lua script is designed to copy files from a directory in /appdata/system/lib to the corresponding destination in /system/lib. The key functionality of this script allows the user to modify the system libraries (e.g., gui_ed.lua in this case) in /appdata/system/lib and have those modified versions persist even after a reboot.
Key Features:

Directory Syncing:
The script checks for files in the /appdata/system/lib directory.
It copies each file to the matching location in /system/lib based on the filenames. For example, if gui_ed.lua is modified in /appdata/system/lib, it will be copied to /system/lib/gui_ed.lua replacing the original.

Persistence of Edits:
Any changes made to files in /appdata/system/lib will persist after reboot, ensuring that the customized libraries remain intact and are used when the system restarts.

Works with Any /system Directory:
The script can be adapted to copy files from any directory within /appdata/system to the equivalent directory in /system, not just /lib. It can be used to update any files in the /system/ directories by making minor changes.

[ Continue Reading.. ]

One of my biggest takeaways from this project is the concrete understanding of the dangers of Feature Creep, as well as the importance of having realistic project expectations and proper planning. In software development, it’s inevitable to encounter bugs and features that need to be adjusted based on real-world scenarios. These tasks take up a significant amount of time, which is often unpredictable. Therefore, it is essential to allocate sufficient time for debugging and adjustments, instead of continuously trying to integrate new features into the program.

Moreover, the dangers of Feature Creep were vividly demonstrated in this project. In my past programming experiences, I rarely paid attention to the memory usage of the program. As a result, I often wrote code with higher readability and decoupled various modules to make them easier to modify and debug. However, this approach inevitably led to code bloat, which I didn’t consider a problem until now. Given the limited code capacity of the Pico-8 engine, I encountered memory issues during the final stages of the project and had to spend extra time trimming down my code. Fortunately, I realized the problem of Feature Creep midway through development and decided to cut half of the planned levels and monsters. Otherwise, the memory constraints would have caused even more headaches.

[ Continue Reading.. ]