Blockland Forums > Modification Help
Iban Explains it All
Nexus:
Any situation where someone creates a weapon addon, or any addon with a projectile, usually has a non-packaged collision function. Many special playertypes do the same thing with arrmor::ontrigger.
Any worthwhile chatmod completely overwrites servercmdmessagesent.
Just a few common examples
Greek2me:
--- Quote from: Stocking on May 09, 2011, 08:46:54 PM ---I struggle to imagine even one scenario in which it would be advantangeous, ethical, and practical to overwrite core game functionality without a way to disable or turn the effect off.
--- End quote ---
The ONLY way to properly modify chat, as Nexus just said, is to completely overwrite serverCmdMessageSent. I had to overwrite it and completely rebuild it so I could change the name color in chat based on team.
Stocking:
--- Quote from: Nexus on May 10, 2011, 01:11:58 AM ---Any situation where someone creates a weapon addon, or any addon with a projectile, usually has a non-packaged collision function. Many special playertypes do the same thing with arrmor::ontrigger.
Any worthwhile chatmod completely overwrites servercmdmessagesent.
Just a few common examples
--- End quote ---
You're not overwriting core default functionality when you are creating scripts for your specific add-on.
ConsoleObject
- Lots of other Classes -
ProjectileData Namespace
Specific ProjectileData
Specific Projectile
All you're doing is adding a function for your Specific ProjectileData. If you were to write something over the ProjectileData namespace, that would be core functionality.
--- Quote from: Greek2me on May 10, 2011, 06:05:13 PM ---The ONLY way to properly modify chat, as Nexus just said, is to completely overwrite serverCmdMessageSent. I had to overwrite it and completely rebuild it so I could change the name color in chat based on team.
--- End quote ---
Rewriting any function, including serverCmdMessageSent and serverCmdTeamMessageSen, is considered a hack. While it's true that the structure of the chat system is rigid and hardcoded so it's not possible to add your own colors, that doesn't excuse the fact that it's still considered a hack to rewrite how the chat system works. Hacks should always be considered a last resort and these sorts of exceptions are not even worth the merit of including in a post about the Parent/Package system because if you're resorting to a hack you're already reaching a point of desperation and ethics are irrelevant.
takato14:
--- Quote from: takato14 ---So what you're saying is that there is NO function that spawns a debris datablock. Nope, dont buy that.
--- End quote ---
Would still appreciate some help here...
Nexus:
--- Quote from: Stocking on May 10, 2011, 09:52:20 PM ---You're not overwriting core default functionality when you are creating scripts for your specific add-on.
--- End quote ---
I was mostly referring to the questions about packaging, but it is considered overwriting default functionality. Honestly it is a bit of a stretch to call much anything "core" unless it has something to do with torque itself.
--- Quote from: takato14 on May 10, 2011, 10:06:49 PM ---Would still appreciate some help here...
--- End quote ---
Try a trace for when derbies are spawned.