Allow only one instance of BYONDexe??

ID:1123510
 
Jan 12 2013, 5:22 pm
Is there currently a way to only allow one instance of a BYONDexe open at a time?
Jan 12 2013, 7:38 pm
For different BYOND games, I don't think you can.

For an online game, you can check the client's computer_id upon logging in to disable multikeying.
Jan 12 2013, 8:03 pm
In response to Jemai1
Jemai1 wrote:
For different BYOND games, I don't think you can.

For an online game, you can check the client's computer_id upon logging in to disable multikeying.

I mean for the actual EXE.
Jan 12 2013, 9:44 pm (Edited on Jan 12 2013, 11:20 pm)
But byond.exe is the pager, no? You can't have more than one instance of that.

EDIT: If you mean the standalone installer, forget what I said.
Jan 13 2013, 5:24 am
It isn't possible to play two characters on Diablo 3 on the same computer, for example. Sure you could prevent multiple clients from the same ip or something, but then the launcher can still be opened more than once.
Jan 13 2013, 7:52 am
I haven't tried BYOND's launcher but you can either request it or make your own launcher that will in turn use BYOND's.

You can make a simple .exe that will call BYOND's but first it'll do every action/check you require.

While it's a bit more complicated it allows you a bit more control over some features.
My launcher (C#) for example can automatically update BYOND, trigger top-most and other graphic features.

If you do decide to take this option, you can page me for further help.
Jan 13 2013, 9:39 am
In response to Rotem12
Rotem12 wrote:
I haven't tried BYOND's launcher but you can either request it or make your own launcher that will in turn use BYOND's.

You can make a simple .exe that will call BYOND's but first it'll do every action/check you require.

While it's a bit more complicated it allows you a bit more control over some features.
My launcher (C#) for example can automatically update BYOND, trigger top-most and other graphic features.

If you do decide to take this option, you can page me for further help.


Are you suggesting embedding the byond launcher inside another launcher. And then doing mutex check.
Jan 13 2013, 9:58 am
Not exactly what I suggested but if that idea works, go for it, same result.
Jan 13 2013, 9:59 am
In response to FIREking
FIREking wrote:
Are you suggesting embedding the byond launcher inside another launcher. And then doing mutex check.

Rotem's launcher runs dreamseeker.exe directly, not the BYONDexe launcher.
Jan 13 2013, 10:01 am
In response to Murrawhip
Murrawhip wrote:
FIREking wrote:
Are you suggesting embedding the byond launcher inside another launcher. And then doing mutex check.

Rotem's launcher runs dreamseeker.exe directly, not the BYONDexe launcher.

What is "Rotem's launcher?" and where can I check it out?
Jan 13 2013, 10:10 am
In response to FIREking
FIREking wrote:
What is "Rotem's launcher?" and where can I check it out?

Rotem really wanted to have interface transparency in her projects without forcing software rendering, something that BYOND isn't able to do. So she used a WinAPI call to do the transparency, and it worked without forcing software rendering.
Obviously she can't expect people to run some random program alongside her BYOND games separately, so she made it into a launcher that runs dreamseeker, and keeps itself hidden but open while the game is running, so that new windows can have the transparency applied as needed.
That was the main reason for the launcher, but obviously you can do other things like keeping BYOND updated, making interface windows stay 'on top', etc.
The launcher isn't in public use right now - the game that used it is offline.