I'd like to see in the upcoming version that you can type like...
"dreamseeker.exe " c:\mygame\gamey.dmb 1337 -trusted
Where c:\mygame\gamey.dmb is the gaming, 1337 is the port, and -trusted indicates it must go under trusted mode.
It will use the standard key [if there is one]. If there is none, it will return 0 and close the dreamseeker program.
There should also be a -minimize option, so it can start in the background.
Main purpose for this is to keep a game up 24/7 not using Daemon [in case the host plays the game as well, it has been showing a problem to connect to localhost, espessially if you're on a router].
The shell("dreamseeker.exe c:\mygame\gamey.dmb 1337 -trusted") does the same effect.
However. OpenPort should be changed.
OpenPort(port,options,etc..)
Same as startup() [with the options] but instead it opens a port on the current game on dream seeker. This way, you can change settings etc.
Please post your comments about my idea. I'll look forward to it, but now I must watch TV. There's a Star Trek Marathon going on. ;)
ID:259760
Jun 9 2004, 1:24 am
|
|
In response to Lummox JR
|
|
Main purpose for this is to keep a game up 24/7 not using Daemon [in case the host plays the game as well, it has been showing a problem to connect to localhost, espessially if you're on a router]. I do know how to configure my router. But my dad password protected it and is not giving me access. Besides, I'm not allowed to 24/7 host anyway. I cannot connect with my external nor my internal, and it isn't my router. Even computers without any routers at all couldn't connect to themselves via BYOND. |
In response to Phoenix Man
|
|
Only some people have that problem. Occasionally I am blocked from joining things I host, but after trying over and over it usually lets me in. Usually though, I have little to no problem.
You could ask your father to allow you access to the router, telling him what you wish to do. Also, you could reset it so that the password returns back to the factory default; but he probably would not like that. |
In response to Phoenix Man
|
|
Phoenix Man wrote:
I cannot connect with my external nor my internal, and it isn't my router. Even computers without any routers at all couldn't connect to themselves via BYOND. Yes they could. I have a link set up to do it. byond://127.0.0.1:2500 Lummox JR |
In response to Lummox JR
|
|
Lummox JR wrote:
1337 is a pretty poor choice for a port; it's rather low. My own default of 2500 is really too low. I use 1029. (It's quick to type.) =D |
In response to Crispy
|
|
Anything above 1023 is pretty safe to use. Under 1023, and especially under 255 is bad to use. IF you're the paranoid type, use a number over 5000. The 1024-5000 range is pretty safe, and not a poor choice at all.
|
In response to OneFishDown
|
|
on my shell server i use port 1551.
|
In response to Lummox JR
|
|
1337 is a pretty poor choice for a port; it's rather low. My own default of 2500 is really too low. I host (once in a blue moon) on port 1750, and I consider it perfectly safe. |
1337 is a pretty poor choice for a port; it's rather low. My own default of 2500 is really too low.
Sounds like you don't know how to configure your router. There should be no problem at all connecting to yourself; it should be vastly easier. You can use 127.0.0.1, your internal network IP address, or the externally visible IP address to connect.
It's not a good idea to give the game control over the settings. The only thing the game can touch is the port, which doesn't leave it free to go into, say, trusted mode, without the host's approval. I do like the idea of adding more command-like options for DS, although this strikes me as doable through a byond:// link, too.
Lummox JR