In the past, I have used multiple LIB tokens to accomplish different tasks. I have my main LIB with my onCampaignLoad and all my macro functions, I have my inventory LIB that keeps a list of all my game items and has no macros, and I have a wiki LIB that holds all the descriptions and flavor text for all the skills, perks and items in the game.
I wanted to ask if this is the normal way of using LIB tokens, or if there's any advantage/disadvantage to using one LIB for multiple tasks. Should I be using more LIB tokens? Can these tokens exist on one map in the campaign or do they have to exist in multiples? And how do yo guys make your LIB tokens part of the map without being obvious. I had been making mine a map compass, but having more than one just looks strange.
I'm rewriting my game for about (I think?) the fourth time, and I'd like to have as many best practice aspects so I never have to rewrite it a fifth time.
Thanks!
One LIB, Two LIB, Red LIB, Blue LIB
Moderators: dorpond, trevor, Azhrei
Forum rules
Posting now open to all registered forum users.
Posting now open to all registered forum users.
Re: One LIB, Two LIB, Red LIB, Blue LIB
I try to stick to one lib per project. One reason is portability, but I've had multiple lib tokens for a project when involving large data where the 2nd lib serves as an alternate data base to the main lib. But that is rare.
Downloads:
- Notepad++ MapTool addon
- RPEdit details (v1.3)
- Coding Tips: Modularity and Design
- Videos: Macro Writing Tools
Re: One LIB, Two LIB, Red LIB, Blue LIB
Definitely one map to rule them all, so you can easily find them. And as alias said, less is better. There might be issues when one lib contains HUGE amounts of data, eg more than 10000 data entries in a property. Overall unless it's practical for portability to split them up, like with the bot, don't.
GETTING STARTED WITH MAPTOOLS - TUTORIALS, DOCS, VIDEOS, TOOLS, ETC
DISCORD (the new MT forum!)
My stuff
Excel Tools: Table and Light editors
MT Tools: Bag of Tricks: Tools for Maptool, Dungeon Builder I, Dungeon Builder II,onMouseOverEvent.
Frameworks: Dark Heresy, Rogue Trader, Deathwatch, Black Crusade, Only War, SET Card Game, RoboRally
Wiki: Debugging Tutorial, Speed Up Your Macros, Working With Two CODE Levels, Shortcut Keys, Avoiding Stack Overflow, READ THIS
DISCORD (the new MT forum!)
My stuff
Excel Tools: Table and Light editors
MT Tools: Bag of Tricks: Tools for Maptool, Dungeon Builder I, Dungeon Builder II,onMouseOverEvent.
Frameworks: Dark Heresy, Rogue Trader, Deathwatch, Black Crusade, Only War, SET Card Game, RoboRally
Wiki: Debugging Tutorial, Speed Up Your Macros, Working With Two CODE Levels, Shortcut Keys, Avoiding Stack Overflow, READ THIS
Re: One LIB, Two LIB, Red LIB, Blue LIB
Just for fun I am going to disagree with the experts. I really don't like monster Libs that do everything, which is why, as far as possible, I tend to go for separate Libs that have specific areas of functionality. I find it just so much easier to manage and its yet to cause me any problems. You still tend to end up with some large Libs though
My current campaign has 5 Libs, for example.
My current campaign has 5 Libs, for example.
Re: One LIB, Two LIB, Red LIB, Blue LIB
I think that's more or less what I said. One lib per project. For example, I have a lib for healing and another for handling adventure dialog. Both are functional, but still a WIP which is why I haven't shared them yet. But I do plan to merge a couple of lib tokens with similar functionality, but during the development process I like to have them separate.
Downloads:
- Notepad++ MapTool addon
- RPEdit details (v1.3)
- Coding Tips: Modularity and Design
- Videos: Macro Writing Tools
Re: One LIB, Two LIB, Red LIB, Blue LIB
same here. 5 libs sounds about right... lets seealiasmask wrote:I think that's more or less what I said. One lib per project. For example, I have a lib for healing and another for handling adventure dialog. Both are functional, but still a WIP which is why I haven't shared them yet. But I do plan to merge a couple of lib tokens with similar functionality, but during the development process I like to have them separate.
lib:ontokenmove (macros of the BoT)
lib:eventmacros (settings and campaign specific stuff for the BoT)
lib:w40k (macro for framework)
lib:ships (macro set for rogue trader specific ship battles of framework)
lib:data (data for framework)
lib:armies (w40k test project)
lib:rpedit (macro editor tool)
lib:tokenprops (tool to check properties of tokens)
and im probly forgetting a couple
ok so more than 5.
for the framework, the w40k contains all core macros for the 5 systems. Then for rogue trader specific there is also ship battles, hence seperate, same for a specific army related project. I've also seperated data and campaign specific properties in a seperate lib and then there are the additional tools.
GETTING STARTED WITH MAPTOOLS - TUTORIALS, DOCS, VIDEOS, TOOLS, ETC
DISCORD (the new MT forum!)
My stuff
Excel Tools: Table and Light editors
MT Tools: Bag of Tricks: Tools for Maptool, Dungeon Builder I, Dungeon Builder II,onMouseOverEvent.
Frameworks: Dark Heresy, Rogue Trader, Deathwatch, Black Crusade, Only War, SET Card Game, RoboRally
Wiki: Debugging Tutorial, Speed Up Your Macros, Working With Two CODE Levels, Shortcut Keys, Avoiding Stack Overflow, READ THIS
DISCORD (the new MT forum!)
My stuff
Excel Tools: Table and Light editors
MT Tools: Bag of Tricks: Tools for Maptool, Dungeon Builder I, Dungeon Builder II,onMouseOverEvent.
Frameworks: Dark Heresy, Rogue Trader, Deathwatch, Black Crusade, Only War, SET Card Game, RoboRally
Wiki: Debugging Tutorial, Speed Up Your Macros, Working With Two CODE Levels, Shortcut Keys, Avoiding Stack Overflow, READ THIS
Re: One LIB, Two LIB, Red LIB, Blue LIB
I'm glad you specified what you meant by project. Initially I had thought you mean one Lib for one campaign, but you (and everyone else) meant more of one Lib per task per campaign. I'll keep on doing what I have been, as it sounds like I have it right (in theory, at least. In practice, my stuff is a mess).aliasmask wrote:I try to stick to one lib per project.
Thanks!
Re: One LIB, Two LIB, Red LIB, Blue LIB
I also misunderstood what people meant by project. I stand corrected