Found this on the BYONDiscord
In response to Legobumb
Legobumb wrote:


Found this on the BYONDiscord

To add some context to this post: This was a summary of multiple peoples' points and some napkin math that was done based on bullshit and no statistics.

I wrote the summary of what was discussed. The gist of it is pretty much my take, and Lummox has stated that some of the math is wrong.

Essentially, his main issue is that the lack of a membership incentive for the players of a game published with an ad-free exe may wind up offsetting the revenue gained and be a net loss. However, he has responded positively to the idea of membership itself being the means behind which you could build an exe, and that exe would still have a splash screen at the open as a membership incentive with the option to play an ad from an external webpage when that functionality is restored.

His concerns are mostly at this time with the revenue loss of the lack of membership clickthroughs from the players of games published with the tools.
In response to Multiverse7
Multiverse7 wrote:
Yes, and that would constitute a separate, public tier, as opposed to the private one that comes with Steam integration

Again, this is not how Steamworks is integrated in BYOND. Nothing requires BYONDexe as far as steam is concerned. Easier to use, yes, required, no.

The functionality that provides communication between DM and the steamworks api (read: steam integration) is available as a part of the language. It’s not gated behind the exe tool at all.
In response to F0lak
I know that you have personal experience working wth BYONDexe for your game, so I will take your word for it.

In that case, the reference seems to be more than a little misleading on this issue.

From the client.GetAPI() reference page:
Interfaces with supported external APIs to read information. Currently this only has meaning for Steam, for specially built games that have a Steam app ID.

Requires that the server and client are using a valid Steam app ID, such as when a game is built for standalone distribution.

From the client.SetAPI() reference page:
Interfaces with supported external APIs to write information. Currently this only has meaning for Steam, for specially built games that have a Steam app ID.

Requires that the server and client are using a valid Steam app ID, such as when a game is built for standalone distribution.

From the client.CheckPassport() reference page:
You can use this with other APIs that are supported by BYOND, which currently only applies to Steam and only if the game is specially built for Steam support.

As you can see, there are numerous references to specially built games, suggesting that might be the only way to use these features. Is there really just an undocumented command-line argument behind all of this?
compile2exe would bring me back into development. i would pay money for this feature, i like the idea of a $100 lump sum or something to use this.

having to guide my testers to take additional steps to test my games sucks. compile2exe would solve this and allow for faster, easier testing and speed up development time.
In response to Multiverse7
The engine has those features, and while the current BYONDexe handles the integration for you within the files it creates and installs, it’s doable with a home brewed standalone as well.

In other words, BYONDexe makes it simple to interface with steam, but it’s by no means the only way to utilize those features. They are not safeguarded behind BYONDexe in any way, in the same way that vscode doesn’t safeguard any of BYONDs native features. It’s a tool, that’s all.


Yo, bump up the jam, bump it up
A-bump it up, yo, bump it
Bump up the jam, bump it up
Bump it, Bump it, Bump it, yeah
Okay, real talk. This is the single most requested feature that this engine has ever had, it’s been in the engine previously, and the current solution is an obscure heap of garbage that’s nigh unusable. It’s been discussed at length, it’s been said how easy it will be to implement, but for some reason it keeps disappearing and the conversation dies out. Is there any sort of timeline to expect this long overdue feature to be added to the engine?
I agree that having this feature directly integrated and signed by BYOND would enhance the safety and convenience of sharing game files among developers. It could also encourage growth within the developer community.
While I understand potential concerns about monetization, making this feature accessible to all developers could greatly benefit the platform.
Offering a Build to EXE feature would make BYOND games more accessible to a wider audience, potentially expanding the player base for developers, and the customer base for BYOND Memberships as a result.
In response to F0lak
F0lak wrote:
Okay, real talk. This is the single most requested feature that this engine has ever had, it’s been in the engine previously, and the current solution is an obscure heap of garbage that’s nigh unusable. It’s been discussed at length, it’s been said how easy it will be to implement, but for some reason it keeps disappearing and the conversation dies out. Is there any sort of timeline to expect this long overdue feature to be added to the engine?



As noted elsewhere, Lummox isn't going to touch it until he has a way to monetize it better, this means making the ads work again, and that means webview2.

There's also nothing that says he's planning to improve how BYONDexe works, which is fine, it works perfectly fine for what it's meant to do, it's just poorly documented and doesn't have many working examples to look at. Eternia's BYONDexe setup is pretty clean and easy to work with.
In response to James
James wrote:
As noted elsewhere, Lummox isn't going to touch it until he has a way to monetize it better, this means making the ads work again, and that means webview2.

There's also nothing that says he's planning to improve how BYONDexe works, which is fine, it works perfectly fine for what it's meant to do, it's just poorly documented and doesn't have many working examples to look at. Eternia's BYONDexe setup is pretty clean and easy to work with.


Making ads work in BYONDExe?
I get it, on a personal level, the developer of the engine needs money to keep it going, and has been making this his primary focus for the better part of a decade, in the hopes of providing

But this is not how we go about doing it. This would take away from the end-user experience, not only would they need to purchase a one-year membership to bypass ads at $24, but this would in no-way support the developer of the game. 100% of the profits from this sale would go directly to the engine that provides the developers a platform.

Why not follow-suit of other game engines, introduce tiered levels of support / development? charge a % off of sales..

Don't force ads.
Page: 1 2 3 4 5