Author Topic: RTB Development  (Read 383713 times)

About how far of a push back? Week? Weeks? Month? Months?
Asking a developer how long it's going to take to get something done is like asking an insomniac when he's going to go to sleep.

About how far of a push back? Week? Weeks? Month? Months?

Probably a week or two.

Asking a developer how long it's going to take to get something done is like asking an insomniac when he's going to go to sleep.
Meh, just looking for a rough estimate.

If the random crashing is a C++ error, then it's not RTB's fault most likely. I have the same problem hosting servers and even when on a server.

If the random crashing is a C++ error, then it's not RTB's fault most likely. I have the same problem hosting servers and even when on a server.

He says there's some problem with the current build of Blockland which causes random crashes. This could either be a source code problem, or some compiled code that he'd rather avoid modifying or can't in the correct fashion without simply revealing a ton of it.

I like how when you click the rtb logo it links you to a fish.

I like how when you click the rtb logo it links you to a fish.

Slowpoke, sir. Major slowpoke...

I like how when you click the rtb logo it links you to a fish.
I like how you're late.

so wats goin on in dis here topic.

RTB Authentication Error, what?

RTB Authentication Error, what?
Because the master server is having trouble.

Because the master server is having trouble.

I would expect the message from Blockland itself and not RTB.

I would expect the message from Blockland itself and not RTB.
RTB tells you that the RTB webserver can't talk to the master server.

RTB tells you that the RTB webserver can't talk to the master server.

So true.

The crash bug is looking like an obscure engine issue related to how the global accelerator map for gui controls manages it's function/method pointers so a fix may be a way off - I don't know how much time Badspot has to look into it.

In the meantime I'm going to try out a considerable hack which I suspect will bypass the issue. I'm reluctant to push something out as a beta which causes crashes consistently - so until I can confirm this crash is sorted (or atleast mitigated) there probably won't be a beta.