K Relay plugin ideas

Use K_script_help.txt and port anything from RR to K...

Wow thanks without that we wouldn't have known how packets work

/s

Thread is pointless without any /s

Should not even be a plugin but a core feature imho . Why calling it proxy if you can only connect to the nexus and cant use portals?

same for /con (change server)

->Dye /Pet/ Skin modifiers
->Allyshoot block
->Enhanced Spam filter ->Block packets containing certain text pattern, public or pm chat only, WITH OPTION TO AUTO IGNORE THE FUCKER
Easy to do.

Russian shop and notifuckers bots cant reach me anymore

->Custom vault layout (so funnny in marinep)
->glow
->Auto pot
->Auto Loot (more efficiant than in client from what i see)
->/who ->how many players in realm
->Auto thessal answering
->Loot bag quest (may be a bit tricky)

Thank you for the serious reply, we indeed moved recon handling to the core, and /connect brings up a gui with server select.
Will look into the ideas you brought out

I forgot
* Fame notification
*old school loot notification
* CLIENTSTAT announcer

What do you mean by "clientstat announcer"?

what about:
*an auto ability for classes like warrior, paladin and priest (when below hp threshold)
*maybe a timer for the rogue cloak

planned and soon to be in the works. I got a whole lotta free time now

great, i have some more ideas:
-a command to check your current roll
-a notification that shows your dps (it's probably not that useful but it might be fun)
-a command like /search "item id" that outputs all the players that have that item

- - - Updated - - -

inb4 /search inc... :/

Dunno how to call that, but what about a 'Core Plugin' that will be used for all other mods

What i'm doing in my fork of RR, is having a World class that is used to store a representation of the current map

This way all your mods could grab data from the World, and no more duplicate code

I'm not sure i have correctly explained the idea but here is a snippet:



World world;

each time you receive MAPINFO -> reset the world
each time you receive CREATESUCCESS -> store your ids
each time you receive UPDATE -> you add/remove objects (store a reference of the current player using what you got in CREATESUCCESS)
each time you receive NEWTICK -> you update your world



This way, all the mods will easily have access to : the current Player, an array of the objects present in the world etc..

We considered doing most of that, and came to the conclusion that it's ultimately not worth the performance and memory costs.
However, each Client instance maintains statdata for its player, with a few extra things like ClassType and MapName, all of which is easily accessible to plugins.
We also added command hooks, to remove all the boiler plate code to get commands parsed and working for each plugin.
Thanks for your suggestions