Virtual building-based closing method and device, computer equipment, medium and program product

Abstract

The embodiment of the invention discloses a closing method and device based on a virtual building, computer equipment, a medium and a program product, and the method comprises the steps: displaying a closing control, and enabling the closing control to initiate a first closing request to a second account through a first account; the first account has a first virtual land, and the second account has a second virtual land. Through the combination control, the first virtual land and the second virtual land can be combined, that is, in response to a trigger operation for the combination control, a first combined virtual land obtained based on combination of the first virtual land and the second virtual land is displayed. Therefore, the virtual objects controlled by the player are combined in all the common virtual buildings through combination of the virtual lands, the desire of the player to adjust the virtual buildings is improved, and the user experience is improved. Moreover, the virtual props in the closed virtual building can be directly adjusted, and communication in advance is not needed, so that the communication cost is reduced, and the server pressure is reduced.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a method, apparatus, computer equipment, medium, and program product for cohabitation based on virtual architecture. Background Technology

[0002] To enhance user experience, many game applications have introduced a housing system. This system offers a co-living feature, where multiple virtual objects live in the same virtual building.

[0003] In related technologies, the shared virtual building is generally a virtual object, such as one of multiple shared virtual objects. However, this shared living method requires communication with the virtual building's owner before any adjustments can be made to the virtual items within the building, resulting in high communication costs and increased server load. Furthermore, players have a low desire to adjust virtual buildings that don't belong to them, leading to a poor user experience. Summary of the Invention

[0004] To address the aforementioned technical problems, this application provides a method, apparatus, computer equipment, medium, and program product for cohabitation based on virtual buildings, which solves the problems of high server load and poor user experience.

[0005] This application discloses the following technical solutions:

[0006] On one hand, embodiments of this application provide a method for cohabitation based on virtual buildings, the method comprising:

[0007] Display a co-living control, which is used to initiate a first co-living request from a first account to a second account, wherein the first account has a first virtual land and the second account has a second virtual land;

[0008] In response to a trigger operation on the shared living control, a first shared living virtual land, obtained by merging the first virtual land and the second virtual land, is displayed. The first shared living virtual land is used to construct virtual buildings that jointly belong to the first account and the second account.

[0009] On the other hand, embodiments of this application provide a method for cohabitation based on virtual buildings, the method comprising:

[0010] The first account initiates a first co-occupancy request to the second account, which is used to request the merging of the first virtual land belonging to the first account with the second virtual land belonging to the second account.

[0011] Determine the attributes of the first shared virtual land, which is a virtual land obtained by merging the first virtual land and the second virtual land;

[0012] From multiple branch lines, determine the first branch line that satisfies the attributes of the first shared virtual land;

[0013] The first shared virtual land is displayed on the first branch line.

[0014] On the other hand, embodiments of this application provide a shared living device based on virtual architecture, the device comprising: a first display unit and a second display unit;

[0015] The first display unit is used to display a co-living control, which is used to initiate a first co-living request to a second account through a first account. The first account has a first virtual land, and the second account has a second virtual land.

[0016] The second display unit is configured to, in response to a trigger operation on the shared living control, display a first shared living virtual land obtained by merging the first virtual land and the second virtual land, wherein the first shared living virtual land is used to construct virtual buildings that jointly belong to the first account and the second account.

[0017] On the other hand, embodiments of this application provide a co-living device based on virtual architecture, the device comprising: an initiating unit, a determining unit, and a display unit;

[0018] The initiating unit is used to initiate a first co-living request to a second account through a first account. The first co-living request is used to request the merging of a first virtual land belonging to the first account and a second virtual land belonging to the second account.

[0019] The determining unit is used to determine the attributes of the first shared virtual land, which is a virtual land obtained by merging the first virtual land and the second virtual land;

[0020] The determining unit is further configured to determine, from multiple sub-lines, a first sub-line that satisfies the attributes of the first shared virtual land;

[0021] The display unit is used to display the first shared virtual land on the first branch line.

[0022] On the other hand, embodiments of this application provide a computer device, the computer device including a processor and a memory:

[0023] The memory is used to store computer programs and to transfer the computer programs to the processor;

[0024] The processor is configured to execute the methods described above according to instructions in the computer program.

[0025] On the other hand, embodiments of this application provide a computer-readable storage medium for storing a computer program for performing the methods described above.

[0026] On the other hand, embodiments of this application provide a computer program product including a computer program, which, when run on a computer device, causes the computer device to perform the methods described above.

[0027] As can be seen from the above technical solution, a shared living control is displayed, which is used to initiate a first shared living request from a first account to a second account. The first account owns a first virtual land, and the second account owns a second virtual land. Through the shared living control, the first and second virtual lands can be merged; that is, in response to a trigger operation on the shared living control, the first shared virtual land, resulting from the merger of the first and second virtual lands, is displayed. This first shared virtual land is used to construct virtual buildings jointly belonging to both the first and second accounts. Thus, through the merging of virtual lands, the virtual objects controlled by the players are no longer shared in someone else's virtual building, but rather in a jointly owned virtual building, increasing the player's desire to adjust the virtual building and improving the user experience. Furthermore, since the shared virtual building belongs to both the first and second accounts, they can subsequently directly adjust the virtual items within the shared virtual building without prior communication, reducing communication costs and thus reducing server load. Attached Figure Description

[0028] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0029] Figure 1 A schematic diagram of a computer system for a cohabitation method based on virtual architecture, provided in an embodiment of this application;

[0030] Figure 2 A schematic diagram illustrating an application scenario of a cohabitation method based on virtual architecture, provided in an embodiment of this application;

[0031] Figure 3 A schematic diagram of a virtual land provided for an embodiment of this application;

[0032] Figure 4 A flowchart illustrating a method for cohabitation based on virtual architecture, provided for an embodiment of this application;

[0033] Figure 5 A schematic diagram of a virtual land and a first cohabitation virtual land provided for embodiments of this application;

[0034] Figure 6 A schematic diagram illustrating the shapes of various first shared virtual lands provided in the embodiments of this application;

[0035] Figure 7 A schematic diagram of a virtual community provided for an embodiment of this application;

[0036] Figure 8 A schematic diagram illustrating the adjustment of virtual props by a first virtual object and a second virtual object, provided in an embodiment of this application;

[0037] Figure 9 A schematic diagram of a home service provided in an embodiment of this application;

[0038] Figure 10 A schematic diagram of a dividing line provided in an embodiment of this application;

[0039] Figure 11 A schematic diagram illustrating a shared living method based on virtual architecture, provided as an embodiment of this application;

[0040] Figure 12 One of the structural schematic diagrams of a shared living arrangement based on a virtual building provided in this application embodiment;

[0041] Figure 13 A second schematic diagram of a shared living arrangement based on a virtual building, provided for an embodiment of this application;

[0042] Figure 14 This application provides a schematic diagram of the structure of a server according to an embodiment of the present application.

[0043] Figure 15 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. Detailed Implementation

[0044] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0045] To facilitate understanding of the technical solutions of this application, some technical terms involved in the embodiments of this application will be briefly introduced below.

[0046] (1) Virtual land: Virtual land is the construction land used in game applications to build virtual buildings and their ancillary facilities, including housing, ancillary buildings and courtyards.

[0047] (2) Virtual buildings: Virtual buildings are structures built on virtual land in game applications for virtual objects to live in, engage in activities or for other purposes.

[0048] (3) Virtual community: It is an enclosed residential area composed of multiple virtual buildings, usually equipped with public service facilities such as commerce, education, and medical care.

[0049] (4) Virtual props: These are props placed in virtual buildings, such as virtual wardrobes, virtual beds, virtual chairs, etc.

[0050] It should be noted that this application may display prompt interfaces, pop-ups, or output voice prompts before and during the collection of user-related data (e.g., cohabitation requests, virtual land, virtual buildings, etc.). These prompt interfaces, pop-ups, or voice prompts are used to inform the user that their relevant data is being collected. This ensures that the application only begins the steps for collecting user-related data after receiving confirmation from the user regarding the prompt interface or pop-up; otherwise (i.e., without receiving confirmation from the user), the steps for collecting user-related data end, meaning no user-related data is collected. In other words, all user data collected in this application is collected with the user's consent and authorization, and the collection, use, and processing of relevant user data must comply with the relevant laws, regulations, and standards of the relevant countries and regions.

[0051] To facilitate understanding of the virtual building-based cohabitation method provided in the embodiments of this application, the computer system for this virtual building-based cohabitation method will be described below.

[0052] See Figure 1 This figure is a schematic diagram of a computer system for a co-living method based on virtual architecture, provided in an embodiment of this application. The computer system 100 includes multiple devices, such as multiple terminal devices 110 and multiple servers 120, etc. The terminal devices 110 and servers 120 can communicate with each other through a communication network.

[0053] The communication network uses standard communication technologies and / or protocols, typically the Internet, but can also be any network, including but not limited to Bluetooth, local area network (LAN), metropolitan area network (MAN), wide area network (WAN), mobile, private network, or any combination of virtual private network. In some embodiments, custom or dedicated data communication technologies may be used to replace or supplement the aforementioned data communication technologies.

[0054] The terminal device can be an electronic device such as a smartphone, wearable device, personal computer (PC), intelligent voice interaction device, smart home appliance, vehicle terminal, aircraft, unmanned vending terminal, extended reality (XR) device, etc. Among them, XR devices can include virtual reality (VR) devices, augmented reality (AR) devices, and mixed reality (MR) devices. A client application for the target application can be installed and run on the terminal device. This target application can be an application that supports displaying virtual buildings, or it can be a game that supports virtual building creation and provides co-living functions, social networking, or other applications; this application does not limit its scope. Furthermore, this application does not limit the form of the target application, including but not limited to applications (Apps), mini-programs, etc., installed on the terminal device, and it can also be in the form of a webpage.

[0055] A server can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services such as cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDNs), and basic cloud computing services such as big data. A server can be a backend server for the aforementioned target application, providing backend services to the client of the target application, such as services supporting shared access functionality.

[0056] To facilitate understanding of the virtual building-based cohabitation method provided in this application embodiment, the following example uses a terminal device as the execution subject of the virtual building-based cohabitation method to illustrate the application scenarios of the virtual building-based cohabitation method.

[0057] See Figure 2 This figure is a schematic diagram illustrating an application scenario of a co-living method based on virtual architecture provided in an embodiment of this application. Figure 2 In this application scenario, a first terminal device 210, a second terminal device 220, and a server 230 are included. The first terminal device 210 and the second terminal device 220 are... Figure 1 Any of the terminal devices 110 described above, on which the aforementioned target application is installed, for executing the virtual building co-living method provided in the embodiments of this application, i.e., providing co-living functionality, and the server 230 is... Figure 1The server 120 described herein is used to support terminal devices in providing co-op functionality, such as executing based on interactive operations sent by the terminal devices (e.g., co-op requests generated based on trigger operations of co-op controls), thereby synchronizing the execution results to the corresponding terminal devices, i.e., synchronizing the status to the corresponding terminal devices (e.g., the first terminal device 210 and the second terminal device 220). The execution process is described in detail below.

[0058] In step S201, after the first player logs in to their first account in the target application through the first terminal device 210, the first virtual land belonging to the first account is displayed. On this first virtual land, the first virtual building constructed through the first account can also be displayed. For example... Figure 3 As shown in Figure A, the virtual community A includes three virtual plots of land. The first virtual plot of land is located in virtual plot 2, on which the first virtual building belonging to the first account is displayed.

[0059] In step S202, after the second player logs into their second account in the target application via the second terminal device 220, a second virtual land belonging to the second account is displayed. On this second virtual land, second virtual buildings constructed through the second account can also be displayed. For example... Figure 3 As shown in Figure B, the virtual community B includes four virtual plots of land. The second virtual plot of land is located in virtual plot 4, and a second virtual building belonging to the second account is displayed on it.

[0060] In step S203, taking the example of the first account sending a first cohabitation request to the second account, a cohabitation control is displayed. This cohabitation control is used to initiate a first cohabitation request from the first account to the second account.

[0061] In step S204, in response to the triggering operation of the co-occupancy control, a first co-occupancy request can be sent to the server 230 through the first terminal device 210.

[0062] In step S205, server 230 merges the first virtual land and the second virtual land to obtain a first shared virtual land, and sends the first shared virtual land to first terminal device 210 and second terminal device 220.

[0063] In steps S206 and S207, the first terminal device 210 and the second terminal device 220 respectively display the first shared virtual land. The first player and the second player can construct virtual buildings on the first shared virtual land using their respective first and second accounts, and these virtual buildings jointly belong to the first and second accounts. Figure 3As shown in C, the virtual community C includes 3 virtual land plots. After merging the first virtual land plot and the second virtual land plot, at least two of the virtual land plots need to be occupied. For example, virtual land plot 2 and virtual land plot 3 will be merged into the first shared virtual land plot, on which the first merged virtual building obtained by merging the first virtual building and the second virtual building can be displayed.

[0064] Therefore, by merging the virtual lands of multiple accounts, the virtual objects controlled by players no longer reside in other people's virtual buildings, but rather in jointly owned virtual buildings. This increases players' desire to adjust the virtual buildings and improves the user experience. Moreover, since the merged virtual buildings belong to both the first and second accounts, both accounts can directly adjust the virtual items within the merged virtual buildings without prior communication, reducing communication costs and thus reducing server load.

[0065] The virtual building-based cohabitation method provided in this application can be executed by a terminal device. However, in other embodiments of this application, the server may also have similar functions to the terminal device to execute the virtual building-based cohabitation method provided in this application, or the terminal device and the server may jointly execute the virtual building-based cohabitation method provided in this application. This embodiment does not limit this to any particular method.

[0066] Next, the virtual building-based co-living method provided in this application will be described in detail from both the front-end visualization perspective and the back-end technology perspective. First, let's combine... Figure 4 This application provides a detailed description of the co-living method based on virtual buildings from a front-end visualization perspective.

[0067] See Figure 4 This figure is a flowchart illustrating a virtual building-based co-living method according to an embodiment of this application. For ease of description, the following embodiment uses a computer device as the executing entity of this virtual building-based co-living method, such as the terminal device or server described above. Figure 4 As shown, this co-living method based on virtual architecture includes S401-S402.

[0068] S401: Display the control.

[0069] As mentioned above, although two virtual objects can coexist in the same virtual building in the relevant technologies, the virtual building belongs to only one virtual object. As a result, players have less desire to adjust the virtual building, and the communication cost required for adjustment is high, which leads to greater server pressure on the target application.

[0070] Based on this, the embodiments of this application provide a new co-living function, which can merge the virtual land of multiple accounts to obtain a larger virtual land. The virtual buildings constructed on this virtual land belong to multiple accounts. The following description uses the first account and the second account as examples.

[0071] Each player logs into the target application using a corresponding account. For example, the first player logs in using account number one, and the second player logs in using account number two. Account number one and account number two are different accounts. Account number one can have a first virtual land in the target application, which belongs to account number one. Similarly, account number two can have a second virtual land in the target application, which belongs to account number two.

[0072] The new co-living function provided in this application embodiment can be implemented through a co-living control, that is, displaying a co-living control. This co-living control is used to initiate a first co-living request from a first account to a second account. The first co-living request is a co-living request initiated by the first account to the second account. The co-living request is a request to merge the virtual land of multiple accounts.

[0073] This application does not specifically limit the display method of the control; two methods are described below as examples.

[0074] Method 1: Generate targeted cohabitation controls.

[0075] Specifically, in response to a triggering action on the target content, a shared accommodation control is displayed. In response to a triggering action on the shared accommodation control, a first shared accommodation virtual land, obtained by merging the first virtual land and the second virtual land, is displayed.

[0076] The target content refers to content that points to the second account, including but not limited to the second account, the second virtual land belonging to the second account, the second virtual building displayed on the second virtual land, and the second virtual object controlled by the second account.

[0077] A trigger operation refers to an operation performed on triggered content. For example, a trigger operation on target content is an operation performed on the target content to obtain a second account from the target content. Similarly, a trigger operation on a clump control is an operation performed on the clump control to implement the clump function. Trigger operations include, but are not limited to, click operations, double-click operations, and swipe operations; this application does not specifically limit these.

[0078] If the first player wants to share a room with the second player, the first player can perform a trigger operation on the target content through the first account. This could be done by clicking on the second account in the friends list, clicking on the second virtual land or building belonging to the second account, or clicking on the second virtual object controlled by the second account. In response to the trigger operation on the target content, it indicates that the first player wants to share a room with the second account corresponding to the target content. This generates a room-sharing control for the second account. Once the trigger operation is performed on the room-sharing control, a room-sharing request will be sent to the second account by default.

[0079] Therefore, by performing a trigger operation on target content related to the second account, a co-occupancy control for the second account can be generated. This co-occupancy control is used to initiate a co-occupancy request to the second account, thus making it more targeted, improving the accuracy of the co-occupancy function's target object, and enhancing the user experience.

[0080] Method 2: Generate macroscopic co-location controls.

[0081] Specifically, a shared accommodation control is displayed, which is not currently targeted at a second account. In response to the triggering operation of the shared accommodation control, pending target content corresponding to multiple accounts is displayed. In response to the selection operation of target content from multiple pending target content, the account corresponding to the target content is determined as the second account, and the first shared accommodation virtual land obtained by merging the first virtual land and the second virtual land is displayed.

[0082] Among them, the target content to be determined is a certain account, a virtual building belonging to a certain account, a virtual land belonging to a certain account, or a virtual object controlled by a certain account.

[0083] In this embodiment, the displayed "share" control is macroscopic, merely a control used to implement the "share" function, and does not indicate which virtual land to merge with. When the first player triggers the "share" control, in response to the trigger operation, multiple pending target contents corresponding to different accounts are displayed. That is, the pending target contents corresponding to multiple accounts that the first player may want to share with are displayed. The first player can select an account to share with from the multiple pending target contents. In other words, in response to the selection operation of the target content from the multiple pending target contents, the account corresponding to the target content is determined as the second account, thereby indicating that the first virtual land and the second virtual land will be merged.

[0084] This application does not specifically limit the method of determining multiple accounts. They can be multiple accounts that have a friend relationship with the first player, or accounts corresponding to other virtual lands in the same virtual community as the first virtual land, or accounts corresponding to all virtual objects within a preset range (e.g., 50 meters) of the first virtual object controlled by the first account. This application does not make specific limitations in this regard.

[0085] Therefore, by displaying a co-op control that only provides the co-op function, rather than a co-op control that provides the co-op function and indicates who to co-op with, players can independently indicate the control they want to co-op with, increasing the freedom of the co-op function and improving the user experience.

[0086] S402: In response to a trigger operation on the co-living control, display the first co-living virtual land obtained by merging the first virtual land and the second virtual land.

[0087] In response to the conditions or states on which the operation is performed depends, one or more operations may be performed in real time or with a set delay when the conditions or states on which they depend are met. Unless otherwise specified, there is no restriction on the order in which the multiple operations are performed.

[0088] In response to a trigger action on the shared living control, indicating that the first player has a shared living need, the first virtual land and the second virtual land are merged to obtain the first shared living virtual land. In other words, the first shared living virtual land is a virtual land obtained by merging the first and second virtual lands, and is a virtual land obtained by merging multiple virtual lands. Furthermore, the first shared living virtual land is used to construct virtual buildings that jointly belong to both the first and second accounts; that is, virtual buildings constructed on the first shared living virtual land belong not only to the first account but also to the second account, meaning they are jointly owned by the first and second accounts.

[0089] See Figure 5 The figure is a schematic diagram of a virtual land and a first shared virtual land provided in an embodiment of this application. Figure 5 As shown in Figure (A), there are currently 7 vacant virtual land plots (i.e., virtual land plots that have not been allocated to players), namely Virtual Land 1 to Virtual Land 7. Figure 5 As shown in Figure (B), virtual land 1 and virtual homestead 2 are merged and allocated to the first shared virtual land, which includes two virtual land plots.

[0090] It should be noted that the virtual building constructed on the first shared virtual land can be referred to as the first shared virtual building. This application does not specifically limit the form of the first shared virtual building; for example, it can be a virtual building constructed from scratch using either the first or second account. Furthermore, if the first virtual land displays a first virtual building belonging to the first account, and the second virtual land displays a second virtual building belonging to the second account, the first shared virtual building can be obtained by merging the first and second virtual buildings. This allows for improved merging efficiency and reduced production costs by reusing existing art resources. Additionally, the merged first virtual building can be modified using either the first or second account; this application does not specifically limit this modification.

[0091] This application does not specifically limit the method of merging the first virtual land and the second virtual land. For example, if there is an empty virtual land next to the first virtual land, the second virtual land can be moved next to the first virtual land to achieve the merger. Similarly, if there is an empty virtual land next to the second virtual land, the first virtual land can be moved next to the second virtual land to achieve the merger. Or, an empty virtual land that can accommodate the first merged virtual land can be found, and both the first and second virtual lands can be moved to that empty virtual land to achieve the merger.

[0092] The embodiments of this application do not specifically limit the size of the first shared virtual land. The size of the first shared virtual land can be equal to the sum of the sizes of the first virtual land and the second virtual land, or the size of the first shared virtual land can be greater than the sum of the sizes of the first virtual land and the second virtual land, so as to encourage multiple players to use the shared function.

[0093] This application does not specifically limit the shape of the first shared virtual land; those skilled in the art can set it according to actual needs. See also Figure 6 This figure is a schematic diagram of the shapes of various first-level shared virtual lands provided in embodiments of this application. Figure 6 The diagram illustrates two shapes of the first shared virtual land obtained by merging two virtual land plots, one shape obtained by merging three virtual land plots, and one shape obtained by merging four virtual land plots. It should be noted that the first shared virtual land plot may also have other shapes, and these are achieved through… Figure 5 All are shown.

[0094] The embodiments of this application do not specifically limit the location of the first shared virtual land. It can be determined based on the attributes of the first shared virtual land, which are used to describe the size, shape or dimensions of the first shared virtual land. The location of the first shared virtual land can be determined based on the attributes to improve the utilization rate of vacant virtual land.

[0095] As one possible implementation, the first shared virtual land comprises multiple virtual plots that are closely connected. "Connected" means the virtual plots are linked together, and "closely connected" means they are not separated by factors such as passageways or weeds. This first shared virtual land, formed by these closely connected plots, allows virtual buildings constructed on it to function as a unified whole, without being separated by other factors. This eliminates the logical boundaries between individual plots, allowing players to share land, enhancing the aesthetics of the virtual buildings, and increasing the success rate of shared living.

[0096] Furthermore, the multiple virtual land parcels included in the first shared virtual land are closely connected and aligned, such as... Figure 5 As shown, the shapes of multiple virtual land plots are consistent, so they can be aligned after being merged, thereby improving the space utilization of the virtual community. With limited resources, more players can be served, improving the user experience while reducing server pressure and construction costs.

[0097] As can be seen from the above technical solution, a shared living control is displayed, which is used to initiate a shared living request from a first account to a second account. The first account owns a first virtual land, and the second account owns a second virtual land. Through the shared living control, the first and second virtual lands can be merged; that is, in response to a trigger operation on the shared living control, the first shared virtual land, resulting from the merger of the first and second virtual lands, is displayed. This first shared virtual land is used to construct virtual buildings jointly owned by the first and second accounts. Thus, through the merging of virtual lands, the virtual objects controlled by the players are no longer shared in someone else's virtual building, but rather in a jointly owned virtual building, increasing the player's desire to adjust the virtual building and improving the user experience. Furthermore, since the shared virtual building belongs to both the first and second accounts, they can subsequently directly adjust the virtual items within the shared virtual building without prior communication, reducing communication costs and thus reducing server load.

[0098] As one possible implementation, this application provides a specific implementation of S402, namely, in response to a trigger operation on the co-occupancy control, displaying the first co-occupancy virtual land obtained by merging the first virtual land and the second virtual land, see A1-A2 for details.

[0099] A1: In response to a trigger operation on the co-living control, determine the first target virtual community among the multiple virtual communities based on the number of vacant virtual lands included in each virtual community.

[0100] As mentioned above, multiple virtual plots of land can be grouped into a virtual community. A virtual community includes multiple plots of virtual land, and the number, size, and shape of the virtual plots may vary between different virtual communities. It should be noted that the virtual plots within a virtual community have two states: occupied and unoccupied. Occupied virtual plots have been allocated to an account, while unoccupied virtual plots have not been allocated to an account; that is, unoccupied virtual plots are those without an assigned account and can be referred to as vacant virtual plots.

[0101] Based on this, in response to the trigger operation of the co-living control, a first target virtual community is determined among the multiple virtual communities according to the number of vacant virtual lands included in each of the multiple virtual communities, such that the number of vacant virtual lands included in the first target virtual community is greater than or equal to the number of first co-living virtual lands, that is, the first target virtual community can place the first co-living virtual lands.

[0102] As one possible implementation, in this embodiment, the multiple virtual land parcels comprising the first shared-living virtual land are closely connected and aligned with each other, thereby reducing the difficulty of allocating the first shared-living virtual land to a suitable virtual community and increasing the success rate of shared living.

[0103] A2: Display the first shared virtual land in the first target virtual community.

[0104] This application does not specifically limit the virtual community where the first virtual land and the second virtual land are located. For example, the first virtual land is in the first virtual community and the second virtual land is in the second virtual community. The first virtual community may be the same as or different from the second virtual community. This application does not make specific limitations in this regard.

[0105] As one possible implementation, if the first virtual community and the second virtual community are different, and the first target virtual community can be the same as the first virtual community, then moving the second virtual land from the second virtual community to the first virtual community allows for a reallocation of the first virtual land's location within the first virtual community, thus achieving a reallocation of the locations for the first and second virtual lands. Alternatively, the location of the first virtual land within the first virtual community can be reused to move the second virtual land from the second virtual community to a location next to the first virtual land within the first virtual community, etc.

[0106] Similarly, if the first virtual community and the second virtual community are different, and the first target virtual community can be the same as the second virtual community, then moving the first virtual land from the first virtual community to the second virtual community allows for the reallocation of the second virtual land within the second virtual community, thus achieving a reallocation of positions for both the first and second virtual land. Alternatively, the position of the second virtual land within the second virtual community can be reused, allowing the first virtual land to be moved from the first virtual community to a location next to it within the second virtual community, etc.

[0107] If the first virtual community and the second virtual community are different, and the first target virtual community is different from the first virtual community, and the first target virtual community is different from the second virtual community, then the first virtual land is moved from the first virtual community to the first target virtual community, and the second virtual land is moved from the second virtual community to the side of the first virtual land in the first target virtual community.

[0108] See Figure 7 This figure is a schematic diagram of a virtual community provided in an embodiment of this application. Figure 7 The virtual community includes not only 18 virtual plots of land, but also a central landscaped area or virtual commercial zone. The first shared virtual plot can be placed in a suitable location among the 18 available virtual plots. For example, a first shared virtual plot consisting of 4 virtual plots can be placed... Figure 7 The virtual community shown is located in the upper left or lower right corner.

[0109] Therefore, when multiple virtual lands are aggregated into a virtual community, the first shared virtual land obtained by merging can be displayed in any virtual community, as long as the number of vacant virtual lands in any virtual community can meet the number of virtual lands included in the first shared virtual land. For example, any virtual community can be the first virtual community, the second virtual community, etc. In this way, the number of virtual lands can be used to ensure successful cohabitation and improve the success rate of cohabitation.

[0110] As one possible implementation, not only can suitable virtual communities be arbitrarily assigned to the first shared virtual land, but players can also choose the virtual community they want. This application provides a specific implementation of A1, namely, in response to a trigger operation on the shared control, determining the first target virtual community among multiple virtual communities based on the number of vacant virtual lands included in each virtual community; see B1-B3 for details.

[0111] B1: In response to a trigger operation on the co-living control, determine multiple pending virtual communities among the multiple virtual communities based on the number of vacant virtual lands included in each virtual community.

[0112] Among them, the number of vacant virtual lands in each of the multiple pending virtual communities is greater than or equal to the number of first shared virtual lands. In other words, each pending virtual community has the ability to place first shared virtual lands, and thus can be used to place first shared virtual lands.

[0113] B2: Displays various pending virtual communities.

[0114] This application does not specifically limit the way the pending virtual communities are displayed. For example, it can display the identifiers (such as names, numbers, etc.) corresponding to each pending virtual community. Alternatively, it can display miniature models corresponding to each pending virtual community, thereby helping players quickly select their preferred virtual community.

[0115] B3: In response to a triggered operation targeting a target virtual community among multiple pending virtual communities, the target virtual community is identified as the first target virtual community.

[0116] If the first player wants to select a target virtual community from multiple pending virtual communities, a trigger operation can be performed on the target pending virtual community. In response to the trigger operation on the target pending virtual community among the multiple pending virtual communities, the target pending virtual community is identified as the first target virtual community.

[0117] Therefore, by displaying multiple undetermined virtual communities with the ability to place the first shared virtual land to the player, the player can choose the desired undetermined virtual community as the first target virtual community for placement. This increases the success rate of shared accommodation, enhances the freedom of choice, and improves the user experience.

[0118] It should be noted that each virtual community is generally managed through a sub-line. When a player enters a virtual community through an account, it is equivalent to the player entering a sub-line through an account. Players on different sub-lines are not visible to each other. That is, players who enter the same sub-line or the same virtual community can see each other, such as their virtual land, virtual buildings, and virtual objects under their control. This application does not specifically limit the definition of visibility.

[0119] Based on this, after the first shared virtual land is placed in the first target virtual community, this application embodiment also provides a method to help players automatically refresh their virtual community, see C1 for details.

[0120] C1: In response to the first shared virtual land being displayed in the first target virtual community for a duration exceeding a duration threshold, the first shared virtual land is displayed in the second target virtual community.

[0121] The display duration of the first shared virtual land in the first target virtual community refers to the duration during which the first shared virtual land is bound to the first target virtual community, that is, the duration during which the first shared virtual land is placed in the first target virtual community.

[0122] If the display duration exceeds the duration threshold, it means that the first shared virtual land has been in the first target virtual community for some time. At this point, in order to expand the player's social relationships, the virtual community where the first shared virtual land is located can be changed to the second target virtual community, that is, the first shared virtual land will be displayed in the second target virtual community. The second target virtual community and the first target virtual community are different virtual communities.

[0123] This application does not specifically limit the time threshold, and those skilled in the art can set it according to actual needs. For example, it can be a week.

[0124] As one possible approach to reduce server load, the virtual community can be changed for all active shared virtual lands. An active shared virtual land is defined as any virtual land whose accounts have logged into the target application within a specified period prior to the current time. In other words, step C1 will only be executed if the first shared virtual community is an active shared virtual land, thus reducing server load.

[0125] Therefore, by changing the virtual community of the first shared virtual land at fixed intervals, players can not only expand their social circle by changing the virtual community, but also change the virtual community of multiple accounts at the same time based on the shared virtual land. This is convenient and fast, and also ensures that multiple accounts still have the shared function, thus improving the user experience.

[0126] As one possible implementation, this application embodiment also provides a specific implementation of S402, namely, in response to a trigger operation on the co-occupancy control, displaying the first co-occupancy virtual land obtained by merging the first virtual land and the second virtual land, see D1 for details.

[0127] D1: In response to a trigger operation on the co-living control, display the first co-living virtual land, and display the first co-living virtual building obtained by merging the first virtual building and the second virtual building on the first co-living virtual land.

[0128] As mentioned above, virtual land is used to construct virtual buildings, and the constructed virtual buildings and virtual land belong to the same account. For example, the first virtual building constructed and displayed on the first virtual land belongs to the first account, and the second virtual building constructed and displayed on the second virtual land belongs to the second account.

[0129] After the first virtual land and the second virtual land are merged to form the first shared-occupancy virtual land, a first shared-occupancy virtual building can be constructed and displayed on the first shared-occupancy virtual land. This first shared-occupancy virtual building belongs to both the first account and the second account. In other words, the first shared-occupancy virtual building is a shared-occupancy virtual building belonging to both the first account and the second account, and a shared-occupancy virtual building is a virtual building that belongs to multiple accounts.

[0130] As one possible implementation, the first shared virtual building can be built from scratch by the first or second account, or it can be obtained by merging the first and second virtual buildings, thereby reducing production costs by reusing existing art resources.

[0131] Therefore, after merging multiple virtual land plots, not only can the merged virtual land be displayed, but also shared virtual buildings can be constructed and displayed on the shared virtual land. Moreover, the merged virtual buildings are directly obtained by merging the virtual buildings constructed and displayed on multiple virtual land plots, thereby reducing usage restrictions and production costs by reusing existing art resources.

[0132] As one possible approach, after constructing a shared virtual building on a shared virtual land, virtual items such as virtual wardrobes, virtual beds, and virtual sofas can be placed within the shared virtual building or shared virtual land. The following section illustrates four placement methods as examples.

[0133] Method 1: Place the first virtual item belonging to the first account in the first shared virtual building or the first shared virtual land.

[0134] The first virtual item is a virtual item belonging to the first account. The first player can place their own first virtual item in the first shared virtual building or on the first shared virtual land through the first account. They can also control the first virtual object to place their own first virtual item in the first shared virtual building through the first account. This application does not make any specific limitations on this.

[0135] This application does not specifically limit the placement method. Virtual props can be placed in the shared virtual building or in the empty space on the shared virtual land. Virtual props can also be stacked on top of other virtual props to achieve a stacking effect.

[0136] In other words, each player who shares a virtual building can use their own virtual items to place within the shared virtual building, or even on the shared virtual land, after sharing the building. Since they are the owners of the shared virtual building, they can freely place virtual items without prior communication with others, reducing communication costs and server load.

[0137] Method 2: Move the second virtual item belonging to the second account within the first shared virtual building or the first shared virtual land.

[0138] The second virtual item is a virtual item belonging to the second account. The first player can move any virtual item in the shared virtual building or the first shared virtual land through the first account, even if it belongs to another player. For example, moving the second virtual item belonging to the second account in the first shared virtual building.

[0139] In other words, each co-occupant in the shared virtual building can operate and move the virtual props that other co-occupants have already placed. Since they are the owners of the shared virtual building, they can freely place virtual props without prior communication with others, reducing communication costs and server pressure.

[0140] Method 3: Select the first target virtual item from the shared virtual backpack and place it in the first shared virtual building or the first shared virtual land. The shared virtual backpack belongs to both the first and second accounts.

[0141] A shared virtual backpack is a virtual backpack jointly owned by multiple roommates in a shared virtual building. For example, the shared virtual backpack in the first shared virtual building belongs to both account one and account two. The first target virtual item is a virtual item included in the shared virtual backpack.

[0142] In other words, roommates cannot directly use virtual items from other roommates' personal virtual backpacks to place items, but they can use virtual items from the shared virtual backpack. Each roommate can place virtual items from the shared virtual backpack and return them to their own virtual backpacks. This reduces communication costs, protects players' assets, and improves user experience.

[0143] Method 4: Reclaim the second target virtual item placed in the first shared virtual building or the first shared virtual land; if the second target virtual item belongs to the first account, the second target virtual item will be stored in the virtual backpack of the first account; if the second target virtual item belongs to the second account, the second target virtual item will be stored in the virtual backpack of the second account.

[0144] The second objective is to place virtual props in the first shared virtual building or the first shared virtual land.

[0145] In other words, each cohabitant can reclaim virtual items placed in the shared virtual building or shared virtual land. The reclaimed virtual items will return to their original owner's virtual inventory, thus preventing players from losing their assets.

[0146] Therefore, cohabitants can place, move, and recycle virtual items within their shared virtual building or shared virtual land. Since they are the owners of their shared virtual building, they can freely place virtual items without prior communication with others, reducing communication costs and server load. Moreover, even if virtual items are placed in public areas, the ownership of the virtual items remains unchanged, preventing asset loss and improving user experience.

[0147] Furthermore, multiple players can simultaneously adjust virtual items in shared virtual land or shared virtual buildings, see E1-E2 for details.

[0148] E1: Displays the first virtual object controlled by the first account and the second virtual object controlled by the second account.

[0149] The first virtual object is a virtual object controlled by the first account, and the second virtual object is a virtual object controlled by the second account.

[0150] E2: In response to a third target virtual prop in the first shared virtual building or the first shared virtual land being edited by a second virtual object, the third target virtual prop in the editing state is displayed.

[0151] The third target virtual prop is a virtual prop within the first shared virtual building or the first shared virtual land that has been edited by the second virtual object. Editing operations are operations performed on the third target virtual prop, such as moving or recycling operations; this application does not specifically limit this.

[0152] Multiple players can simultaneously adjust virtual items in shared virtual land or shared virtual buildings, and can see each other's adjustment process, thus avoiding disputes. For example, the first player can see the second player's editing operations on a third target virtual item. To distinguish it from other virtual items, the third target virtual item can be set to edit mode, such as by specially displaying or highlighting it. This application does not impose specific limitations on this.

[0153] See Figure 8 This figure is a schematic diagram illustrating the adjustment of virtual props by a first virtual object and a second virtual object according to an embodiment of this application. Figure 8 As shown in Figure (A), the third virtual prop is enclosed by a solid border to indicate that it is in edit mode. The second virtual object wants to move the third virtual prop from position A (e.g., ...). Figure 8 Move the position circled by the solid line in Figure (A) to position B (e.g.) Figure 8(The area circled by the dashed line in Figure (A)). This movement process is seen by the first player through the first virtual object, and during the editing operation, the third virtual item is circled by the solid line. For example... Figure 8 As shown in Figure (B), the state of the third virtual prop after its transfer is displayed from another angle. The third virtual prop is enclosed by a solid border to indicate that it is in edit mode. The second virtual object has moved the third virtual prop from position A (as shown in Figure B). Figure 8 Move the position circled by the dashed border in Figure (B) to position B (e.g.) Figure 8 (Figure B) shows the position circled by the border.

[0154] As a result, multiple players can simultaneously perform editing operations on virtual items in shared virtual land or shared virtual buildings, and their editing operations are visible to each other. That is, the operation process is displayed synchronously, and the virtual item being edited will be in an edit state. This makes it easy for players to know which virtual item is being edited, thus avoiding multiple players editing the same virtual item at the same time, preventing competition, and improving the user experience.

[0155] As one possible implementation, this application not only provides the function of cohabitation, but also the function of separation, as detailed in F1-F2.

[0156] F1: Displays the split control.

[0157] The split control is used to reclaim the first virtual land from the first shared virtual land and return it to the first account. Through the shared virtual land control, the first account can initiate a shared virtual land with a second account. Through the split control, the first account can end the shared virtual land, that is, leave with its own virtual land and reclaim the first virtual land from the first shared virtual land.

[0158] F2: In response to a trigger action on the split control, display the first virtual land.

[0159] In response to the triggering action of the split control, it indicates that the first player has the intention to split, and thus the first virtual land can be reclaimed from the first shared virtual land. The first shared virtual land will no longer be displayed, but the first virtual land belonging to the first account will be displayed instead.

[0160] Among them, the first shared virtual land becomes the remaining virtual land, which is the virtual land obtained after removing the first virtual land from the first shared virtual land.

[0161] For example, if the first shared virtual land is obtained based on the first and second virtual lands, then the remaining virtual land is the second virtual land. If the first shared virtual land is obtained by combining the first, second, and third virtual land belonging to a third account—meaning the first and second accounts subsequently shared land with the third account—then the remaining virtual land is obtained based on the second and third virtual lands. In other words, the shared virtual land resulting from merging virtual lands from multiple accounts can also be separated based on the user's wishes, without requiring the consent of others. The remaining virtual land can be one or more virtual lands, thus satisfying the user's desire to separate while maximizing the sharing of other users' wishes, thereby improving the user experience.

[0162] Therefore, the co-living control allows virtual land belonging to multiple accounts to be merged, while the separation control allows virtual land to be separated from co-living virtual land, becoming independent virtual land that is not merged with other virtual land. Thus, the co-living and separation functions provide users with more freedom in social interaction and improve the user experience.

[0163] As one possible implementation, after splitting up, one can not only take their own virtual land with them, but also retrieve the virtual items they placed in the shared virtual building or shared virtual land. The following example uses taking the first virtual item from the shared virtual building as an example. Based on this, this application embodiment provides a specific implementation of F2, which displays the first virtual land in response to a trigger operation on the splitting up control. See G1 for a specific implementation method.

[0164] G1: In response to a trigger operation on the split control, display the first virtual land and the first virtual building on the first virtual land.

[0165] If a first shared virtual building is also displayed on the first shared virtual land, and this first shared virtual building includes the first virtual item belonging to the first account, then after the first player executes the split control, not only will the first virtual land belonging to the first account be reclaimed, but also the items belonging to the first account in the first merged virtual homestead, such as the first virtual building and the first virtual item, will be reclaimed. The reclaimed virtual items will be stored in the virtual inventory belonging to the first account. This avoids the loss of player assets, making both the shared and split functions more flexible and requiring less deliberation from players, thus improving the user experience.

[0166] Furthermore, the first shared virtual building becomes a remaining virtual building because the first account is splitting up. The remaining virtual building only includes the remaining virtual items. That is, the remaining virtual building is the virtual building after removing the first virtual building from the first shared virtual building, and the remaining virtual items are the virtual items after removing the first virtual item from the virtual items displayed in the first shared virtual building.

[0167] Therefore, by separating from shared virtual land through the separation control, i.e., becoming independent virtual land and not merging with other virtual lands, not only can the virtual land belonging to the account be reclaimed, but also other items belonging to the account can be reclaimed, such as virtual props placed in shared virtual buildings. Thus, based on the separation function, the loss of player assets is avoided, allowing users to socialize more freely and improving the user experience.

[0168] As one possible approach, when initiating a co-living request to another account, the consent of that other account and the consent of other co-living participants in the shared virtual land where that other account resides are required before the co-living can be completed. See H1-H3 for details.

[0169] H1: Displays the second co-living request from the fourth account.

[0170] The second cohabitation request is directed at the first account. The second cohabitation request is a cohabitation request sent by the fourth account to the first account.

[0171] Let's take the example of a fourth account sending a second roommate request to a first account. After the fourth account sends the second roommate request to the first account, the first account will display the second roommate request from the fourth account. Depending on whether the first account is willing to share the room, there are two scenarios. These will be explained below.

[0172] H2: If the first virtual land and the second virtual land are merged and displayed as the first shared virtual land, then in response to both the first account and the second account agreeing to the second shared request, the second shared virtual land is displayed.

[0173] Scenario 1: The first account and the second account share a room.

[0174] At this point, if the fourth account sends a second co-living request to the first account, both the first and second accounts will receive the second co-living request. Only after both the first and second accounts agree will the co-living take place, and the second co-living virtual land will be displayed. This second co-living virtual land is a virtual land obtained based on the first virtual land, the second virtual land, and the fourth virtual land belonging to the fourth account.

[0175] H3: If the virtual land belonging to the first account is displayed independently, then in response to the first account's agreement to the second cohabitation request, the third cohabitation virtual land will be displayed.

[0176] Scenario 2: The first account resides independently.

[0177] At this point, if the fourth account sends a second co-living request to the first account, only the first account will receive the second co-living request. Only after the first account agrees to the co-living request will the co-living take place, and the second co-living virtual land will be displayed. The second co-living virtual land is a virtual land obtained based on the first virtual land and the fourth virtual land belonging to the fourth account.

[0178] Therefore, when initiating a co-living request to other accounts, the consent of the other accounts and other co-living participants in the shared virtual land of those other accounts is required before the co-living can be completed. This satisfies the initiator while also ensuring the wishes of other accounts and their co-living participants, thus guaranteeing a pleasant co-living experience and improving the user experience.

[0179] After introducing the co-living method based on virtual buildings provided in this application embodiment from the perspective of front-end visualization, since the front-end visualization method based on virtual buildings requires back-end technology support, the co-living method based on virtual buildings provided in this application embodiment will be introduced from the perspective of back-end technology below, see S1101-S1104.

[0180] For ease of explanation, the service architecture will be described first below.

[0181] The designers of the target application will pre-set multiple virtual scenarios, each of which can be identified by a DungeonID. Each virtual scenario corresponds to the same or different resources, such as the number of virtual land plots and supporting virtual facilities, for subsequent allocation.

[0182] A virtual scene can be managed through multiple seplines, which are entities used to allocate virtual land and manage virtual buildings. Each sepline runs a virtual scene instance, and multiple virtual lands are allocated on a single sepline, corresponding to a virtual community. The virtual lands on multiple seplines are independent of each other. When a player enters a virtual scene, they are essentially entering a sepline within that scene. Players on the same sepline can see each other, while players on different seplines are not visible to each other.

[0183] Each virtual land managed by a sub-line has a unique land number. When a virtual land is assigned to a player, the corresponding land number is linked to the player's account, indicating that the virtual land is in an assigned state. Similarly, when a player's virtual land is assigned to another sub-line, it can be unlinked from the land number of the current sub-line, releasing the unlinked virtual land. This means that the unlinked virtual land on the current sub-line is now in an unassigned state.

[0184] Virtual buildings are data entities that players construct on virtual land. Multiple players can share the same shared virtual building. Each virtual building can occupy one or more virtual plots of land, and these plots can be closely connected or even aligned.

[0185] The HouseService is responsible for maintaining sub-lines and virtual buildings. This server supports multi-instance deployment, and multiple sub-lines of the same virtual scene will be distributed in a load-balanced manner across various HouseService servers.

[0186] See Figure 9 This figure is a schematic diagram of a home service provided in an embodiment of this application. Figure 9 The image shows three homestead services: Homestead Service 1, Homestead Service 2, and Homestead Service 3. Each homestead service is responsible for multiple sub-lines. Figure 9 (Only two are shown in the image). Multiple sub-lines can come from the same virtual scene, such as sub-line 1, sub-line 2, and sub-line 3 coming from virtual scene 1.

[0187] See Figure 10 This figure is a schematic diagram of a dividing line provided in an embodiment of this application. Figure 10 In the process, the branch cache includes multiple branches, each responsible for multiple virtual lands and capable of constructing multiple virtual buildings. For example, branch 1 can construct virtual building 1, virtual building 2, virtual building 3, etc.

[0188] After introducing the service architecture, we can use the example of a single person buying a house to illustrate the process of using the service architecture.

[0189] When a player initiates a house purchase request to the Homestead Service, the Homestead Service generates a virtual building entity. Then, it retrieves a suitable virtual landline (with an unallocated plot) from the landline cache and binds the generated virtual building to the plot's ID. If no suitable landline is found in the cache, a new landline is generated for virtual land allocation. The pseudocode for generating a new house for a single player is as follows:

[0190] AddNewHouse()

[0191] 1. GetRedisLockForPlayers() / / Acquires a Redis distributed lock for each player to prevent multiple requests from players from being executed concurrently.

[0192] 2 GenerateNewHouseID() / / Generates a unique house ID

[0193] 3. CreateHouseEntity() / / Creates a house entity

[0194] 4. AssignSeplineForHouse() / / Assigns a Sepline to the generated house entity

[0195] 4.1 CalcNeedGroundNum() / / Calculates the required amount of virtual land.

[0196] 4.2 for each Sepline in LRUCache: / / Iterate through the LRU cache until a Sepline is found that satisfies the allocation requirement.

[0197] bSucc, HouseNoList = Sepline.GetOneHouse(NeedGroundNum)

[0198] if bSucc: break

[0199] 4.3 if bFailedFromLRU: / / Failed to allocate from LRU

[0200] AddNewSepline() / / Generates a new Sepline

[0201] NewSepline.GetOneHouse(NeedGroundNum) / / An empty Sepline will always be successfully allocated.

[0202] 5. NotifyPlayerGetNewHouse() / / Notify the player to update data

[0203] 6. UnlockRedisLock() / / Releases the Redis distributed lock

[0204] In addition, the lines in the line cache can be managed using methods such as Least Recently Used (LRU). That is, lines that are removed from the line cache will be written to the database (DB) and added back to the line cache the next time they are accessed.

[0205] The following describes the usage process of the service architecture of the co-living method based on virtual buildings provided in the embodiments of this application.

[0206] See Figure 11 The figure is a schematic diagram of a cohabitation method based on virtual buildings provided in an embodiment of this application.

[0207] S1101: Initiate the first cohabitation request to the second account through the first account.

[0208] Each player logs into the target application using a corresponding account. For example, the first player logs in using account number one, and the second player logs in using account number two. Account number one and account number two are different accounts. Account number one can have a first virtual land in the target application, which belongs to account number one. Similarly, account number two can have a second virtual land in the target application, which belongs to account number two.

[0209] The first co-occupancy request is used to request the merging of the first virtual land belonging to the first account and the second virtual land belonging to the second account.

[0210] S1102: Determine the attributes of the first shared virtual land.

[0211] The first shared virtual land is a virtual land obtained by merging the first virtual land and the second virtual land. The attributes of the first shared virtual land describe its properties, such as shape, quantity, and size. These attributes are also used to assign suitable boundaries to the first shared virtual land.

[0212] S1103: From multiple sub-lines, determine the first sub-line that satisfies the attributes of the first shared virtual land.

[0213] Based on the attributes of the first shared virtual land, one of the multiple branch lines is selected that can successfully place the first shared virtual land, namely the first branch line.

[0214] Similar to the process of buying a house individually, a purchase request is sent to the Homestead Service. The Homestead Service merges the first virtual building and the second virtual building to obtain the entity of the first shared virtual building. Then, it retrieves a suitable sub-line (i.e., a sub-line) from the sub-line cache that still has unallocated virtual land and the number of unallocated virtual land is greater than or equal to the number of virtual land included in the first shared virtual building. The first shared virtual building is then bound to the number of the unallocated virtual land, and the entity of the generated first shared virtual building is also bound to the first shared virtual land. If there is no suitable sub-line in the sub-line cache, a new sub-line is generated for virtual land allocation.

[0215] S1104: Display the first shared virtual land in the first branch line.

[0216] The first shared virtual land is assigned to the first branch for management. For example, placing the first shared virtual land on an unassigned virtual land within the first branch will cause the first shared virtual land to occupy the land number of that unassigned virtual land, thus achieving virtual land binding. The first shared virtual land is displayed on the first branch, and all players on the first branch can see it.

[0217] For example, during the initialization of a sub-line, the system retrieves the virtual land maintained by that sub-line from the Home Service, and even the virtual buildings bound to those virtual lands. It then generates a participant (HouseActor, Actor instance) for that virtual building at the corresponding land location. This Actor instance obtains the editing scheme for the virtual props currently used by the corresponding virtual building and generates the corresponding virtual props in the scene. This achieves the display of the first shared virtual land in the first sub-line, and the display of the first shared virtual building and virtual props on the first shared virtual land. The pseudocode for shared housing can be as follows:

[0218] MergeHouse()

[0219] 1 For each House

[0220] House.PreMergeHouse() / / Preprocessing

[0221] 2 for each House

[0222] Sepline.PreDeleteHouse() / / Pre-deletes virtual land from the branch line containing the virtual land.

[0223] 3. AddNewHouse() / / Generates a new house

[0224] 4. PostProcess(bSucc) / / Post-processing. If any of the above steps fail, then bSucc (i.e., the logic above) = false; otherwise, bSucc = true.

[0225] for each House

[0226] if bSucc: House.ConfirmMergeHouse()

[0227] else: House.CancelMergeHouse()

[0228] for each House

[0229] if bSucc: Sepline.ConfirmDeleteHouse()

[0230] else: Sepline.CancelDeleteHouse()

[0231] As one possible implementation, two shared virtual plots can be combined again, provided both users agree. Therefore, if the virtual plot to be combined is already in a shared state, its data in the database can be deleted, as it will not be reused. If the virtual plot to be combined is not in a shared state, i.e., belongs solely to one account, it can be marked as "deleted," while its data in the database can be retained for future use when separating.

[0232] As can be seen from the above technical solution, a first co-occupancy request is initiated from the first account to the second account. The first account possesses a first virtual land, and the second account possesses a second virtual land. Through this first co-occupancy request, the first and second virtual lands can be merged to obtain a first co-occupied virtual land. To allocate this first co-occupied virtual land, based on its attributes, a first sub-line is determined from multiple sub-lines to manage it. This first co-occupied virtual land is used to construct virtual buildings jointly owned by the first and second accounts. Thus, through the merging of virtual lands, the virtual objects controlled by players are no longer co-occupied in someone else's virtual building, but rather in a jointly owned virtual building, increasing the player's desire to adjust the virtual building and improving the user experience. Furthermore, since the co-occupied virtual building belongs to both the first and second accounts, they can directly adjust the virtual items within the co-occupied virtual building without prior communication, reducing communication costs and thus reducing server load.

[0233] As one possible implementation, if the first virtual land is displayed on the second sub-line and the second virtual land is displayed on the third sub-line before the merger, then after the first co-occupancy request is initiated from the first account to the second account, the first virtual land is unbound from the second sub-line and the second virtual land is unbound from the third sub-line.

[0234] Specifically, unbinding the first virtual land from the second sub-line is equivalent to deleting the first virtual land from the second sub-line. The second sub-line no longer manages the first virtual land, and the released virtual land in the second sub-line can be reallocated. Releasing the virtual land occupied by the first virtual land in the second sub-line changes its state from allocated to unallocated, allowing it to be re-bound to other virtual lands in the future.

[0235] Similarly, unbinding the second virtual land from the third sub-line is equivalent to deleting the second virtual land from the third sub-line. The third sub-line no longer manages the second virtual land, and the released virtual land in the third sub-line can be reallocated. Unbinding the second virtual land from the third sub-line releases the virtual land occupied by the second virtual land in the third sub-line, changing it from an allocated state to an unallocated state, so that it can be rebound with other virtual lands in the future.

[0236] Based on this, displaying the first shared virtual land on the first branch line can specifically involve binding the first shared virtual land to the unallocated virtual land on the first branch line, so that the virtual land on the first branch line changes from an unallocated state to an allocated state, thereby displaying the first shared virtual land on the first branch line. This is equivalent to transferring the first virtual land from the second branch line to the first branch line and transferring the second virtual land from the third branch line to the first branch line.

[0237] Therefore, managing virtual land through separate lines not only simplifies the management of multiple players, but also allows for changing virtual land communities through unbinding and binding, expanding players' social interactions, increasing users' exploration of different maps, and improving the user experience.

[0238] As one possible implementation, the consent of the applicant can be obtained through an application queue, as detailed in I1-I2.

[0239] I1: Place the first cohabitation request in the first application queue.

[0240] The first application queue is the application queue corresponding to the virtual land belonging to the second account, and is used to store co-living requests initiated to the first shared virtual land. The virtual land belonging to the second account can be a second virtual land that belongs solely to the second account, or it can be a shared virtual land jointly owned by the second account and other accounts. This application does not make specific limitations on this.

[0241] The first application queue includes at least one account belonging to the virtual land, which is a second account.

[0242] I2: If all accounts belonging to the virtual land corresponding to the first application queue agree to the first co-living request, then proceed to step S1102.

[0243] If all accounts belonging to the virtual land corresponding to the first application queue agree to the first co-occupancy request, it means that all co-occupants of the virtual land agree to the addition of the first account. Then, the aforementioned step S1102 is executed to determine the attributes of the first co-occupancy virtual land.

[0244] It should be noted that the first application queue can store multiple co-living requests, each of which can come from different accounts. When one of the multiple co-living requests in the first application queue is approved, the first application queue will be cleared, the two virtual lands will begin to merge, and after a new virtual land is generated, the first application queue can receive co-living requests for the new virtual land.

[0245] Therefore, by storing and processing co-living requests in the application queue, not only is there ample time for all co-livers of the virtual lands to be merged to agree, which is simple and quick, but it also ensures that the co-living is something that all co-livers like, thus improving the user experience.

[0246] As one possible implementation, it is possible not only to send co-living requests to other accounts, but also to send invitations to other accounts to co-living, see J1-J5 for details.

[0247] J1: Send an invitation to live together to the third account through the first account.

[0248] The "Invite to Share a Room" request is used to invite a third account to share a room with the first account. The third account is an account controlled by a third player, and the third account is a different account from the first account.

[0249] J2: If the third account agrees to the invitation to share a room, then the second request to share a room will be placed in the second application queue.

[0250] If the third account agrees to the invitation to share a room, it means that the third player corresponding to the third account agrees to share a room with the first account. At this time, you can take the initiative to help the third account initiate a second sharing request. This second sharing request is placed in the second application queue. The accounts that own the virtual land corresponding to the second application queue include the first account. That is, the second sharing request is initiated to the virtual land owned by the first account (which may be virtual land owned solely by the first account, or it may be shared virtual land jointly owned by the first account and other accounts).

[0251] It should be noted that since the third account passively sends the second co-living request to the second application queue through the invitation to live together initiated by the first account, the second co-living request assumes that the first account has already agreed. In other words, the first account does not need to agree to the second co-living request again, thereby reducing the number of operations required for the first account and improving the user experience.

[0252] J3: If all accounts belonging to the virtual land corresponding to the second application queue agree to the second co-occupancy request, then determine the attributes of the virtual land for the second co-occupancy.

[0253] The second shared virtual land is a virtual land obtained by merging the first virtual land and the third virtual land belonging to the third account. If all accounts belonging to the virtual land in the second application queue agree to the second shared land request, it means that everyone agrees to the third account sharing the land, thus determining the attributes of the second shared virtual land. The attributes of the second shared virtual land describe its nature and characteristics, such as shape, quantity, and size. The attributes of the second shared virtual land are used to assign suitable sub-landings to the second shared virtual land.

[0254] J4: From multiple sub-lines, determine the fourth sub-line that satisfies the attributes of the second shared virtual land.

[0255] J5: The second shared virtual land is displayed in the fourth sub-line.

[0256] For details regarding J4-J5, please refer to the aforementioned S1103-S1104, which will not be repeated here.

[0257] Therefore, the first account can send a co-living invitation to the third account. Once the third account agrees, it will automatically complete the co-living process for the third account, which means it will send a second co-living application for the third account. It will also be assumed that the first account has already agreed to the second co-living application. As long as other accounts also agree, the merging of the two virtual lands can begin. Thus, by inviting co-living requests, not only are the use cases for the co-living function expanded, but user operations are also reduced, improving the user experience.

[0258] As one possible implementation, this application embodiment also provides a separation function, see K1-K5 for details.

[0259] K1: Receive the split request from the first account.

[0260] The separation request can be generated by performing a trigger operation on the aforementioned separation control, as detailed in F1-F2 above.

[0261] A split request is used to request the return of the first virtual land from the first shared virtual land to the first account. Through a shared virtual land request, the first account can initiate a shared virtual land with a second account. Through a split request, the first account can end the shared virtual land, that is, leave with its own virtual land and return the first virtual land from the first shared virtual land.

[0262] K2: Unbind the first shared virtual land from the first branch line.

[0263] After the first virtual land is reclaimed from the first shared virtual land, it becomes the remaining virtual land. The remaining virtual land is the virtual land after removing the first virtual land from the first shared virtual land. The remaining virtual land continues to be bound to the first branch line, and occupying the position of the first shared virtual land may lead to the waste of resources of the first branch line. Therefore, the first shared virtual land can be unbound from the first branch line so that the remaining virtual land can be reallocated to a more suitable branch line.

[0264] Unbinding the first shared virtual land from the first sub-line is equivalent to deleting the first shared virtual land from the first sub-line. The first sub-line no longer manages the first shared virtual land, and the released virtual land in the first sub-line can be reallocated. Releasing the virtual land occupied by the first shared virtual land in the first sub-line changes its state from allocated to unallocated, allowing it to be re-bound to other virtual lands in the future.

[0265] K3: Determine the attributes of the first virtual land and the attributes of the remaining virtual lands.

[0266] The attributes of the first virtual land are used to describe its properties, such as shape, quantity, and size. These attributes are also used to assign suitable boundaries to the first virtual land.

[0267] The attributes of remaining virtual land are used to describe the properties and characteristics of the remaining virtual land, such as shape, quantity, and size. These attributes are also used to assign suitable boundaries to the remaining virtual land.

[0268] K4: From multiple sub-lines, determine the fifth sub-line that satisfies the first virtual land and the sixth sub-line that satisfies the remaining virtual land.

[0269] The fifth sub-line is suitable for allocation to the first virtual land, and the sixth sub-line is suitable for allocation to the remaining virtual land. The fifth sub-line may be the same as or different from the sixth sub-line; this application does not impose any specific limitations on this. In other words, from multiple sub-lines, new sub-lines are reallocated to the two separated virtual lands.

[0270] K5: The first virtual land is displayed on the fifth sub-line, and the remaining virtual land is displayed on the sixth sub-line.

[0271] For details regarding K4-K5, please refer to the aforementioned S1103-S1104, which will not be repeated here. The pseudocode for the splitting process is as follows:

[0272] SplitHouse()

[0273] 1. House.PreSplitHouse() / / Preprocesses and obtains initial virtual land information

[0274] 2 for each OldHouse

[0275] GetOneSepline() / / Pre-fetches a branch line; this branch line temporarily stops accepting land allocation requests.

[0276] 3 Sepline.PreDeleteHouse() / / Pre-delete shared virtual land from the branch line containing the shared virtual land.

[0277] 4 for each OldHouse

[0278] Sepline.AddHouse() / / Adds each virtual land to the pre-assigned subline.

[0279] 5. PostProcess(bSucc) / / Post-processing

[0280] 5.1 if bSucc: House.ConfirmSplitHouse()

[0281] Else: House.CancelSplitHouse()

[0282] 5.2 for each OldHouse:

[0283] Sepline.Unlock() / / Re-accept new land allocation requests

[0284] 5.3 if bSucc: Sepline.ConfirmDeleteHouse()

[0285] Else: Sepline.CancelDeleteHouse()

[0286] Furthermore, as mentioned above, the shared virtual land system records the initial virtual land for each account. For accounts applying for separation, the initial virtual land for that account will be restored, and the "delete" mark on the initial virtual land will be removed. For remaining virtual land, if the number of co-owners is greater than 1, co-ownership will continue. If the number of co-owners is equal to the number of users, the account's initial virtual land will be restored, and the relevant data for the shared virtual land will be deleted, as this data will not be reused.

[0287] As one possible implementation, a cooling-off period could be provided for split requests. Specifically, split requests could be stored in a maintenance queue to record players in the split cooling-off period. A first-in, first-out (FIFO) principle could be followed to execute split requests that have ended their cooling-off period. That is, the homestead service would attempt to retrieve the split request at the head of the queue; if the split request had already ended its cooling-off period, it would begin execution and be removed from the head of the queue.

[0288] Furthermore, a personalized cooling-off period can be set for each split request, so that when a split request in the maintenance queue meets the cooling-off period, the split request can be executed and removed from the maintenance queue.

[0289] Therefore, the co-living request allows virtual land belonging to multiple accounts to be merged, while the separation request allows users to detach from the co-living virtual land, making it an independent virtual land that is not merged with other virtual lands. Thus, the co-living and separation functions provide users with more freedom in social interaction and improve the user experience.

[0290] As one possible implementation, after splitting up, one can not only take their own virtual land with them, but also retrieve the virtual items they placed in the shared virtual building or shared virtual land. The following example uses taking the first virtual item from the shared virtual building as an example. Based on this, this application embodiment provides a specific implementation method for displaying the first virtual land in the fifth branch line of K5, see L1.

[0291] L1: Display the first virtual land on the fifth line, and display the first virtual building on the first virtual land.

[0292] If a first shared virtual building is also displayed on the first shared virtual land, and that first shared virtual building includes the first virtual item belonging to the first account, then after the first player sends a separation request, not only will the first virtual land belonging to the first account be reclaimed, but also the items belonging to the first account within the first merged virtual homestead, such as the first virtual building and the first virtual item, will be reclaimed. The reclaimed virtual items will be stored in the virtual inventory belonging to the first account. This avoids the loss of player assets, making both the shared and separation functions more flexible and requiring less deliberation from players, thus improving the user experience.

[0293] Furthermore, the first shared virtual building becomes a remaining virtual building because the first account is splitting up. The remaining virtual building only includes the remaining virtual items. That is, the remaining virtual building is the virtual building after removing the first virtual building from the first shared virtual building, and the remaining virtual items are the virtual items after removing the first virtual item from the virtual items displayed in the first shared virtual building.

[0294] For example, players can edit multiple plans for their shared virtual land, but only one plan can be applied to the real-world instance at a time. Therefore, when editing a plan, a player's virtual items = virtual items in their account's virtual inventory + virtual items from the edited plan corresponding to the real-world instance. When applying the edited plan corresponding to the real-world instance, the difference in the quantity of each virtual item compared to the original plan is calculated. Newly added virtual items are deducted from the player's inventory, and reduced virtual items are redistributed to the player's virtual inventory. For players sharing a virtual land, each player's virtual items = virtual items in their account's virtual inventory + their own virtual items from the edited plan corresponding to the real-world instance. Each virtual item in the edited plan corresponding to the real-world instance is recorded as belonging to a specific player. When applying the edited plan corresponding to the real-world instance, the difference in the quantity of virtual items for each player compared to the original plan is calculated. Newly added virtual items are deducted from the player's virtual inventory, and reduced virtual items are redistributed to the player's virtual inventory.

[0295] Therefore, by requesting a separation from a shared virtual land, i.e., becoming an independent virtual land that is not merged with other virtual lands, not only can the virtual land belonging to that account be reclaimed, but also other items belonging to that account can be reclaimed, such as virtual props placed in shared virtual buildings. Thus, based on the separation function, the loss of player assets is avoided, allowing users to socialize more freely and improving the user experience.

[0296] As one possible implementation, multiple players can also simultaneously adjust virtual items in shared virtual land or shared virtual buildings, see M1-M2 for details.

[0297] M1: If a virtual scene identifier from the first account and a virtual scene identifier from the second account are obtained, then the first virtual object and the second virtual object are controlled to enter the virtual editing scene corresponding to the virtual scene identifier.

[0298] The virtual scene identifier is used to enter the virtual editing scene. The virtual editing scene is a virtual scene for editing operations on the first shared virtual land. The first virtual object is a virtual object controlled by the first account, and the second virtual object is a virtual object controlled by the second account.

[0299] When a player initiates an edit operation, they will enter a new virtual editing scene to edit virtual items. Since shared virtual lands correspond to multiple players, all players need to enter the same editing scene instance. When sharing, the shared virtual land is pre-assigned a virtual scene identifier (WorldDBID), and multiple players sharing the same virtual land enter the same virtual editing scene by specifying the same virtual scene identifier.

[0300] In the Homestead service, the same virtual scene identifier corresponds to the same instance of a virtual editing scene. Therefore, players living together will enter the same instance of a virtual editing scene. Editing operations between multiple players are synchronized to other players' clients through the Area of ​​Interest (AOI), enabling collaborative editing. For example, this can be achieved using Blueprints to allow multiple players in a shared homestead to edit simultaneously. In edit mode, the program allocates a dedicated server (DS) in Unreal Engine (UE) to all players entering the same virtual editing scene. Players in a shared homestead will enter the same DS to edit. Within this DS, player animations and actions on third-party virtual items are synchronized, and the editing status of the third-party virtual items is changed. This ensures that players editing simultaneously can see each other's actions and the current status of their assets.

[0301] M2: If an edit operation is obtained for a third target virtual item in the first shared virtual building or the first shared virtual land, change the status of the third target virtual item to edit state.

[0302] The third target virtual prop is a virtual prop within the first shared virtual building or the first shared virtual land that has been edited by the second virtual object. Editing operations are operations performed on the third target virtual prop, such as moving or recycling operations; this application does not specifically limit this.

[0303] Multiple players can simultaneously adjust virtual items in shared virtual land or shared virtual buildings, and can see each other's adjustment process, thus avoiding disputes. For example, the first player can see the second player's editing operations on a third target virtual item. To distinguish it from other virtual items, the third target virtual item can be set to edit mode, such as by specially displaying or highlighting it. This application does not impose specific limitations on this.

[0304] As a result, multiple players can simultaneously perform editing operations on virtual items in shared virtual land or shared virtual buildings, and their editing operations are visible to each other. That is, the operation process is displayed synchronously, and the virtual item being edited will be in an edit state. This makes it easy for players to know which virtual item is being edited, thus avoiding multiple players editing the same virtual item at the same time, preventing competition, and improving the user experience.

[0305] As mentioned above, each virtual community is generally managed through a sub-line. When a player enters a virtual community through an account, it is equivalent to the player entering a sub-line through an account. Players on different sub-lines are not visible to each other. That is, players who enter the same sub-line or the same virtual community are visible to each other, such as being able to see each other's virtual land, virtual buildings, and virtual objects they control. This application does not specifically limit the definition of visibility.

[0306] Based on this, after the first shared virtual land is displayed through the virtual community corresponding to the first branch line, this application embodiment also provides a way to help players automatically refresh their virtual community, see N 1 for details.

[0307] N1: If the display duration of the first shared virtual land on the first sub-line is greater than the duration threshold, then the first shared virtual land will be displayed on the seventh sub-line.

[0308] The display duration of the first shared virtual land in the first sub-line refers to the duration during which the first shared virtual land is bound to the virtual community corresponding to the first sub-line, that is, the duration during which the first shared virtual land is placed in the first sub-line or displayed in the virtual community corresponding to the first sub-line.

[0309] If the display duration exceeds the duration threshold, it means that the first shared virtual land has been in the virtual community corresponding to the first sub-line for some time. At this point, in order to expand the player's social relationships, the virtual community where the first shared virtual land is located can be changed, such as changing it to the virtual community corresponding to the seventh sub-line, that is, the first shared virtual land will be displayed on the seventh sub-line. Note that the first sub-line and the seventh sub-line are different sub-lines, and the virtual communities corresponding to the first sub-line and the virtual communities corresponding to the seventh sub-line are different virtual communities.

[0310] This application does not specifically limit the time threshold, and those skilled in the art can set it according to actual needs. For example, it can be a week.

[0311] As one possible approach to reduce server load, all active shared virtual lands could be reassigned to different servers or virtual communities. An active shared virtual land refers to any account within that shared virtual land that has logged into the target application within a specified period prior to the current time. In other words, step N1 will only be executed if the first shared virtual community is an active shared virtual land, thus reducing server load.

[0312] For example, the Homestead Service assigns new sub-lines to all virtual lands or shared virtual lands weekly. When a sub-line is bound to a virtual land or shared virtual land, an expiration timestamp is recorded. Because there are many instances of virtual lands or shared virtual lands, and many are inaccessible for extended periods, the Homestead Service maintains an active virtual land list, which includes active virtual lands or shared virtual lands. Before their expiration time, new sub-lines are reassigned to all active virtual lands or shared virtual lands. Data related to old sub-lines is deleted from the database when they are no longer referenced.

[0313] In addition, a timer will be added after players log in, and the player will actively try to apply to the Home Service to be assigned a new virtual land before the land expires. If the virtual land or shared virtual land is not assigned a new land during global matchmaking, it will be reassigned, thus ensuring that inactive virtual land or shared virtual land can also obtain a new land.

[0314] Therefore, by changing the branch line of the first shared virtual land at fixed intervals, the virtual community can be changed. This not only expands the player's social circle by changing the virtual community, but also allows multiple accounts to change the virtual community at the same time, based on the shared virtual land. This is convenient and fast, while ensuring that multiple accounts still have the shared function, thus improving the user experience.

[0315] To facilitate a further understanding of the technical solutions provided in the embodiments of this application, the following description uses the execution subject of the co-living method based on virtual buildings provided in the embodiments of this application as a server, and takes a user-generated content (UGC) game as an example to provide an overall exemplary introduction to the co-living method based on virtual buildings.

[0316] In this application, after players create UGC (User-Generated Content) buildings, they can co-live and build together with others, with clear division of their furniture assets. Players can initiate co-living arrangements while already having their own residences, and the system will merge the players' current houses and land according to the rules. Multiple players can co-live together.

[0317] To address the issue of players sharing accommodations in the game, when constructing virtual communities within 3D art scenes, multiple closely connected and aligned virtual plots of land can be included, such as... Figure 7 As shown. Each player can place and build houses using UGC on their own land. When players initiate a co-living request, the system will remove the logical placement boundary restrictions on their respective lands, thus allowing players to co-live. See S401-S402 or S1101-S1104 above for details, which will not be repeated here.

[0318] Players sharing a room can place items or build their homes on the virtual land of two or more cohabiting members. See the four layout methods mentioned above for details.

[0319] The assets of cohabitants are handled as follows: (1) Each cohabitant can place their own furniture (virtual props) on the shared virtual land after cohabitation. At this time, cohabitants can stack and place their own furniture and the other party's furniture, and the specific operations are the same as their own stacking and placement. (2) Each cohabitant can operate and move the furniture that other cohabitants have placed in the virtual editing scene. (3) Each cohabitant can reclaim the furniture that other cohabitants have placed in the virtual editing scene. After reclamation, the furniture will return to its original owner's virtual backpack. (4) Cohabitants cannot directly use the props that cohabitants still have in their virtual backpacks for placement. However, they can use the virtual props in the shared virtual backpack for placement. The virtual props in the shared backpack can be placed by cohabitants, and each cohabitant can reclaim their own virtual props.

[0320] Furthermore, the solution to the cohabitation / separation issue is as follows: In cohabitation situations, players are allowed to separate their virtual land. Separation means that each player returns to their virtual land state before cohabitation and divides their assets. See F1-F2 or K1-K5 for details.

[0321] When players initiate a co-op session, the program records the ownership of each player's items within the co-op scenario. When players divide assets, the items will be returned to their respective inventory points according to ownership. See G1 or L1. This solution ensures that players do not lose virtual items due to co-op, improving the player experience.

[0322] Therefore, this application embodiment allows players to co-live in multiplayer communities and achieve virtual land merging; virtual land merging can be performed on existing art scenes with fewer restrictions; it better solves the problems of joint construction and asset management for players in co-living situations; and it solves the problem of co-living for more than two players, enabling larger-scale co-living. Thus, it achieves at least the following effects:

[0323] (1) Multi-player co-living innovation: Allows multiple players to truly live together in a 3D virtual scene, merge each other's virtual lands, and use each other's virtual assets for placement and construction, greatly promoting social interaction.

[0324] (2) Realization of multi-player co-construction: Based on solving the problem of multiple people living together, multi-player co-construction is realized, which allows multiple players to share each other's virtual props and materials to carry out joint construction, thus solving the problems of prop sharing, synchronization and storage.

[0325] (3) The community matching experience is more humanized: Based on the players' living arrangements and the actual art scene, the players are matched. At the same time, the players' friend relationships are also taken into account when the community matching is carried out, which is conducive to some players with social potential to form a more advanced social relationship.

[0326] In response to the virtual building-based cohabitation method described above, this application also provides a corresponding virtual building-based cohabitation device, so that the above-mentioned virtual building-based cohabitation method can be applied and implemented in practice.

[0327] See Figure 12 This figure is one of the structural schematic diagrams of a shared living arrangement based on a virtual building, provided in an embodiment of this application. Figure 12 As shown, the virtual building-based co-living device 1200 includes: a first display unit 1201 and a second display unit 1202;

[0328] The first display unit 1201 is used to display a co-living control, which is used to initiate a first co-living request to a second account through a first account. The first account has a first virtual land and the second account has a second virtual land.

[0329] The second display unit 1202 is used to display a first shared virtual land obtained by merging the first virtual land and the second virtual land in response to a trigger operation on the shared living control. The first shared virtual land is used to construct virtual buildings that belong to both the first account and the second account.

[0330] As can be seen from the above technical solution, a shared living control is displayed, which is used to initiate a first shared living request from a first account to a second account. The first account owns a first virtual land, and the second account owns a second virtual land. Through the shared living control, the first and second virtual lands can be merged; that is, in response to a trigger operation on the shared living control, the first shared virtual land, resulting from the merger of the first and second virtual lands, is displayed. This first shared virtual land is used to construct virtual buildings jointly belonging to both the first and second accounts. Thus, through the merging of virtual lands, the virtual objects controlled by the players are no longer shared in someone else's virtual building, but rather in a jointly owned virtual building, increasing the player's desire to adjust the virtual building and improving the user experience. Furthermore, since the shared virtual building belongs to both the first and second accounts, they can subsequently directly adjust the virtual items within the shared virtual building without prior communication, reducing communication costs and thus reducing server load.

[0331] As one possible implementation, the second display unit 1202 is specifically used for:

[0332] In response to a trigger operation on the shared living control, a first target virtual community is determined among the multiple virtual communities based on the number of vacant virtual lands included in each of the multiple virtual communities. The number of vacant virtual lands included in the first target virtual community is greater than or equal to the number of the first shared living virtual lands. The vacant virtual lands are virtual lands without an account.

[0333] The first shared virtual land is displayed in the first target virtual community, which is obtained by merging the first virtual land and the second virtual land.

[0334] As one possible implementation, the second display unit 1202 is specifically used for:

[0335] In response to a trigger operation on the co-living control, based on the number of vacant virtual lands included in each of the plurality of virtual communities, a plurality of undetermined virtual communities are determined among the plurality of virtual communities, wherein the number of vacant virtual lands included in the undetermined virtual communities is greater than or equal to the number of the first co-living virtual lands.

[0336] Display each of the aforementioned pending virtual communities;

[0337] In response to a trigger operation targeting a target virtual community among the plurality of pending virtual communities, the target virtual community is identified as the first target virtual community.

[0338] As one possible implementation, the second display unit 1202 is specifically used for:

[0339] If the display duration of the first shared virtual land in the first target virtual community exceeds a duration threshold, the first shared virtual land is displayed in the second target virtual community, and the second target virtual community and the first target virtual community are different virtual communities.

[0340] As one possible implementation, if a first virtual building belonging to the first account is displayed on the first virtual land, and a second virtual building belonging to the second account is displayed on the second virtual land, then the second display unit 1202 is specifically used for:

[0341] In response to a trigger operation on the shared living control, the first shared living virtual land is displayed, and a first shared living virtual building, which is a result of merging the first virtual building and the second virtual building, is displayed on the first shared living virtual land. The first shared living virtual building belongs to both the first account and the second account.

[0342] As one possible implementation, the virtual building-based co-living device 1200 further includes an operating unit for:

[0343] Place the first virtual item belonging to the first account in the first shared virtual building or the first shared virtual land, wherein the first shared virtual building is a virtual building displayed on the first shared virtual land; or,

[0344] Move the second virtual item belonging to the second account within the first shared virtual building or the first shared virtual land; or...

[0345] Select a first target virtual item from the shared virtual backpack, and place the first target virtual item in the first shared virtual building or the first shared virtual land. The shared virtual backpack belongs to both the first account and the second account; or...

[0346] Recover the second target virtual item placed in the first shared virtual building or the first shared virtual land;

[0347] If the second target virtual item belongs to the first account, then the second target virtual item is stored in the virtual backpack belonging to the first account;

[0348] If the second target virtual item belongs to the second account, then the second target virtual item is stored in the virtual backpack belonging to the second account.

[0349] As one possible implementation, the virtual building-based co-living device 1200 further includes a third display unit for:

[0350] Displays a first virtual object controlled by the first account and a second virtual object controlled by the second account;

[0351] In response to the second virtual object performing an editing operation on a third target virtual prop in the first shared virtual building or the first shared virtual land, the third target virtual prop in the editing state is displayed.

[0352] As one possible implementation, the virtual building-based co-living device 1200 further includes a fourth display unit for:

[0353] Display a separation control, which is used to reclaim the first virtual land from the first shared virtual land and give it back to the first account;

[0354] In response to a trigger operation on the separate control, the first virtual land is displayed;

[0355] Wherein, the first shared virtual land becomes the remaining virtual land, which is the virtual land obtained by removing the first virtual land from the first shared virtual land.

[0356] As one possible implementation, if the first shared virtual land is obtained based on the first virtual land and the second virtual land, then the remaining virtual land is the second virtual land;

[0357] If the first shared virtual land is obtained from the first virtual land, the second virtual land, and the third virtual land belonging to the third account, then the remaining virtual land is obtained based on the second virtual land and the third virtual land.

[0358] As one possible implementation, if a first shared virtual building is displayed on the first shared virtual land, and the first shared virtual building is a virtual building obtained based on a first virtual building belonging to the first account and a second virtual building belonging to the second account, and the first shared virtual building includes a first virtual item belonging to the first account, then the fourth display unit is specifically used for:

[0359] In response to a trigger operation on the split control, the first virtual land is displayed, and the first virtual building is displayed on the first virtual land;

[0360] In this process, the first shared virtual building becomes the remaining virtual building, and the remaining virtual building includes remaining virtual items. The remaining virtual building is obtained by removing the virtual items belonging to the first virtual building from the first shared virtual building. The remaining virtual items are obtained by removing the first virtual items from the virtual items displayed in the first shared virtual building. The first virtual items are stored in the virtual backpack belonging to the first account.

[0361] As one possible implementation, the virtual building-based co-living device 1200 further includes a fifth display unit for:

[0362] A second co-living request is displayed from a fourth account, which is directed at the first account;

[0363] If the first virtual land and the second virtual land are merged and displayed as the first shared virtual land, then in response to both the first account and the second account agreeing to the second shared request, the second shared virtual land is displayed. The second shared virtual land is a virtual land obtained based on the first virtual land, the second virtual land, and the fourth virtual land belonging to the fourth account.

[0364] If the virtual land belonging to the first account is displayed independently, then in response to the first account agreeing to the second co-living request, a third co-living virtual land is displayed, which is a virtual land obtained based on the first virtual land and the fourth virtual land.

[0365] As one possible implementation, the first display unit 1201 is specifically used for:

[0366] In response to a triggered operation targeting the content, the co-living control is displayed, wherein the target content is the second account, a virtual building belonging to the second account, the second virtual land, or a second virtual object controlled by the second account; or,

[0367] The second display unit 1202 is specifically used for:

[0368] In response to a trigger operation on the shared living control, multiple pending target contents corresponding to each account are displayed. The pending target contents are accounts, virtual buildings belonging to the accounts, virtual land belonging to the accounts, or virtual objects controlled by the accounts.

[0369] In response to the selection operation for the target content from the plurality of pending target content, the account corresponding to the target content is determined as the second account, and the first shared virtual land obtained by merging the first virtual land and the second virtual land is displayed.

[0370] See Figure 13 This figure is a second structural schematic diagram of a shared living arrangement based on a virtual building, provided in an embodiment of this application. Figure 13 As shown, the virtual building-based co-living device 1300 includes: an initiation unit 1301, a determination unit 1302, and a display unit 1303;

[0371] The initiating unit 1301 is used to initiate a first co-living request to a second account through a first account. The first co-living request is used to request the merging of a first virtual land belonging to the first account and a second virtual land belonging to the second account.

[0372] The determining unit 1302 is used to determine the attributes of the first shared virtual land, which is a virtual land obtained by merging the first virtual land and the second virtual land;

[0373] The determining unit 1302 is further configured to determine, from multiple branch lines, a first branch line that satisfies the attributes of the first shared virtual land;

[0374] The display unit 1303 is used to display the first shared virtual land on the first branch line.

[0375] As can be seen from the above technical solution, a first co-occupancy request is initiated from the first account to the second account. The first account possesses a first virtual land, and the second account possesses a second virtual land. Through this first co-occupancy request, the first and second virtual lands can be merged to obtain a first co-occupied virtual land. To allocate this first co-occupied virtual land, based on its attributes, a first branch line is determined from multiple branch lines to meet those attributes, and this first branch line manages the first co-occupied virtual land. This first co-occupied virtual land is used to construct virtual buildings jointly belonging to both the first and second accounts. Thus, through the merging of virtual lands, the virtual objects controlled by players are no longer co-occupied in someone else's virtual building, but rather in a jointly owned virtual building, increasing the player's desire to adjust the virtual building and improving the user experience. Furthermore, since the co-occupied virtual building belongs to both the first and second accounts, they can subsequently directly adjust the virtual items within the co-occupied virtual building without prior communication, reducing communication costs and thus reducing server load.

[0376] As one possible implementation, the virtual building-based co-living device 1300 further includes an unbinding unit for:

[0377] If the first virtual land is displayed on the second branch line and the second virtual land is displayed on the third branch line, after the first cohabitation request is initiated from the first account to the second account, the first virtual land is unbound from the second branch line and the second virtual land is unbound from the third branch line.

[0378] The display unit 1303 is specifically used for:

[0379] The first shared virtual land is bound to the unassigned virtual land on the first branch line to display the first shared virtual land on the first branch line, which is different from the second branch line and different from the third branch line.

[0380] As one possible implementation, the virtual building-based co-living device 1300 further includes an application unit for:

[0381] After the first co-living request is initiated from the first account to the second account, the first co-living request is placed in the first application queue, and the account to which the virtual land corresponding to the first application queue belongs includes the second account;

[0382] If all accounts belonging to the virtual land corresponding to the first application queue agree to the first co-living request, then the step of determining the attributes of the first co-living virtual land is executed.

[0383] As one possible implementation, the virtual building-based co-living device 1300 also includes an invitation unit for:

[0384] The first account sends an invitation to the third account to share a room;

[0385] If the third account agrees to the invitation to share a room, the second request to share a room is placed in the second application queue. The account to which the virtual land belongs in the second application queue includes the first account, and the first account agrees to the second request to share a room.

[0386] If all accounts belonging to the virtual land in the second application queue agree to the second co-living request, then the attribute of the second co-living virtual land is determined. The second co-living virtual land is a virtual land obtained by merging the first virtual land and the third virtual land belonging to the third account.

[0387] From the plurality of branch lines, determine the fourth branch line that satisfies the attributes of the second shared virtual land;

[0388] The second shared virtual land is displayed on the fourth branch line.

[0389] As one possible implementation, the virtual building-based co-living device 1300 also includes a separate unit for:

[0390] Obtain the split request from the first account;

[0391] Unbind the first shared virtual land from the first branch line;

[0392] Determine the attributes of the first virtual land and the attributes of the remaining virtual land, wherein the remaining virtual land is the virtual land remaining after removing the first virtual land from the first shared virtual land;

[0393] From the plurality of sub-lines, determine the fifth sub-line that satisfies the first virtual land and the sixth sub-line that satisfies the remaining virtual land;

[0394] The first virtual land is displayed on the fifth sub-line, and the remaining virtual land is displayed on the sixth sub-line.

[0395] As one possible implementation, if a first shared virtual building is displayed on the first shared virtual land, and the first shared virtual building is a virtual building obtained based on a first virtual building belonging to the first account and a second virtual building belonging to the second account, and the first shared virtual building includes a first virtual item belonging to the first account, then the separation unit is specifically used for:

[0396] The first virtual land is displayed on the fifth line, and the first virtual building is displayed on the first virtual land;

[0397] In this process, the first shared virtual building becomes the remaining virtual building, and the remaining virtual building includes remaining virtual items. The remaining virtual building is obtained by removing the virtual items belonging to the first virtual building from the first shared virtual building. The remaining virtual items are obtained by removing the first virtual items from the virtual items displayed in the first shared virtual building. The first virtual items are stored in the virtual backpack belonging to the first account.

[0398] As one possible implementation, the virtual building-based co-living device 1300 further includes a simultaneous editing unit for:

[0399] If a virtual scene identifier from the first account and a virtual scene identifier from the second account are obtained, then the first virtual object and the second virtual object are controlled to enter the virtual editing scene corresponding to the virtual scene identifier. The virtual scene identifier is used to enter the virtual scene for editing the first shared virtual land. The first virtual object is a virtual object controlled by the first account, and the second virtual object is a virtual object controlled by the second account.

[0400] If an edit operation is performed on a third target virtual item in the first shared virtual building or the first shared virtual land, the state of the third target virtual item is changed to edit state.

[0401] As one possible implementation, the virtual building-based co-living device 1300 further includes a refresh unit for:

[0402] If the display duration of the first shared virtual land on the first branch line is greater than the duration threshold, then the first shared virtual land will be displayed on the seventh branch line. The first branch line and the seventh branch line are different branches.

[0403] This application also provides a computer device, which can be a server or a terminal device. The computer device provided in this application will be described below from a hardware implementation perspective. Figure 14 The diagram shown is a structural schematic of the server. Figure 15 The diagram shown is a structural schematic of the terminal device.

[0404] See Figure 14This figure is a schematic diagram of a server structure provided in an embodiment of this application. The server 1400 can vary considerably due to different configurations or performance. It may include one or more processors 1422, such as a central processing unit (CPU), memory 1432, and one or more storage media 1430 (e.g., one or more mass storage devices) for application programs 1442 or data 1444. The memory 1432 and storage media 1430 can be temporary or persistent storage. The program stored in the storage media 1430 may include one or more modules (not shown in the figure), each module may include a series of instruction operations on the server. Furthermore, the processor 1422 may be configured to communicate with the storage media 1430 and execute the series of instruction operations in the storage media 1430 on the server 1400.

[0405] Server 1400 may also include one or more power supplies 1426, one or more wired or wireless network interfaces 1450, one or more input / output interfaces 1458, and / or one or more operating systems 1441, such as Windows Server. TM Mac OS X TM Unix TM Linux TM FreeBSD TM etc.

[0406] The steps performed by the server in the above embodiments can be based on this Figure 14 The server structure shown.

[0407] The processor 1422 is used to perform the following steps:

[0408] Display a co-living control, which is used to initiate a first co-living request from a first account to a second account, wherein the first account has a first virtual land and the second account has a second virtual land;

[0409] In response to a trigger operation on the shared living control, a first shared living virtual land, obtained by merging the first virtual land and the second virtual land, is displayed. The first shared living virtual land is used to construct virtual buildings that jointly belong to the first account and the second account.

[0410] Or perform the following steps:

[0411] The first account initiates a first co-occupancy request to the second account, which is used to request the merging of the first virtual land belonging to the first account with the second virtual land belonging to the second account.

[0412] Determine the attributes of the first shared virtual land, which is a virtual land obtained by merging the first virtual land and the second virtual land;

[0413] From multiple branch lines, determine the first branch line that satisfies the attributes of the first shared virtual land;

[0414] The first shared virtual land is displayed on the first branch line.

[0415] Optionally, the processor 1422 may also execute method steps of any specific implementation of the cohabitation method based on virtual buildings in the embodiments of this application.

[0416] See Figure 15 This figure is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. The description will be based on a smartphone as an example. Figure 15 The diagram shown is a block diagram of a portion of the structure of the smartphone, which includes: a radio frequency (RF) circuit 1510, a memory 1520, an input unit 1530, a display unit 1540, a sensor 1550, an audio circuit 1560, a Wi-Fi module 1570, a processor 1580, and a power supply 1590, among other components. Those skilled in the art will understand that... Figure 15 The smartphone structure shown does not constitute a limitation on smartphones and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0417] The following is combined with Figure 15 A detailed introduction to the various components of a smartphone:

[0418] The RF circuit 1510 can be used to receive and transmit signals during information transmission or calls. In particular, it receives downlink information from the base station and processes it with the processor 1580; in addition, it transmits uplink data to the base station.

[0419] The memory 1520 can be used to store software programs and modules, and the processor 1580 runs the software programs and modules stored in the memory 1520 to realize various functions and data processing of the smartphone.

[0420] The input unit 1530 can be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the smartphone. Specifically, the input unit 1530 may include a touch panel 1531 and other input devices 1532. The touch panel 1531, also known as a touch screen, can collect touch operations from the user on or near it and drive corresponding connected devices according to a pre-set program. In addition to the touch panel 1531, the input unit 1530 may also include other input devices 1532. Specifically, other input devices 1532 may include, but are not limited to, one or more of the following: a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, a joystick, etc.

[0421] The display unit 1540 can be used to display information input by the user or information provided to the user, as well as various menus of a smartphone. The display unit 1540 may include a display panel 1541, which may optionally be configured as a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0422] Smartphones may also include at least one sensor 1550, such as a light sensor, a motion sensor, and other sensors. Other sensors that smartphones may also be equipped with, such as gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be detailed here.

[0423] Audio circuit 1560, speaker 1561, and microphone 1562 provide an audio interface between the user and the smartphone. Audio circuit 1560 converts received audio data into electrical signals and transmits them to speaker 1561, where speaker 1561 converts them into sound signals for output. On the other hand, microphone 1562 converts collected sound signals into electrical signals, which are received by audio circuit 1560, converted into audio data, and then processed by processor 1580 before being transmitted via RF circuit 1510 to, for example, another smartphone, or the audio data can be output to memory 1520 for further processing.

[0424] The processor 1580 is the control center of the smartphone, connecting various parts of the smartphone through various interfaces and lines. It performs various functions and processes data by running or executing software programs and / or modules stored in the memory 1520, and by calling data stored in the memory 1520. Optionally, the processor 1580 may include one or more processing units.

[0425] The smartphone also includes a power supply 1590 (such as a battery) that supplies power to various components. Preferably, the power supply can be logically connected to the processor 1580 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.

[0426] Although not shown, smartphones may also include a camera, Bluetooth module, etc., which will not be described in detail here.

[0427] In this embodiment of the application, the memory 1520 included in the smartphone can store computer programs and transmit the computer programs to the processor.

[0428] The processor 1580 included in the smartphone can execute the virtual building-based cohabitation method provided in the above embodiments according to the instructions in the computer program.

[0429] This application also provides a computer-readable storage medium for storing a computer program for executing the virtual building-based cohabitation method provided in the above embodiments.

[0430] On the other hand, embodiments of this application provide a computer program product including a computer program that, when run on a computer device, causes the computer device to perform the co-living method based on virtual buildings provided in various optional implementations of the above aspects.

[0431] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium can be at least one of the following media: read-only memory (ROM), RAM, magnetic disk or optical disk, and other media that can store computer programs.

[0432] The terms “first,” “second,” “third,” “fourth,” etc., as used in this application (if applicable), are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “corresponding,” and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0433] In the embodiments of this application, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0434] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects detailed in this application.

[0435] The terminology used in this application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The singular forms “a,” “the,” and “the” used herein are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more of the associated listed items. Depending on the context, the word “if,” as used herein, can be interpreted as “when,” “in response to a determination,” or “when…”.

[0436] It should be noted that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for the device and system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiments. The device and system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of the solution in this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0437] The above description is merely one specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Based on the implementation methods provided in the above aspects, this application can also be further combined to provide more implementation methods.

Claims

1. A method for cohabitation based on virtual architecture, characterized in that, The method includes: Display a co-living control, which is used to initiate a first co-living request from a first account to a second account, wherein the first account has a first virtual land and the second account has a second virtual land; In response to a trigger operation on the shared living control, a first shared living virtual land, obtained by merging the first virtual land and the second virtual land, is displayed. The first shared living virtual land is used to construct virtual buildings that jointly belong to the first account and the second account.

2. The method according to claim 1, characterized in that, The response to a trigger operation on the shared accommodation control, displaying a first shared accommodation virtual land obtained by merging the first virtual land and the second virtual land, includes: In response to a trigger operation on the shared living control, a first target virtual community is determined among the multiple virtual communities based on the number of vacant virtual lands included in each of the multiple virtual communities. The number of vacant virtual lands included in the first target virtual community is greater than or equal to the number of the first shared living virtual lands. The vacant virtual lands are virtual lands without an account. The first shared virtual land is displayed in the first target virtual community, which is obtained by merging the first virtual land and the second virtual land.

3. The method according to claim 2, characterized in that, In response to a trigger operation on the shared living control, determining a first target virtual community among the multiple virtual communities based on the number of vacant virtual land parcels included in each virtual community includes: In response to a trigger operation on the co-living control, based on the number of vacant virtual lands included in each of the plurality of virtual communities, a plurality of undetermined virtual communities are determined among the plurality of virtual communities, wherein the number of vacant virtual lands included in the undetermined virtual communities is greater than or equal to the number of the first co-living virtual lands. Display each of the aforementioned pending virtual communities; In response to a trigger operation targeting a target virtual community among the plurality of pending virtual communities, the target virtual community is identified as the first target virtual community.

4. The method according to claim 2, characterized in that, The method further includes: If the display duration of the first shared virtual land in the first target virtual community exceeds a duration threshold, the first shared virtual land is displayed in the second target virtual community, and the second target virtual community and the first target virtual community are different virtual communities.

5. The method according to claim 1, characterized in that, If a first virtual building belonging to the first account is displayed on the first virtual land, and a second virtual building belonging to the second account is displayed on the second virtual land, then the step of responding to the trigger operation of the co-living control by displaying the first co-living virtual land obtained by merging the first virtual land and the second virtual land includes: In response to a trigger operation on the shared living control, the first shared living virtual land is displayed, and a first shared living virtual building, which is a result of merging the first virtual building and the second virtual building, is displayed on the first shared living virtual land. The first shared living virtual building belongs to both the first account and the second account.

6. The method according to claim 1, characterized in that, The method further includes: Place the first virtual item belonging to the first account in the first shared virtual building or the first shared virtual land, wherein the first shared virtual building is a virtual building displayed on the first shared virtual land; or, Move the second virtual item belonging to the second account within the first shared virtual building or the first shared virtual land; or... Select a first target virtual item from the shared virtual backpack, and place the first target virtual item in the first shared virtual building or the first shared virtual land. The shared virtual backpack belongs to both the first account and the second account; or... Recover the second target virtual item placed in the first shared virtual building or the first shared virtual land; If the second target virtual item belongs to the first account, then the second target virtual item is stored in the virtual backpack belonging to the first account; If the second target virtual item belongs to the second account, then the second target virtual item is stored in the virtual backpack belonging to the second account.

7. The method according to claim 6, characterized in that, The method further includes: Displays a first virtual object controlled by the first account and a second virtual object controlled by the second account; In response to the second virtual object performing an editing operation on a third target virtual prop in the first shared virtual building or the first shared virtual land, the third target virtual prop in the editing state is displayed.

8. The method according to claim 1, characterized in that, The method further includes: Display a separation control, which is used to reclaim the first virtual land from the first shared virtual land and give it back to the first account; In response to a trigger operation on the separate control, the first virtual land is displayed; Wherein, the first shared virtual land becomes the remaining virtual land, which is the virtual land obtained by removing the first virtual land from the first shared virtual land.

9. The method according to claim 8, characterized in that, If the first shared virtual land is obtained based on the first virtual land and the second virtual land, then the remaining virtual land is the second virtual land; If the first shared virtual land is obtained from the first virtual land, the second virtual land, and the third virtual land belonging to the third account, then the remaining virtual land is obtained based on the second virtual land and the third virtual land.

10. The method according to claim 8, characterized in that, If a first shared virtual building is displayed on the first shared virtual land, and the first shared virtual building is a virtual building obtained based on a first virtual building belonging to the first account and a second virtual building belonging to the second account, and the first shared virtual building includes a first virtual item belonging to the first account, then the step of displaying the first virtual land in response to the trigger operation of the separation control includes: In response to a trigger operation on the split control, the first virtual land is displayed, and the first virtual building is displayed on the first virtual land; In this process, the first shared virtual building becomes the remaining virtual building, and the remaining virtual building includes remaining virtual items. The remaining virtual building is obtained by removing the virtual items belonging to the first virtual building from the first shared virtual building. The remaining virtual items are obtained by removing the first virtual items from the virtual items displayed in the first shared virtual building. The first virtual items are stored in the virtual backpack belonging to the first account.

11. The method according to claim 1, characterized in that, The method further includes: A second co-living request is displayed from a fourth account, which is directed at the first account; If the first virtual land and the second virtual land are merged and displayed as the first shared virtual land, then in response to both the first account and the second account agreeing to the second shared request, the second shared virtual land is displayed. The second shared virtual land is a virtual land obtained based on the first virtual land, the second virtual land, and the fourth virtual land belonging to the fourth account. If the virtual land belonging to the first account is displayed independently, then in response to the first account agreeing to the second co-living request, a third co-living virtual land is displayed, which is a virtual land obtained based on the first virtual land and the fourth virtual land.

12. The method according to claim 1, characterized in that, The display control includes: In response to a triggered operation targeting the content, the co-living control is displayed, wherein the target content is the second account, a virtual building belonging to the second account, the second virtual land, or a second virtual object controlled by the second account; or, The response to a trigger operation on the shared accommodation control, displaying a first shared accommodation virtual land obtained by merging the first virtual land and the second virtual land, includes: In response to a trigger operation on the shared living control, multiple pending target contents corresponding to each account are displayed. The pending target contents are accounts, virtual buildings belonging to the accounts, virtual land belonging to the accounts, or virtual objects controlled by the accounts. In response to the selection operation for the target content from the plurality of pending target content, the account corresponding to the target content is determined as the second account, and the first shared virtual land obtained by merging the first virtual land and the second virtual land is displayed.

13. A method of cohabitation based on virtual architecture, characterized in that, The method includes: The first account initiates a first co-occupancy request to the second account, which is used to request the merging of the first virtual land belonging to the first account with the second virtual land belonging to the second account. Determine the attributes of the first shared virtual land, which is a virtual land obtained by merging the first virtual land and the second virtual land; From multiple branch lines, determine the first branch line that satisfies the attributes of the first shared virtual land; The first shared virtual land is displayed on the first branch line.

14. The method according to claim 13, characterized in that, If the first virtual land is displayed on the second branch line and the second virtual land is displayed on the third branch line, after initiating the first co-living request from the first account to the second account, the method further includes: Unbind the first virtual land from the second branch line, and unbind the second virtual land from the third branch line; The display of the first shared virtual land on the first branch line includes: The first shared virtual land is bound to the unassigned virtual land on the first branch line to display the first shared virtual land on the first branch line, which is different from the second branch line and different from the third branch line.

15. The method according to claim 13, characterized in that, After initiating the first cohabitation request from the first account to the second account, the method further includes: The first cohabitation request is placed in the first application queue, and the account to which the virtual land corresponding to the first application queue belongs includes the second account; If all accounts belonging to the virtual land corresponding to the first application queue agree to the first co-living request, then the step of determining the attributes of the first co-living virtual land is executed.

16. The method according to claim 13, characterized in that, The method further includes: Send a request to share a room to the third account through the first account; If the third account agrees to the invitation to share a room, the second request to share a room is placed in the second application queue. The account to which the virtual land belongs in the second application queue includes the first account, and the first account agrees to the second request to share a room. If all accounts belonging to the virtual land in the second application queue agree to the second co-living request, then the attribute of the second co-living virtual land is determined. The second co-living virtual land is a virtual land obtained by merging the first virtual land and the third virtual land belonging to the third account. From the plurality of branch lines, determine the fourth branch line that satisfies the attributes of the second shared virtual land; The second shared virtual land is displayed on the fourth branch line.

17. The method according to claim 13, characterized in that, The method further includes: Obtain the split request from the first account; Unbind the first shared virtual land from the first branch line; Determine the attributes of the first virtual land and the attributes of the remaining virtual land, wherein the remaining virtual land is the virtual land remaining after removing the first virtual land from the first shared virtual land; From the plurality of sub-lines, determine the fifth sub-line that satisfies the first virtual land and the sixth sub-line that satisfies the remaining virtual land; The first virtual land is displayed on the fifth sub-line, and the remaining virtual land is displayed on the sixth sub-line.

18. The method according to claim 17, characterized in that, If a first shared virtual building is displayed on the first shared virtual land, and the first shared virtual building is a virtual building obtained based on the first virtual building of the first account and the second virtual building belonging to the second account, and the first shared virtual building includes a first virtual item belonging to the first account, then displaying the first virtual land on the fifth branch line includes: The first virtual land is displayed on the fifth line, and the first virtual building is displayed on the first virtual land; In this process, the first shared virtual building becomes the remaining virtual building, and the remaining virtual building includes remaining virtual items. The remaining virtual building is obtained by removing the virtual items belonging to the first virtual building from the first shared virtual building. The remaining virtual items are obtained by removing the first virtual items from the virtual items displayed in the first shared virtual building. The first virtual items are stored in the virtual backpack belonging to the first account.

19. The method according to claim 13, characterized in that, The method further includes: If a virtual scene identifier from the first account and a virtual scene identifier from the second account are obtained, then the first virtual object and the second virtual object are controlled to enter the virtual editing scene corresponding to the virtual scene identifier. The virtual scene identifier is used to enter the virtual scene for editing the first shared virtual land. The first virtual object is a virtual object controlled by the first account, and the second virtual object is a virtual object controlled by the second account. If an edit operation is performed on a third target virtual item in the first shared virtual building or the first shared virtual land, the state of the third target virtual item is changed to edit state.

20. The method according to claim 13, characterized in that, The method further includes: If the display duration of the first shared virtual land on the first branch line is greater than the duration threshold, then the first shared virtual land will be displayed on the seventh branch line. The first branch line and the seventh branch line are different branches.

21. A co-living device based on virtual architecture, characterized in that, The device includes: a first display unit and a second display unit; The first display unit is used to display a co-living control, which is used to initiate a first co-living request to a second account through a first account. The first account has a first virtual land, and the second account has a second virtual land. The second display unit is configured to, in response to a trigger operation on the shared living control, display a first shared living virtual land obtained by merging the first virtual land and the second virtual land, wherein the first shared living virtual land is used to construct virtual buildings that jointly belong to the first account and the second account.

22. A co-living device based on virtual architecture, characterized in that, The device includes: an initiation unit, a determination unit, and a display unit; The initiating unit is used to initiate a first co-living request to a second account through a first account. The first co-living request is used to request the merging of a first virtual land belonging to the first account and a second virtual land belonging to the second account. The determining unit is used to determine the attributes of the first shared virtual land, which is a virtual land obtained by merging the first virtual land and the second virtual land; The determining unit is further configured to determine, from multiple sub-lines, a first sub-line that satisfies the attributes of the first shared virtual land; The display unit is used to display the first shared virtual land on the first branch line.

23. A computer device, characterized in that, The computer device includes a processor and memory: The memory is used to store computer programs and to transfer the computer programs to the processor; The processor is configured to perform the method according to any one of claims 1-13, or the method according to any one of claims 14-20, based on the computer program.

24. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program for performing the method according to any one of claims 1-13, or for performing the method according to any one of claims 14-20.

25. A computer program product comprising a computer program, characterized in that, When it is run on a computer device, it causes the computer device to perform the method of any one of claims 1-13, or the method of any one of claims 14-20.

Images