//
sign in
Profile
by @danabra.mov
Profile
by @dansshadow.bsky.social
Profile
by @jimpick.com
AviHandle
by @danabra.mov
AviHandle
by @dansshadow.bsky.social
AviHandle
by @katherine.computer
EventsList
by @katherine.computer
ProfileHeader
by @dansshadow.bsky.social
ProfileHeader
by @danabra.mov
ProfileMedia
by @danabra.mov
ProfilePlays
by @danabra.mov
ProfilePosts
by @danabra.mov
ProfilePosts
by @dansshadow.bsky.social
ProfileReplies
by @danabra.mov
Record
by @atsui.org
Skircle
by @danabra.mov
StreamPlacePlaylist
by @katherine.computer
+ new component
Profile
Loading...
Working on Cyclopean II: The Dreamlands https://store.steampowered.com/app/3998510/Cyclopean_II_The_Dreamlands/
MKSchmidt







Loading...
I keep going back and forth between these ideas and it is causing my workflow to suffer.
Thanks! I'm glad we had this talk.
I am caught in a little design quagmire of sorts. I am making several cities for my game. Part of me wants to complete each city before moving on to the next. Another part thinks it will be better to approach them more like an assembly line... #gamedesign
The second approach seems more logical. The first seems more tedious. But I think the first approach might result in more unique environments that feel more organic and intriguing.
I think I will start by making them each, singly. If that becomes too burdensome, I can always resort to the assembly line approach later.
While working on Cyclopean II: The Dreamlands, I am often reminded of the trope in which people just add #tentacles to make things more #Lovecraftian. Since the Dream-Quest mentions cabbages being one of the products of Ulthar, I offer you ... the Cabbage Beast! Look not, for it drives men mad!
So first do all the buildings fore each city, then all the NPCs, then all the quests, etc...