So I've recently been testing the map editor, and been hosting a non-public server in my spare time with friends.
I've become partially familiar with the map editor, and I'm already quite familiar with adminning.
But now, I'm looking at creating a server map that - rather than resetting each round - is perpetual.
I'm interested to know if anyone has figured out a way to do so - if indeed there is a way to do so.
Either through preventing the map from wiping clean to its original map state at the beginning of a new round, or by merely setting some config file to 1 instead of 0.
Any thoughts or suggestions are very welcome guys!
And yes - A perpetual server would probably not work for a real game on a public server. There'd be nothing left by the time the second crew arrived. But let's not worry about that for now.
Oct 7 2012, 4:16 am
|
|
Capt matt4
 |
the last line made me lose it.
|
Save the map each round. Load the map before the start of the next round.
http://www.byond.com/developer/Foomer/MapStorage http://www.byond.com/developer/LummoxJR/SwapMaps | |
Thank you so much!
| |
The idea sounds nice, but one griefer and you'll be ruined forever.
| |
Completely true. I'm looking at creating a different style gameplay for it however - for starters I'm looking at it being a Starship with rank and file, rather than a Space Station with jobs and minimal supervision.
I'm looking at basing the design and preliminary ideas on Star Trek Voyager and its namesake starship. I'm currently attempting to duplicate the deck plan of that - albeit not all 15 decks - using Z levels. Ladders are a bit of a bother, and I'm still working out shuttles (for the turbolifts between decks). I do plan to dramatically alter the gameplay though - given I plan rounds to last perhaps one week each, there will be incentives - such as promotions, special privileges, away missions, special duties - to keep people at it, and not griefing. Not to mention most of the key systems and tool lockers will rank or department restricted. I'm also looking at making ID's (which would be for rank/department rather than job) remotely editable as a further anti-griefing measure. But of course, it won't be that bland - there'll be space battles which may lead to damage to the ship, or perhaps even enemy/alien boarding parties. Or maybe the ship will run low on deuterium to fuel its core, so special away missions would be organised to locate more. Definitely admin supervision at all times to initiate events, keep the crew busy, and irl repercussions for overbearingly stupid gameplay. I'm very open to any suggestions or pointers too! I'm a quick learner, but much of the game mechanics and requirements for coding is still a large mountain I'm yet to climb! | |