[21:14] <FBIagent> just look at http://pastebin.ca/382635
[21:14] <@DrLecter> hi FBIagent
[21:14] <@DrLecter> lemme see
[21:14] <yellowperil> npcid,poly id,ondie,onattack,hp level, timer
[21:15] <FBIagent> condition is a varchar value
[21:15] <yellowperil> npcid1, npcid2,ondie,0,0
[21:15] <yellowperil> npcid2,npcid3,onattack,50%,0
[21:15] <yellowperil> npcid3,npcid4,ontattcke,0,0
[21:15] <FBIagent> if you just have one poly id per mob it's not flexible
[21:15] <yellowperil> npcid4,0,ondie,50
[21:16] <FBIagent> i mean
[21:16] <FBIagent> gremlin -> rabit -> gramlin
[21:16] <yellowperil> basically the last 0 on the poly would restart the task on the original spawn after the timer
[21:16] <FBIagent> rabit -> arch angel -> gremlin
[21:16] <yellowperil> dont specify the last one
[21:16] <yellowperil> keep it as 0
[21:17] <yellowperil> this will tell it to reactive the original task to respawn
[21:17] <@DrLecter> is it hp or chance?
[21:17] <yellowperil> hp %
[21:17] <FBIagent> if rabit have value to poly to gremlin rabit would never can poly to arch angel
[21:17] <FBIagent> just example
[21:18] <@DrLecter> is that the leak way?
[21:18] <yellowperil> well mostly the id's go in numerical order
[21:18] <@DrLecter> aehm.. offie i mean :P
[21:18] <FBIagent> so you need to create for each different poly more npc just to get poly working flexible
[21:18] <yellowperil> we do this on the npcid not the spawnid
[21:18] <FBIagent> soem mobs will poly to more the just one
[21:19] <FBIagent> arch angel -> gremlin -> cherebus -> gremlin -> archangel
[21:19] <yellowperil> its this from retail ?
[21:19] <yellowperil> or for mods
[21:19] <yellowperil> cos that sounds more like on spawnid not npcid
[21:19] <FBIagent> just example to show you implement most flexible is better
[21:19] <FBIagent> what is if
[21:20] <FBIagent> arch angel -> cherebus -> gremlin -> arch angel -> gremlin
[21:20] <yellowperil> ok for the time benig lets just get it to reatil
[21:20] <yellowperil> not a mod
[21:20] <FBIagent> arch angel can only hold one poly id so only one of the archangel -> will work
[21:20] <yellowperil> this npcid goes to this npcid
[21:20] <yellowperil> then your wanting to do it on spawnid
[21:20] <FBIagent> what is if they change it in the future rewrite the whole thing?
[21:21] <yellowperil> yes, but most likely they will not
[21:21] <FBIagent> i thinks that's not the right way
[21:21] <FBIagent> like my item handlers they are flexible for future when something changes
[21:21] <yellowperil> well the issue atm is we need npcid to poly to this npcid
[21:21] <yellowperil> the way your stating it, is on spawnid
[21:22] <yellowperil> that means for every archangle we would need an ebtry
[21:22] <@DrLecter> i dont think they'll spawn some second instance of a mob that has no drops after one that have them
[21:22] <FBIagent> why you are against new tables T-T
[21:22] <yellowperil> there could be hundreds
[21:22] <yellowperil> basically your saying we make a list per spawnid, am i wrong ?
[21:23] <yellowperil> donig it by npcif we have one entry for 100 spawns
[21:23] <FBIagent> i poly list for the npcid who need it
[21:23] <FBIagent> a
[21:23] <@DrLecter> ya, npcid should be the way imo too
[21:23] <FBIagent> but with new table T_T
[21:23] <yellowperil> basically atm there is a handful of mobs npcid's that poly to the next, we dont need to do it on spawnid
[21:24] <yellowperil> otherwise we create a whole DB of stuff
[21:24] <yellowperil> we dont really need
[21:25] <@DrLecter> yellowperil: shrap talon tigers are suposed to poly onAttack, in retail this is triggered by chance or hp level?
[21:25] <yellowperil> plus we are writing code that really may not be used ever except for moders
[21:25] <FBIagent> http://pastebin.ca/382635 http://pastebin.ca/382643 http://pastebin.ca/382644
[21:25] <yellowperil> i think most is on hp
[21:25] <yellowperil> or a mixture of hp and chance
[21:25] <FBIagent> till now it just support ondie
[21:25] <yellowperil> eg hp goes under % then chance of something
[21:25] <FBIagent> just need to check things in the right place
[21:26] <yellowperil> I think just doing it on a random % would be sufficient
[21:26] <@DrLecter> from what i read sometimes they get poly just on the first hit
[21:26] <yellowperil> we need onhp%,ondie
[21:26] <@DrLecter> should read the AI
[21:26] * @DrLecter goes and read
[21:26] <FBIagent> anyway somebody should write ai
[21:27] <FBIagent> all this things should be handled there
[21:27] <yellowperil> lol
[21:27] <yellowperil> ai per npcid would be sweet
[21:28] <yellowperil> but for the time being we just need a npcid,polyid,ondie,onhp%,timer
[21:28] <yellowperil> nothing more complex I think is needed
[21:28] <@DrLecter> we're back to the ai topic, but once again, we should add this sort of stuff to provide support until we have it
[21:28] <@DrLecter> yellowperil: whats the timer good for?
[21:29] <FBIagent> and few days ago i read "we should do things most user friendly"
[21:29] <FBIagent> why then not do it most flexible?
[21:30] <yellowperil> last mob
[21:30] <FBIagent> i think this is the first thing to change to get user to use L2J original, not uncluding custim stuff but be able to add custom stuff by admins
[21:30] <FBIagent> for there servers
[21:30] <@DrLecter> what the customization ease has to do with poly support?
[21:31] <yellowperil> eg poly should pause the task for the first spawn (not poly), and then the poly are done on there own spawn, the last one wont have a polyid, but a timer, this would in effect, time the restart of the paused task for the oringal spawn
[21:31] <FBIagent> it was just a hint
[21:31] <@DrLecter> (FBIagent im not fully against another table if there's a must to have it)
[21:31] <FBIagent> in some thread there where written more user friendly things but when implementing things with districtions it's not user firendly
[21:32] *** Steuf (n=Steuf@val59-1-89-84-107-24.dsl.club-internet.fr) joined
[21:32] <Steuf> Hi