Major Expansion of the Availability of LionsShop Data to Players

I have an idea for ways in which the utility of LionsShops could be expanded; an idea birthed by me, its umbilical cord cut by Dr. Ted1246, and the birth-y goop wiped from its bare naked newborn body by none other than dorn284.

‌

Quick Diction Note: Any and all uses of the words “accessed” or “accessible” when referring to the data of a LionsShop within the following text is to be interpreted as meaning “viewed”, “observed”, and/or “able to be viewed/observed”

‌

Firstly, LionsShops data as a broad concept could be made remotely available via commands to players. Anywhere from simply the numbers of shop items presently in the chests of a certain LionsShop, to the statistical data of said shop such as rate of sales, regular/returning customers, & dates and times the shop was used and by whom.

LionsShops could be configured by their shop owner so that certain parts of the shop’s data is publicly accessible or not. Certain parts of the data would be by default set to “shop owner can view only” or “publicly accessible for viewing” if the shop owner does not configure their shop from the start. For example, the transaction logs(records of when the shop was purchased from/sold to and by whom) would be by default set to only be accessible to the shop’s owner. Said configurations would, as I mentioned before, accessed by commands.

Other commands could be used to configure shop data accessibility settings on the fly. Said commands would be able to be used by all shop owners, with an ID or name being assigned to each individual LionsShop on the server by their respective owners. Using the commands and their shop’s ID/name, the owner of a shop and only the owner of a shop could use said configuration commands on their shop. There is no good reason to give players the ability to change the data accessibility settings of a shop that they are not the owner of. Duh.

The utility of such features goes without saying. Shop owners could receive a chat notification upon logging in to the server that alerts them if one of their shops is out of stock, look at statistical data to figure out what shop items(blocks and items) are most in-demand and what prices consumer players are most willing/likely to buy said shop items at, and what locations have higher traffic(what locations makes for a better location for a shop) in terms of the numbers of players that pass through/visit the location and buy stuff.

‌

The second part of my idea is much, much more consumer player focused. So we have all this data that can be accessed in regards to LionsShops. What if shop location and shop contents(the product and price) were included among them?

Imagine you’re a new player who has collected lots of building materials and amassed a decent amount of wealth. You’re looking for one specific block for a build you’re working on, and want to know if there are any good LionsShops selling that block. So, using a search command, you search for all publicly-accessible(as shop owners would have the option to configure their shop so that it does not come up in LionsShop searches, in the event they wish to make a private shop) LionsShops that sell the block you’re looking for. A list of them comes up in chat, with shop name/ID and the price at which the block is sold(as well as the quantity at which the block is sold), as well as a simple indicator that notates if a LionsShop among the list is in stock, low on stock, or out of stock(does not provide a number, merely a text indication) if that particular LionsShop is set by its owner so that data(the data on how stocked the shop is) is publicly accessible.

You find that the cheapest shop is selling the block you need in groups of 16 per purchase, at a price of 3 diamonds. Interested, you type in a separate command from the search command, putting the shop name/ID that was provided to you by said search command into this separate command. You are then presented with expanded information on the LionsShop(said information would, again, be able to be made publicly accessible or inaccessible by the shop’s owner), such as the coordinates location(or, possibly even a /map link and/or which Nexus branch is closest to the shop’s location), the username of the player who owns the shop, and the shop’s numerical(not merely text indication as was seen in the search command) stock. With the shop’s location now known to you, you make your way there, and make your purchase.

‌

Comments (1)