Post: #2

honestly I don't get the point, but anyway, on sphere 56d it will first read TAG.NOTO.HUE, and if there's nothing set it will use default noto color from sphere.ini. But this doesn't change the notoriety value, it only change the name color

on the other hand, @NotoSend overrides the entire notoriety, noto value and noto color set here will be saved on char memories, but afaik the purpose here is only change noto X to another noto Y that already exists (eg: change red to gray, consider red as blue, etc) instead create more notoriety values. You can also keep the default noto values and also change its color, eg: you can keep blue notoriety as blue (NotoGood), but showing light blue on humans and dark blue on gargoyles. If you change the color here you don't have to change it again using TAG.NAME.HUE

@NotoSend is called every time sphere calculate an notoriety (usually when every new char appears on screen). Sphere will keep all noto on cache for X seconds (NotoTimeOut) to avoid too much recalculations. Sphere already call all the notoriety code internally and any modern hardware can handle this with no drawbacks but we must always alert ppl to avoid heavy codes on these triggers