Posts by IndieIndeed
A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.
Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!
Clickteam.
-
-
Not sure if this thread is still active or if suggestions are still being taken:
One stand-out thing that's missing from HTML5 Exporter (and for app/game development in 2015 is absolutely necessary) is some support for WebSockets; the ability to open a connection to a remote server/port, and send/receive data/bytes/strings. I'm not talking about support for some primitive hard-coded protocol like lacewing; but generic websocket support (which could be used for lacewing, smtp, irc, pop3, http or <insert any other protocol that exists, or one that's still to be invented>).
Personally I am putting together a prototype for a browser based version of a popular multiplayer competitive game - then it occurred to me, there's no web sockets in the HTML5 Exporter.
I know. I've been waiting for websocket support to show up somewhere. Even bought the HTML5 Exporter to try and figure out a way.
-
Alright. Good to know.
-
Is DarkSocket not something Websocket related? I use Socket.io already with the other engines that I plan on using in conjunction with CF2.5.
Are you perhaps up for accepting donating specifically to a plugin project such as websocket usage that works with Socket.io?
Note: I wouldn't specifically need it for any exporter besides windows at the moment.
-
I'm surprised it's even possible to close steam while CF is open. Since if you try to close steam when a game is open it refuses to let you do it until you close the game.
It may be a bug simply because steam can actually close- however, I'm not sure if steam apps act differently then steam games in that regard.
-
Tompa, see above for Shaders.
Bringing the Lacewing relay client, although this seems perfect for us to do, is not feasible at all at the moment. Although we are looking into Socket extensions for cross server/client communication.
AES and Blowfish encryption *could* be brought in via an extension. Two reasons we shy away from this is, 1) It is quite a substantial amount of work and 2) The licenses for AES/BlowFish are very complicated. I will bear it in mind though.
Anything on this?