I'm trying my best. I am at the top of the PAMM list right now. and my sig sends back to this thread. what else could I do? a steam page? my mod is PTE-compatible and probably stable incompatible in it's current state. cheers ! EDIT: drats they changed the shader again! back to figuring it out!
As I wrote in moldez's thread, you only need to change the icon_atlas.css file to use 32x32 pixel images, and the icons will work. If you want the icon highlighting to work, the previous code no longer works, but you can just copy what Uber does or what I did in my version to get it to work as before.
hi, first thank you for your job, next I want to report a bug on the insalation with PAMM. When I click on install I have an error message and i can't instal it.
my mod works???? last I left it it was completely dysfunctional. lemme give you a version that at least doesn't have this awful bug you see. https://dl.dropboxusercontent.com/u/22720750/FAFicons_v.14.zip the shader probably doesn't work. someone else's may look better but you may have to find a middle ground between mine and yours. I don't think there much demand at all for this mod. if it truns out there is i'll get back to making it.
so far looks like I can't get around this bug and it isn't on my end. none of the changes i make on the config file are taken into account by pamm, it's using it's own copy. you'll have to ask @proeleert or @raevn if you replace the text in : Uber Entertainment/Planetary Annihilation/client_mods/mods.json with this: Code: { "mount_order": [ "com.pa.tatsu.FAFicons", "com.pa.deathbydenim.dpamm" ] } it runs but as predicted the shader makes the icons show up yellow and white..... not so great EDIT : i changed the link above with a download that fixed the icon colors in a temporary way : none of the icon color changing happens when selecting a unit. and also the included patched mods.json file that will drop in the right place and overwrite the old. (it will deactivate all other mods but you can reactivate them on top without an issue) these are IMO the best mods PAMM has to offer. EDIT: oh yeah and don't click on "update" on my mod or "update all" it'll just replace it with the old version that doesn't work.
I know. and I'm currently working on making it even better. https://forums.uberent.com/threads/help.68221
just joking x'D I just thought this was hilarious personally. trying to learn git, so far from linux (and on a terminal) it's playing much nicer than on windows. can I please be told whether I made any mistakes thus far? :
I think you are mixing up stuff. Either create your own repository on GitHub and use "git init" or clone pamods, add your mod with the others (including as zip), commit and push. I personally prefer the first method, but either method works.
could you give me some extra details, since I'm REALLY new to this (if not to say a total noob) what do you mean by the first method, and what about the second? I only see one method in your reply. also is there a method that doesn't involve downloading all of pamods on my tiny SSD? a step by step guide would make my day! found this : To add new files to the repository or add changed files to staged area: $ git add <files> To commit them: $ git commit To commit unstaged but changed files: $ git commit -a To push to a repository (say origin): $ git push origin To push only one of your branches (say master): $ git push origin master To fetch the contents of another repository (say origin): $ git fetch origin To fetch only one of the branches (say master): $ git fetch origin master To merge a branch with the current branch (say other_branch): $ git merge other_branch Note that origin/master is the name of the branch you fetched in the previous step from origin. Therefore, updating your master branch from origin is done by: $ git fetch origin master $ git merge origin/master
Well, what I normally do: Go to GitHub.com and create a new repository. In the next paste it shows you the commands you can copy-paste in the terminal. They've made it pretty easy. And, yeah, with "git add" you can add your files to be tracked by git and with "git commit" you can submit the changes. "git push" will upload the commited changes to GitHub. On GitHub, you can draft "Releases". I use that the make a static link to a certain version of my mod for use with PAMM. For example, my structure looks like this: https://github.com/DeathByDenim/mines_as_strips
No, since it is your own repository that you created on your own GitHub account, only you have write access to it. It's possible to add others on GitHub though. The second method I was talking about in my first post is a giant repository (called pamods) with multiple authors (36!) and multiple mods. It all depends on what you want.
I'm willing to sacrifice the skin on my back if I can upload my updates to my mod to PAMM on my own like a big boy. that's all I want. does the method with my own repo allow me to do this are there more steps (that involve more babysitting of poor old tatsu)? If downloading the whole PAMM collection allows me to make a push to my own mod quick and easy then fine.
@DeathByDenim whyyyyy why is this so haaaard? the command guide from git you talked about no longer exists, I know what you mean because i saw this : here's what it looks like now : no more tutorial. you're right git. fu*k noobs. how do I tell it to include recursively all files in the current dir to the commit/push