ID:163460
 
Well I have a question for anyone that thinks they are up to attempt to answer it. Seeing as BYOND 4.0 doesnt support 3.5 clients (BAD) I have been looking for a way to get some of 4.0 options into the 3.5 game.

So heres my question I know that its impossible to compile a 3.5 game to have a dmf an still have the 4.0 clients see this file an use it when hosting from a 3.5 server.

So this is my question seeing as its possible to check what version of byond you are running is it possible to set it up so if a 3.5 client connects it runs normal an if a 4.0 client connections it checks the users computer to see if it has a dmf file if it doesnt it will connect to a temp 4.0 server or even a website download the dmf save it to the hard drive an disconnect them an tell them to reconnect if its a 1st time download then when they reconnect to the 3.5 client it will load the dmf file from the users save dir if they are on a 4.0 client an load the skin.

If this is possible anyone wanna throw a fix hints or examples my way? XD Im playin with it a bit myself but yah I dont have that much free time. The whole point of this post really though is to see if its possible the help is nice if anyone wants to offer but not needed an if its possible this be something everyone would use because honestly I dont see myself update to 4.0 until it can atleast support 3.5 clients an older just because people will wanna play an might not wanna update.
Ac19189 wrote:
Well I have a question for anyone that thinks they are up to attempt to answer it. Seeing as BYOND 4.0 doesnt support 3.5 clients (BAD) I have been looking for a way to get some of 4.0 options into the 3.5 game.

It's not bad, just life. That's like saying it's bad that you can't run BYOND on an old NES. BYOND 3.5 simply can't run 4.0's games. There is the matter, as Tom brought up, of 4.0-based servers running 3.5 games, which 3.5 clients still can't connect to. The reason is the 4.0 server would have to go through a lot of contortions to talk properly with a 3.5 client, so it's not an especailly feasible thing for us to support.

So heres my question I know that its impossible to compile a 3.5 game to have a dmf an still have the 4.0 clients see this file an use it when hosting from a 3.5 server.

Right, for two reasons: 1) 3.5 doesn't know the skin is there or how to tell the client about it, and 2) routines needed to interact with it like output() and winset() don't exist in 3.5.

So this is my question seeing as its possible to check what version of byond you are running is it possible to set it up so if a 3.5 client connects it runs normal an if a 4.0 client connections it checks the users computer to see if it has a dmf file if it doesnt it will connect to a temp 4.0 server or even a website download the dmf save it to the hard drive an disconnect them an tell them to reconnect if its a 1st time download then when they reconnect to the 3.5 client it will load the dmf file from the users save dir if they are on a 4.0 client an load the skin.

Um, that's not a question; it's a paragraph run through a compactor. I have no idea what you just said. There are like 6 sentences there begging to escape from each other.

Lummox JR
In response to Lummox JR
ROFL Is it possible to have a 3.5 game check what version you are running then if you are running a 4.0 client it will connect you to a 4.0 server that will then save a dmf for the game in the game folder then when you connect to a 3.5 game using a 4.0 it will check to see if you have the dmf if you do it will load as the default skin for that 4.0 client from a client side location.

What I want to know is if a game is coded right in 3.5 is it possible so if you are running a 4.0 client in a 3.5 game it can check the version number an tell the 4.0 client to load a dmf skin on the fly from the users hard drive so long as it was downloaded.
In response to Ac19189
ROFL Is it possible to have a 3.5 game check what version you are running then if you are running a 4.0 client it will connect you to a 4.0 server...

If you mean that you have two known servers up, than sure... all you have to do is send the 4.0 users to the other server and you can check the client version via client.byond_version()

If you mean running their own server, it will check if it is 4.0 and load the DMF while leaving 3.5 as is... it won't work that way. The 3.5 DM (which produces the host files, of course) is not compiled for 4.0, that includes how to use the DMF and all the new stuff like alpha and new procs.