Changing default Unique spawnpoint

12/16/2018 09:40 MrCatGardens#1

Hey guys,
I'm wondering how I can change the default spawnpoints after Serverrestart.
I've tried to get the logic by Tab_RefNest, but it seems the NestID is choosen randomly, but will never change :)

I've alot of spawnpoints for a new unique, but i have no clue how i could change the points after an inspection. So is there any way to get random NestIDs working?

Cheers

12/16/2018 12:26 #HB#2

RefNest isn't chosen randomly, it just depends on time. The original uniques like (Tiger Girl, Uruchi, Captain Ivy, Isyutaru, Lord Yarkan, Demon Shaitan) nearly has exceptions at the server files, so they might be chosen randomly and they don't respawn till their death.

But any other unique just re-spawns with the delay given at Tab_RefNest, you can change the spawn point through Tab_RefNest & Tab_RefHive, Tab_RefHive contains the world ID of the spawning, Tab_RefNest contains the region ID, postions X,Y,Z.

12/16/2018 13:43 MrCatGardens#3

Quote:

Originally Posted by #HB

RefNest isn't chosen randomly, it just depends on time. The original uniques like (Tiger Girl, Uruchi, Captain Ivy, Isyutaru, Lord Yarkan, Demon Shaitan) nearly has exceptions at the server files, so they might be chosen randomly and they don't respawn till their death.

But any other unique just re-spawns with the delay given at Tab_RefNest, you can change the spawn point through Tab_RefNest & Tab_RefHive, Tab_RefHive contains the world ID of the spawning, Tab_RefNest contains the region ID, postions X,Y,Z.

I appreciate your answer but I think you got me wrong :)
Let me explain what I mean^^
After a serverrestart, the common uniques like TG, Cerb and so on will spawn at a fixed place. This place never changes, like in isro. Inspection done -> Shaitan at Wing Peak, TG at Bandit's Mountain, Cerb left from Desperado Hill.

Now I have added some other Uniques to an area (lets say arabia uniques at samarkand with 20 spawnpoints each). These Uniques have also exactly ONE "default" spawnplace after inspection. Serverrestart -> they are again at the same spot. Next serverrestart -> again at this spot.

So how does this works? Theres no "flag" or sth else at DB to tell the game, this place is the default one.

12/16/2018 14:45 #HB#4

So, you mean that the unique re-spawns always at the same place or after every restart, the first spawn of a unique is the same spot?

12/16/2018 14:47 MrCatGardens#5

Quote:

Originally Posted by #HB

So, you mean that the unique re-spawns always at the same place or after every restart, the first spawn of a unique is the same spot?

exactly this...

12/16/2018 21:39 #HB#6

Probably GS loads the spots in a list with ordered by NestID and a flag of spawn, and starts to pick up depending on NestID order and the flag of spawn. Example: This is a game server spots list,

Code:

Ordered NestID  |   RefMobCode    |              Spot                |    Spawned Times
1               |  MOB_OA_URUCHI  |  Whatever, Middle of Tarim Basin |         0
2               |  MOB_OA_URUCHI  |  Whatever, North of Tarim Basin  |         0
3               |  MOB_OA_URUCHI  |  Whatever, West of Tarim Basin   |         0

So, it starts to pick up the monster with the least spawn times with the order of NestID, so its gonna pick the NestID 1 above.

But, if the list is like this,

Code:

Ordered NestID  |   RefMobCode    |              Spot                |    Spawned Times
1               |  MOB_OA_URUCHI  |  Whatever, Middle of Tarim Basin |         1
2               |  MOB_OA_URUCHI  |  Whatever, North of Tarim Basin  |         1
3               |  MOB_OA_URUCHI  |  Whatever, West of Tarim Basin   |         0

It's gonna pick the NestID 3.

Code:

Ordered NestID  |   RefMobCode    |              Spot                |    Spawned Times
1               |  MOB_OA_URUCHI  |  Whatever, Middle of Tarim Basin |         2
2               |  MOB_OA_URUCHI  |  Whatever, North of Tarim Basin  |         2
3               |  MOB_OA_URUCHI  |  Whatever, West of Tarim Basin   |         2

Pick NestID 1, ...etc

Note: That's just a prediction of GS's behaviour.