Markets on CVRs

[Davin]

Ok, here's a new "game design" discussion topic for you...

As always, when getting a CVR you get a report of what's on a city's market and how much they're asking for it.  And remember that I've mentioned that through the game system, CVRs can optionally be "shared" with other players.  However, the new system provides for an extra mechanism in markets whereby the CL can place very flexible (and potentially complicated) restrictions on their marketplace.  For instance, you might be selling swords on your market but you don't want to sell them to anyone in your opposing faction.  So you can put a restriction on that item so that the other faction can't buy them and can't even get to see them on their CVRs.

I like this flexibility, and coding it is easy enough, but it presents me with a reporting problem.  How do I show restricted marketplaces on CVRs?  If it's only for you, that's fine because it's showing you what's available to you.  But if you share the CVR to someone else, it may show something to which they're not otherwise entitled to see.  The opposite is also true - you may not be seeing something because you're restricted, but the other player then wouldn't see it either even though it's available to them.  (This can be a particular problem when someone has hired you to get a CVR for them.)

What should I do about this CVR conundrum?

[DreamWeaver]

Maybe within the process you have a question...In which faction is the person that your sending the CVR too, this way the system will send the details, call it a "flag" tag question.

[Davin]

Yeah, but you get it as well. And you may decide to share it to someone else later. So it may need to be appropriate for multiple destinations simultaneously.

[DreamWeaver]

Does the CVR get saved into a file or table, if so you could have a subroutine that always checks what "faction" your clan is in, and then provides the details that you can see. Plus if it is being sent to another player, it also asks what faction they are in or it checks too and then sends the details that are available for that clan to see.

Basically when a <clan> enters a specific city and requests a copy of the CVR for that city, have a data file added to a table with that CVR full details at that date stored. Then have a subroutine run that checks that clans faction number and only the details that it can see will be presented in the clan's turn results. Now if a clan then sends that same CVR to someone else, then have the subroutine check the clan faction number that is getting the CVR and send to that clan the details that it can see. So if their is different data that they both can/can't see they will only see what their specific clans can see.

[Davin]

Technologically, this is quite reasonable.  But it presents problems when the players don't have the same reports and they start discussing and comparing them.  That also means there's a loophole about what data is revealed to players if they can then trade hidden information in the old-fashioned way.

[DreamWeaver]

This way Black Markets could be handled that way and etc.

Now how long will a CVR be stored for a clan? How many copies will be stored as well, like if you are in a city for (6) turns/cycles, and requested a CVR for that same city each time then you would have (6) different copies of the same CVR but from (6) different cycles/turns. These details might be important depending on what your looking for. Now over time this data will build up for a clan, how long will the details be kept for?

[Davin]

At present, I'm planning on saving CVRs and all other reports indefinitely (and buying more hard disk if needed to support that).  I may eventually end up trimming stuff that gets to be more than several years old, but I'll discuss that with the players if the time comes.

[Davin]

Black markets will be handled internally in the same way as a regular market, and will share the same reporting structure and procedures.  It'll just be accessed a little differently.

I'm also trying to come up with some other way to handle black markets besides a password, but all my ideas so far have fallen short in one way or another.

[DreamWeaver]

You know you could just resolve the CVR issue by just allowing only the data that the clan be see be sent as the CVR. That would be like copy a CVR and snail mail or scan it and email it. What is wrong with just doing it that way. It is more realistic.

[DreamWeaver]

Ok speaking as bot a DBA and Solutions Architect, try to avoid "data creep". The build up in space and performance hit will kill you and the game. I would think store the CVR off in a archive table, and have just a pointer to that same CVR in a table within the clans data set. This way the clan data sets will NOT become so huge. Now granted I am guess that a CVR can be a rather large datafile/data set on it's own.

Black Markets should have a subroutine that look for your faction (SOA only) and Clan number, then as to password...well that is the only way to set it up