Clear credit for my teammate’s Pasur
There is one point I want to make clear at the start of Dalo’s development story: my teammate wrote Pasur’s game implementation. I built the shared card core and the other parts I describe in this collection of articles, but Pasur is my teammate’s distinct contribution to the project. That difference should remain visible when I talk about Dalo as a collection. For me, a shared result and credit for individual parts belong together. The player should see a coherent application, while several people may have worked on different pieces behind that experience.
A shared foundation for independent work
One reason for building the core was to avoid rebuilding everything for later games. Cards, player hands and turns have a shared foundation, while each game’s rules need their own place. That approach takes on a more practical meaning when another person’s work enters the project. It needs to be clear which part belongs to the game and which parts come from the shared project. Pasur is more than another name in the menu for me. It shows how a collection can grow from several streams of work without attributing every game to one rule set or one author.
Pasur’s place in the collection
Pasur has its own separate area in the project, alongside checks related to its integration. That structure helps me describe contributions more precisely. A game’s place in the project does not establish every detail of a final release, so I am not adding new claims about unverified Pasur features here. What I want to explain is its place in Dalo: a game implemented by my teammate, connected to the collection’s shared parts. The menu and surrounding experience should make that collection understandable to players without requiring them to think about the project’s internal boundaries.
A personal story and a shared result
Writing this article gave me a chance to make my personal development story more precise. Stages such as building the core or Hokm directly describe my own work. Pasur’s story is one of collaboration, and that should stay in the text. I want readers following Dalo’s development to see the shared decisions and understand where each contribution came from. Explaining teamwork does not require making everyone’s contribution identical or unclear. Dalo brings together different games and systems, and Pasur belongs to that collection. Start from the Dalo page to explore the rest of the path.
