Hello,
There seem to be no documented variables, triggers, or macros for that purpose, hence effective money-pack info (and global.cfg info in general) is likely just one more among the many kinds of data-sets that OMSI simply never bothered exposing to its users. Then again documentation has always been lacking, so, who knows, maybe there actually just so happens to be some arcane variable/trigger/macro after all, mentioned somewhere in the depths of these fora...
In the meantime one could of course always attempt to write an OMSI plugin that parses the global.cfg (but which one of them all? there's no reliable way of programmatically telling which map you're currently on -- only which hof your vehicle has been assigned to), or alternatively dumps the OMSI process's memory, so as to extract the targeted information and ultimately communicate it back to specific vehicle script variables for further processing. It's just a question of cost vs benefit.
(Edit) Maybe the most reasonable compromise would be a mere ".hof-constant":
Then in the script:
Lastly in the model.cfg you can swap textures in the usual ways (e.g. via [matl_item], [visible], ...). When the currency variable is 0 you can assume a default texture you'd use most often (I'd guess EUR or DM), so that you're not forced to specify that default in every .hof-file.
