ID:1415096
 
(See the best response by SilkWizard.)
The biggest issue I have with it right now is I haven't the slightest clue how to use it. Before anyone tells me to read the readmes: the readmes do not help. They outline the CSS and config options, but they do not actually say how to use the suite.

I'm utterly lost and confused as to what to do with all these files.


I get all the configuration files, I get the byondexe.exe building process, I get the installation submodule (that you can optionally download via sourceforge) but I don't get how to use it in general. I'm always feeling like I'm using it wrong.

Here's a few issues that have left me pulling my eyes out the past few hours:

- Attempting to join a server in the standalone does not work.

- I noticed I was using an outdated version. Fine, I updated, and decided to start from scratch using the same key. I rebuild everything and lo and behold it's the same content I built in the old version. What? They're not even in the same folder, how is that possible? I haven't changed anything yet. What???

- The instructions say to edit the default hub.html/css/ini. What? They don't exist!

- There is no conceivable way to edit the login box.

- Sometimes when changes are made they do not seem to have any affect, even with rebuilt countless times.

- What the hell does verpatch do?


Hopefully someone else has shared my plight and can shed some light on this.
The issue you're having is cached files. Documents\BYOND\Cache (I think...) keeps a cache of the installer's files. When rebuilding the standalone a lot you'll have to manually delete these files to see the updated versions.

As for the other stuff, not sure, I haven't had access the the standalone stuff in a while so I'm out of date on how things work now. I sure as heck can't afford to buy a key to experiment myself and write up tutorials =P


... not that I have anything to buy a key for, my only active game is MLAAS and 'helpers' don't get access to the distribution tab.
In response to Nadrew
I can't seem to find where they're cached. Are they cached in the main byond.rsc?
I think we need to make a tutorial for this so users can walk through an example. It shouldn't be this difficult to get going so I'm wondering if we have a bug in there. We'll make that a priority this week.
In response to Doohl
Doohl wrote:
I can't seem to find where they're cached. Are they cached in the main byond.rsc?

I'm probably mistaken as to the location of the files since it's been a while since I used the standalone stuff, try the 'skins' directory in Documents/BYOND instead (eg. 'Documents/BYOND/Skins/Writinganewone/Eternia')
In response to Tom
Tom wrote:
I think we need to make a tutorial for this so users can walk through an example. It shouldn't be this difficult to get going so I'm wondering if we have a bug in there. We'll make that a priority this week.


It's definitely not too tricky once you get the hang of things, but I do recall being totally lost in a few places and having to ask you about specifics. A nice robust tutorial explaining every aspect of it would be pretty awesome.

Best response
Here is a copy/paste of some basic instructions that I emailed to someone else last week about how to get the standalone tools to actually compile something. From that point it's just a matter of editing the hub.css and hub.html files.


Silk wrote:
I sat down this morning and downloaded a fresh copy of the byondexe files to give you directions starting from a blank slate. Here are the steps:

1) First you need to open the 'byondexe.ini' file and copy/paste the code that Tom gave you where is says "KEY_FROM_BYOND"

2) On the third line change 'include = setup/cfg, setup/skin, setup/rsc' to just say 'include = setup/skin'

3) Save the file and close it.

4) Open up the "setup" folder and delete the "skin" folder, then rename the "cfg" folder to "skin".

After doing that, clicking on the 'byondexe.exe' program should compile a basic version of the standalone client as 'game.exe'. The problem was that the 'byondexe.ini' file causes the compiling to fail if it tries to look for folders that aren't there.
Oh snap, if our default setup isn't compiling out of the box, that's a problem. We'll fix it. Thanks for the pointers everyone.

Also, this should help a lot more when everyone has access to a key to test.
Thanks guys, a lot of this stuff really helps!
Though I'm still having trouble with the standalone not refreshing when rebuilt. I can't find the files that I need to delete to show the latest changes.
I cannot see any changes I make to the standalone html pages; this is apparently because I need to delete the cache file(s). Where are they? Deleting the cache files normally doesn't help.
Did you look under Documents\BYOND\Skins\writinganewone like I suggested previously? That seems to be where my old standalone cache stuff from Eternia is sitting right now.
Yeah, I did, I even deleted the entire Skins folder and the old content is still being pulled from somewhere.

EDIT: seems like I overlooked the Documents\BYOND\bin folder, because that's where everything is being kept it seems.
Ah yeah, I didn't even think to look there. I see the files there too, I guess I had them in Skins/ for some other reason.
I've finally got something presentable made, after a lot of wrestling with the system and trying to get things to work.

We've got it over at: http://www.pixel-realms.net/play/


It really shouldn't have been this hard to get it to work, but that's probably just because it was lacking a guide. I think if there was a legitimate guide to getting the standalone up and running I would've had no issues whatsoever with this!
In response to Doohl
"cubersome"
In response to Vrocaan
Eternia is in the preparatory process of advertising the game. Most non-BYOND users do not want to install a bunch of "shady" software to play some game that they found on the internet. They just want to download and play the game itself.

Although cubersome might've been the wrong word in that situation :P
In response to Doohl
My point was that it was misspelled.

see: cumbersome
In response to Vrocaan
Oh wow. Oops, guess I need to pick up a dictionary!
We'll improve this process. I honestly had no idea that there were this many issues. I have to believe we messed something up in one of the release iterations as I know I tested a "dummy" exe with our default includes and it launched without problem.

So we'll take a look and provide better documentation so this is easier in the future.
Page: 1 2