Matrim Cauthon Jr Wrote:Ellie Wrote:Matrim Cauthon Jr Wrote:We had another thread about this. And not one in every town. How about one in all 6 towns you deliver letters too?
Eh. But only half the guilds who would probably use it (that are outside Pront) are in those 6 towns.
Then you have NE in Rachel, What is still around of LW? in Hugel, Rev in Gon...
Those guilds can use one of the other 6 when they want. It's not hard. Seriously.
Posting here because it's the more recent thread.
I agree with Matrim, though to be fair depending how modifications to the NPCs and maps work on eAthena it might not be hard to populate every town with a DB warper and it's own private room either.
If the NPCs are just triggers (when X is clicked do Y) with pointers (load map Z) then duplicate NPCs could be scripted (such as the warper and save NPCs) with pointers to to multiple instances of our existing private DB room.
In other words, if we assume that the Pront private DM room is the master map "privateDBroom", we would then make several copies of that same map with different names to be referenced (i.e. privateDBroom_pay, privateDBroom_lou, etc.) by the multiple DB warper NPCs. We would then clone the DP warper npc and give them similar references (DBwarper_pay, DBwarper_lou, etc.). Each warper NPC would then be slightly tweaked to point to their respective map as opposed to pointing to the original master master map while the rest of their scripting remains the same and voila!, multiple DB warpers and private rooms.
Of course, this is all assuming that the eAthena environment is as robust and malleable as that. But even if it doesn't function exactly like I've outlined here, I don't imagine it'd be so different as to greatly increase the amount of work that would be needed to achieve the same result. After all, most programmers want to spend as little time writing code as possible