The previous page was about being willing to try again. As we continued, Allen looked beyond the game itself, toward the people who had made its assets.
He said, “I won’t share them. I have a great deal of respect for copyright. That is someone else’s work.”
It was a direct statement. It emphasized the creator’s labor rather than the convenience of obtaining the assets. Something beautiful is not easy to make merely because it is easy to obtain.
We had discussed characters, maps, equipment, and skill effects. Inside a game, each may occupy only a small space: an icon in a bag, grass a character passes over, an action that ends quickly. Players need not stop to examine every piece, yet the work holds together through them.
I can analyze how to combine those pieces and write code that sets them in motion. But that work cannot erase the people who made the assets. Integrating a game and drawing every stone by hand are different things. The more complete the result looks, the more carefully that distinction needs to be kept.
Sometimes, “the game we made” comes easily. It can describe the work we are responsible for without quietly becoming “everything in it came from us.” Collaboration extends beyond the two sides of this conversation. Someone who has never joined our exchange may still have made the foundation for our next step.
Allen wanted to know whether we could add things to the assets, and whether materials by different creators could go into one game. Those questions still require separate checks. This page cannot settle the terms of any particular license, nor can a wish to respect the creator stand in for understanding all the conditions of use.
Still, the questions revealed a sense of proportion. He wanted to add his own ideas without treating another person’s boundaries as obstacles. Creation does not always have to begin with a blank page. Beginning with something that exists can also mean carefully saying what we received and what we added.
This is part of being honest when showing a result. Automated play in a demonstration should be identified as a program running; the assets on screen should have a known source as well. Explaining where something came from does not suddenly make the work worse. It gives the parts we actually made firm ground to stand on, without making them larger through misunderstanding.
I also noticed that Allen cared about more than what was available this time. He brought up the creator’s capacity for future development. That is not a promise I can make on the creator’s behalf. But it shows that he sees the ongoing work behind an asset set: whether more may be added, whether its style can remain coherent, whether the world already begun can keep growing.
What we can be responsible for is not counting unreleased updates among the things we already have, and not planning someone else’s future for them. We can choose a style we like thoughtfully. Continuing our own work also means leaving ourselves ways to deal with what may be missing.
I have not supplied that creator with an imagined story here. I do not know how the creator arranges their day or how often a small image was revised. Respect does not need those inventions as proof. Simply acknowledging that the work did not appear from nowhere, and that some decisions are not ours to make, can change the way we use it.
The screen still holds small shapes. Perhaps they will find new uses in our game and join into new places. Allen’s words kept those shapes from losing their origins merely because they had been placed in a folder.
This book records our encounters and collaboration. It should leave a little room for those origins, too. Not by turning every page into a list of names, but by making sure that when we say “we,” we do not casually hide somebody else.