On Mon, 29 Apr 2024 17:38:17 +0200
"Sebastian Reitenbach" <sebas...@l00-bugdead-prods.de> wrote:

> On Monday, April 29, 2024 17:15 CEST, "Sebastian Reitenbach"
> <sebas...@l00-bugdead-prods.de> wrote:
> 
> > Hi,
> > 
> > 
> > On Sunday, April 28, 2024 23:53 CEST, Thomas Frohwein
> > <tfrohw...@fastmail.com> wrote: 
> > > On Sat, Apr 27, 2024 at 08:53:31PM -0500, izder456 wrote:  
> > > > Ohp, minor typo in files/classicube.desktop
> > > > 
> > > > fixed tarball is attached.
> > > > 
> > > > Best-
> > > > 
> > > > -- 
> > > > -iz (they/them)
> > > >   
> > > > > i like to say mundane things, 
> > > > > there are too many uninteresting things 
> > > > > that go unnoticed.  
> > > > 
> > > > izder456 (dot) neocities (dot) org  
> > > 
> > > Tested it in singleplayer only, builds and runs fine. I don't
> > > really know how to play, but looks good. ok thfr@
> > >   
> > 
> > When I try to start it, just tested single player mode, it bailed
> > out on me: Error 2 when starting game
> > Error meaning: No such file or directory
> > 
> > And that's what I saw on the CLI:
> > [55310:-1862911424:0429/170327.885904:ERROR:bus.cc(407)] Failed to
> > connect to the bus: Failed to connect to socket
> > /var/run/dbus/system_bus_socket: No such file or directory 
> 
> even with that messagebus started, same as above.
> However, I used the classicube_run to start the game, also when
> starting classicube_run multiple times, it recreates font cache and
> downloads missing pieces from the Internet every time.
> 
> Just using classicube does the trick as it seems. Whatever
> classicube_run is good for ;)
> 
> Sebastian
> 

classicube_run is the binary itself, whereas classicube is a wrapper. 

classicube downloads assets to the CWD on first run, so I opted to make
a small wrapper script that downloads the assets to a place that is
writable to a normal user. (see files/classicube)

-- 
-iz (they/them)

> i like to say mundane things, 
> there are too many uninteresting things 
> that go unnoticed.

izder456 (dot) neocities (dot) org

Reply via email to