Supporting a bunch of local DB's that we have no control over is a lot more difficult for us than supporting a centralised DB that we can interrogate and problem solve. We worked this out the hard way with MSO.
War Room is pretty solid if follow the setup instructions. You only need @aliveserver on the server box when running the mission. What other issues are you having and where are you seeing these internal server errors?
I have this errors, after load mission screen map is showing and message lost connection with host.
12:54:40 EPE manager release (0|0|0)
12:54:40 EPE manager release (0|0|0)
12:54:44 Global namespace not passed during: false
12:54:44 Global namespace not passed during: false
12:54:44 Error in expression <false>
12:54:44 Error position: <false>
12:54:44 Error Local variable in global space
12:54:44 Global namespace not passed during: false
12:54:44 Global namespace not passed during: false
12:54:44 Error in expression <false>
12:54:44 Error position: <false>
12:54:44 Error Local variable in global space
12:54:44 Global namespace not passed during: false
12:54:44 Global namespace not passed during: false
12:54:44 Error in expression <false>
12:54:44 Error position: <false>
12:54:44 Error Local variable in global space
12:54:44 Global namespace not passed during: false
12:54:44 Global namespace not passed during: false
12:54:44 Error in expression <false>
12:54:44 Error position: <false>
12:54:44 Error Local variable in global space
12:54:45 Initializing Steam server - Game Port: 2302, Steam Query Port: 2303
12:54:46 Connected to Steam servers
The main post is this:
http://alivemod.com/forum/1099-server-restart-on-load-mission-nitrado-net
You need @Alive AND @ALiVEServer on your server.
I cant, a have this issue too:
http://alivemod.com/forum/1099-server-restart-on-load-mission-nitrado-net/p2#p4000
Seriously?
"Supporting a bunch of local DB's that we have no control over is a lot more difficult for us than supporting a centralised DB that we can interrogate and problem solve. We worked this out the hard way with MSO."
Every single piece of web software out there pretty much uses a database as a backend - including this forum - which I'm guessing you didn't write.
You're saying that for whatever reason, when people cannot use your software it's different to every other piece of software out there ?
Sounds like bunkum.
Er....what?
@Friznit Er....what?
TLDR?: The internet is made up of pieces of 3rd part software running on databases. Everyone seems to have coped just fine until now.
Maybe I'm misunderstanding something. Is this your round about way of saying please?
Anyway, as I explained, our experience from supporting local DB's in MSO for several years shows that your assertion is demonstrably untrue for everyone, so we're sticking to our current plans for now.
@Friznit Maybe I'm misunderstanding something. Is this your round about way of saying please?
People asked for an option for local DB citing "Frequent internal server errors, saying "Sorry." a lot.
In this thread http://alivemod.com/forum/1199-what-features-we-would-like it was in fact the most asked for feature by everyone who replied.
Pretty sure "please" was covered there and in the title of this thread already.
By all 3 of them, indeed. We have several thousand users on our War Room DB. I appreciate it's not ideal for everyone but given our available resources it is simply not on the list of priorities.
Just a word of advice: being aggressively rude to volunteer dev teams really isn't going to make them want to help you out.
I hear the moon landing was a hoax. Calling that out isn't "aggressively rude" either.
The entire internet runs on the notion you find unworkable. Calling that out, isn't being "aggressively rude".
Neither is the line "Sounds like bunkum."
Perhaps some thicker skin ?
In fact "accept what I have to say just because I'm the one saying it" is an entitled attitude more akin to cult leaders (because control) than software development, perhaps you owe us an apology.
Whatever.
No.
Is that clear enough for you?
Good to see those clear minds at work.
OK, im sorry but...
I for myself put in 4000 hours of my life to have some bigmouth telling me how the world spins?
whats wrong with you...
@highhead OK, im sorry but...
I for myself put in 4000 hours of my life to have some bigmouth telling me how the world spins?
whats wrong with you...
There's that entitled rudeness again, that you were so against. Who was rude to whom?
We already worked out how the world spins apparently summed up by "Whatever." or perhaps as you say "the world is flat" ?
"Supporting a bunch of local DB's that we have no control over is a lot more difficult for us than supporting a centralised DB that we can interrogate and problem solve. We worked this out the hard way with MSO."
This was the reason given. Now you call me a bigmouth for refuting obvious bullshit ?
The entire internet works on the exact basis you can't get working. I've put a lot more than 4000 hours into the internet buddy. And I know damned well if it can be saved remotely, it can be saved locally.
Refute it if you want. I could really give a shit what a bunch of self entitled forum admins and modders think. Stroke your ego some more and tell us how the world spins.
At least you're doing what you're good at then.
keep calm, you must have empaty, to users with issues and to voluntary dev.
About support local DB issues isn't necessary, only ask this because some gameservers are blocking external connections or i dont know.
You can continue supporting War-room DB only, but insert a local DB feature too.
It is not a question whether having local db as an option is possible, the problem lies in all the work around it. They've got to do code changes, testing, tutorials, and support for everyone who chooses this as an option. Do you really think they wouldn't like to get rid of their monthly charges to host the remote DB? I'm sure they would love to not have to pay $65 a month. It's not as simple as just hitting the "Allow local db" button. There is a lot of work that goes into it and then after that, a whole new wave of people who want help trying to set it up. It's a lot easier for them to provide help and support with a remote db as opposed to everyone having their own local db. As Friznit said, they've experienced this before. You also have to look at the roadmap, they are very hard at work putting together support for a wide array of features that tons of people have requested. They aren't superheros, they aren't getting paid, they have lives of their own to worry about first. Just request it nicely and see where things go. We are lucky enough to have a mod with ALiVE's capabilities already, the least we could do is not harass the devs who give up thousands of hours to make it possible.
My patience ran out. Sensible constructive discussion is fine but this is getting unpalatable.
Spyder - many thanks for explaining it in more detail. There seems to be some confusion between "technically feasible" and "supporting users setting up and running local db's".
The official answer remains the same - yes, it's technically feasible and one day we'd like to develop a local DB option but right now, given the available dev time and other project priorities, it's not on the roadmap.
Until then, there is the persistent database that we offer as a plug and play service via the War Room.
Just to chip in here.
Finn, I didn't find your response particularly rude.
The reasons we don't support local db are because
We honestly felt this approach was the best for ALiVE and we hope people respect that decision.
Now as you can see a few quite blunt responses here shows the passion and effort some people have put in :) I hope this post explains things in more detail and is not considered bullshit reasons.
We are looking at a possible file based local storage for certain things.
Cheers,
Tup
@zyg0tic BTW internal server errors on the website only occur for maps that are currently not uploaded on War Room - does not affect persistence.
alive.cfg can be downloaded by any machine, but it must be placed on the server you setup in War Room.
@AliveServer is only required on your server during the mission (not during editing). @ALiVE is also required on your server.
Having a single config file and registering your server on War Room is a lot easier than administering your own DB :)