Open BoGuu opened 8 years ago
Yeah you could have 2 columns in the database, Tanoa Houses and Altis Houses and depending on the worldName retrieve.
I do like this idea, ive seen alot of communitys having both maps because people prefer Tanoa for RP (most of the time) however not everyone has the dlc so have the altis up as a backup and for those who dont like Tanoa
Yep, a worldName
column would be perfect.
Or just let people create a new house table and figure it out themselves. Because what if they plan on doing 2 Tanoa servers instead of Altis & Tanoa... Idk, I'd just let them figure out how to change a few sql statements to use a new table for the new server...
Surely It wouldn't matter? Most servers have two Altis servers so they can accept more players. The houses are shared anyway between server. The point of using the same database is so that players data is consistent
Why would you make it so players can just hop from an underpopulated server to a populated and have the same house and such? You'd have two servers and just restrict players on housing. Why not essentially increase your housing capacity, since you're increasing player capacity. w/e in the end idgaf.
Fair play, I was just looking at what all servers do atm as they dont have the option to not share housing. However this could be a option to toggle, i still think most community would want sharing of homes. The servers big enough to afford and maintain 2 servers are the ones where server #1 lets say is always full so the second is used as a overflow allowing players to still access there house even tho they cant get on there main one.
There is plenty of houses on Tanoa to support 2 Tanoa servers. The idea of this is purely aimed at communities wishing to open a second server to support a larger player base. Which isn't currently too feasible (without changes) on two different maps.
Nothing is stopping people from using two different schema ofcourse.
I really think that adding a worldName column is unnecessary, If someone wants to run two different servers, it's really not that hard to have them point to different housing tables in the same database
As i said before we could have it so it auto detects the world name and then chooses the appropriate table. I think the thing were trying to do here is make the mission/framework easier for the end user to use.
@dbenson24
The point is, it's two changes, each of which are a couple of words, just for ease. Won't affect anything at all. Just nice to give people the option instead of faffing with tables etc.
i would like to see this option implemented
Should we update the houses/containers SQL to support the input of worldName, thus allowing people to use the same database for two maps? They ofcourse work independently, but if you ran both a Tanoa and Altis server off the same database, it would try incorrectly assign non-existent houses.
This would allow a community to run both maps, and allow synced persistence across them.
Thoughts?