Optimizations roadmap
-
So, how shall the market work between shards?
-
The old world has a lot of baggage- zombie players on 10cpu, or just somewhat inactive players who don’t mind paying but also don’t do anything.
Scripts of players without subscription stop working after 30 days of inactivity (no log into the game during 30 days).
I don’t think relying on it eventually balancing it out is the best way to handle it.
If it doesn’t balance itself, then we’ll start to balance it manually. Eventually our goal is to provide lower tick rates for all shards.
In my mental model of the screeps world I’m viewing shards as another dimension- a Z axis to go with the X and Y (or in this case north and south) and would like to see “elevators” in all the highway intersection rooms for going between levels.
Exactly, you got the idea of it. I can’t tell for now where those portals will be located, but what I can tell is that they will be neutral, and there will be plenty of them so that everyone can access. Inter-shard portals can be considered just another type of inter-room exit tiles. As long as all interested players can easily move back and forth, it remains the same idea of a single world consisting of isolated game zones (rooms/shards).
-
> So, how shall the market work between shards?
They would be seperated... otherwise the economy of a new shard would already broken from the beginning
> I really think the shard idea would be easier to deal with if the tick rates and time were kept close together, even if it does mean throttling the new shard when it gets too far ahead.
But the lower tick rate on the new shard is one of the only things I can think of why you would want to spawn on a new shard.
> The world is still single, just consists of connected shards. Eve Online is actually a great example of this, since they implemented the same idea of different game speed in different regions of space - so called “time dilation” mechanic.
It's a bit like apples and pears ... the time in eve online is only slowered in the star systems where currently a big combat is happening ... it has no impact on the econoly... and it is one of the most hated systems in eve online
It more reminds me on a mmog I played several years ago .. I currently don't remember the name. players and guilds could create villages and build cities and one of the features was that you can move your guild to other servers. Later there were guilds that were not interested in building cities but to only move from server to server and destroy others stuff
-
So, how shall the market work between shards?
They will be fully isolated. But you can start doing some import/export shenanigans between them, might be quite interesting way to raise some credits
-
I think the portals will have to work a bit differently. The room bouncing problem is already bad enough when your script is running on one server, but having to send a creep and have another script grab it at the right tick sounds like an amazingly frustrating experience. Having "entrance" and "exit" portals for each side, so a creep can get on a square in one world and end up on a non-portal square in another, with no concern about bouncing between the two.
I also think Memory should be completely independent so one server doesn't overwrite the other. Being able to request segments from different shards would give a useful communication channel.
-
> But the lower tick rate on the new shard is one of the only things I can think of why you would want to spawn on a new shard.
If the worlds are connected in a stable way then I would happily put an outpost on the other server, and build up on both sides. Having bases that players can't get to without either respawning or investing in extra-dimensional portal traversal seems like a huge strategic advantage.
-
> They will be fully isolated. But you can start doing some import/export shenanigans between them, might be quite interesting way to raise some credits
Credits too? Will subscription tokens be the same across shards?
-
I think the portals will have to work a bit differently. The room bouncing problem is already bad enough when your script is running on one server, but having to send a creep and have another script grab it at the right tick sounds like an amazingly frustrating experience. Having “entrance” and “exit” portals for each side, so a creep can get on a square in one world and end up on a non-portal square in another, with no concern about bouncing between the two.
Activating a portal would most likely require some explicit action like
Creep.moveToShard(portal, shardName)since the same portals may be used for more than two shards in the future.I also think Memory should be completely independent so one server doesn’t overwrite the other. Being able to request segments from different shards would give a useful communication channel.
Memory and segments will be independent to prevent race conditions, and due to loosely coupled architecture (runtime workers will be connected only to their shard’s database, not to others’). We still need to figure out some way to pass messages between shards in an asynchronous manner though.
Credits too? Will subscription tokens be the same across shards?
Can’t tell anything for sure now. We need to prevent race conditions on operations with credits and other account-wise resources like tokens. It can be achieved by either introducing locks and mutexes on such operations (reducing the performance), or separating their balances on each shard with an ability to transfer between them.
-
> Can’t tell anything for sure now. We need to prevent race conditions on operations with credits and other account-wise resources like tokens. It can be achieved by either introducing locks and mutexes on such operations (reducing the performance), or separating their balances on each shard with an ability to transfer between them.
Either way if you do this (split balances) it would be really useful if you also added in the market functions to transfer credits between players. If two players are in completely different shards they can't use the "expensive energy order" trick to transfer credits so there will need to be some mechanism there. It would also be nice if there was a client side or api level way of transferring credits, since even with the above mentioned transfer function it still requires an active room for console commands and with the multiple shard system that may end up being complicated.
-
while credit transfer would be a nice thing, I think even better would be private market entries... so you would add a receipient to the market order and no other player could see or accept the order.
to better arrange those transfers/deals some kind of in in-script messaging would be great of course
-
you can "in game message" now with public memory segments.
-
> you can "in game message" now with public memory segments.
really? how do you send someone a message with a public segment? do you put your message in there and hope that they read your segment in the near future?
do you scan every players public memory segments for messages ?
-
Well, I'd suppose you'd have to write one, but two people that know (or a large group that knows) to look at a certain segment could use that as a place to store "messages" that other people that know where to look, could read and process.
One thing is for sure, I don't need yet another source for spam. So no Game.notify("coteyr", "my message here") or anything like that.
-
How would you spam someone? The messages would get delivered to an array that has to get read - or ignored - by your script.. you would not even notice the messages if you don‘t look for it. I don‘t think many people will be interested in wasting cpu by sending messages to people who would not even notice that they got a message.
I still don‘t get how you would do the group messaging using public segments. How do you store your messages in someone else public segment? It‘s easy to publish data but it‘s impossible to tell someone to fetch your data without using a terminal hack or something like that. Checking every other players public segment one by one every tick will take a while if you want to communicate with a group of people like your alliance and neighbors.
-
(Answering with own ideas, not as a Screeps official)
Activating a portal would most likely require some explicit action like Creep.moveToShard(portal, shardName) since the same portals may be used for more than two shards in the future.
That’s a nice solution. The bouncing between shards could cause big issues due to different tick times.
Will the creep memory be passed along? I’d love to at least give it some purpose once it’s on the other side.We still need to figure out some way to pass messages between shards in an asynchronous manner though.
You could probably make a memory segment public per shard, which you can load in other segments. It could be loosely coupled
RawMemory.publishActiveShardSegment(id)
publishes data exactly once in a synchronous matter. This way there is no need to keep it up to date every tick.RawMemory.setActiveShardSegment("shardname")
set active shard data on the shard it’s run onRawMemory.shardSegment["shardname"]
get data from the raw memoryThat could fit nicely in the architecture without too much work. I’d grade cross-shard operations as an “advanced game mechanic” anyway, so doing it with segments seems like a good idea.
I still don‘t get how you would do the group messaging using public segments
You could do the following in your code:RawMemory.segments[0] = "hi bob"; RawMemory.setPublicSegments([0]);Another player could do:
RawMemory.setActiveForeignSegment("dissi", 0); // Next tick: var messageFromOtherPlayer = RawMemory.foreignSegmentobject.data;This should at least get the messaging going
-
@dissi: it was not a technical question about code.. I know how to get public segments of other players.
The problem is the other player would not know when I put some data into my public segment... so the plan is to put something into a public segment and then tell somebody in slack to fetch it?
-
W4rl0ck- you have to work out the protocol you build on top of the segments with the players who are also using them. There are a number of different options for this- The Culture is using terminals to transfer private keys as well as segment id's to watch, for instance- but at the moment there is no "universal" messaging system (although one could easily be built by the community).
-
Yeah. But the devs said in an other thread that they don‘t like using terminals for communication...
-
That was just one example, it was not intended to be the only one. You could easily share private keys in slack, or not use private keys at all. You can agree on communication segment ids and code them in yourself. The point is that the protocol itself is something that the group of people communicating need to come up with themselves.
This is a bit of a tangent though. If you are interested in creating a standard protocol for this you can join #diplomacy in slack where we're discussing these things.
-
Will the creep memory be passed along? I’d love to at least give it some purpose once it’s on the other side.
No it won’t, since the player may have custom Memory structure. But the creep’s name will be transferred, and you will be able to pass custom text messages to other shard as well (somehow).
You could probably make a memory segment public per shard, which you can load in other segments. It could be loosely coupled
This would require to connect runtime workers to all shards’ memory storages which creates to much coupling between all backend components. The idea is that inter-shard connectivity is being done only by one single isolated component running in background, passing creeps and text messages along between shards.
