Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Quest Type: Cross Server Quests. #7

Closed
3 tasks
Pychnight opened this issue Dec 25, 2017 · 0 comments
Closed
3 tasks

New Quest Type: Cross Server Quests. #7

Pychnight opened this issue Dec 25, 2017 · 0 comments
Assignees
Labels

Comments

@Pychnight
Copy link
Owner

Pychnight commented Dec 25, 2017

Add new lua feature to send the player to anther server during a quest.
Ensure during the "transfer" quest is not aborted, and continued on the other server.

This requires support for external mysql databases for Leveling, Housing, Quests Plugin.
This also requires both servers to have the same plugin and server scripts for the quest, otherwise it will error out or abort the quest.

New commands for server transfer
Room names are defined within the config file and alias for each room.
/lobby join (room name)
/lobby leave (sends you back to the previous server)
/lobby list (checks server list and status (player count + online / offline) )

  • admins commands

/lobby send (forces a player to join targeted lobby / server)

New lua Functions to send the party over to the new server

party:sendconnect("ip","port")

  • Find a good way to report player count back to one server / combined total for sub servers
  • ensure all server report there status to the lobbies admin command (should also work on the sub-servers
  • Custom Connect Message during loading screen (seen this once before)
  • Track other player data for Custom Achievements system (future plugin), all servers will be using one database, so this should be really easy.

Player Data that should be tracked
#10 Mentions this data
QuestStart Time, Quest Finish time (this is per quest, think as this as a anti-cheat or ladder board type data, though with cross server quests, not sure how you would handle this to ensure the data for actually finishing the quest is correct)
Quests Completed
Quests Unlocked

  • Also acceptable would be isolated instanced quests / regions, would be acceptable too.
  • however, we will need to find a way to prevent the server from refreshing that region / tiles for a extremely long period of time and deal with player joining / leaving
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants