Toggle shoutbox
Shoutbox
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Mods.
#4
Posted 05 February 2013 - 12:07 PM
creating mods =/= using themMake a copy before doing this or FairPlay fucks up. But I thought mods were against the rules? Wasn't there just a massive topic on deadman using mods? Whatever.
and some shits allowed that doesnt change textures n shit
like http://www.demobase..../20586-fp-ui-2/
Edited by bing bang blaow, 05 February 2013 - 12:08 PM.
#6
Posted 06 February 2013 - 01:34 AM
I've already included ingame serverlist in my fp ui(check the link I gave you before) along with some other useful features.I would like to make like an in game name maker like rpm full. And have a server list and some cool rcon page.
I noticed formatting of the original post was fucked up and so were the links to fp ui down, so I updated that post quickly.
What you mentioned(ingame name maker, server list, blahblah) all comes down to modifying the contents in /ui folder inside assets.pk3. As I said, use winrar to extract the stuff, when you are packing it all together make sure to make it into .zip first and then rename it to .pk3 (.rar wont work afaik!)
Even if you don't want to use that fp ui shit personally, you could still download it and use it as an example to what to do to achieve what you want. there's probably shitload of messy and not useful code written in it as well but I didn't really bother cleaning it up cause it works just as it is. you can compare whatever I/fox/ross did with the original files and figure out how it works that way.
#8
Posted 06 February 2013 - 02:32 AM
to do specifically what you brought up: http://www.linux.ucl...u/q3tamenu.htmlBut how would i make a mod from scratch?
this is all user interface related. if you want to do more complex things like what RPM implemented you should get into various programming languages(q3 engine is written in C i think?).
but I still believe that at first you should just experiment with the original files using trial and error. I only used this site when I wanted to create something really really specific. also it's 1000 times easier when you modify the original files to your liking because you don't have to (re)write everything you aren't modding, what I mean is that the EXIT button is already in the code and you probably aren't gonna do anything to that(maybe reposition it a little bit to match with whatever you add but that's about it) so it would be quite time consuming to rewrite 80% of the shit that's already present in the code
really though, open up assets.pk3 and start exploring and come with more specific questions. everything else is covered by google
Edited by bing bang blaow, 06 February 2013 - 02:39 AM.
#9
Posted 06 February 2013 - 03:17 AM
Ty For that Rocket.to do specifically what you brought up: http://www.linux.ucl...u/q3tamenu.html
this is all user interface related. if you want to do more complex things like what RPM implemented you should get into various programming languages(q3 engine is written in C i think?).
but I still believe that at first you should just experiment with the original files using trial and error. I only used this site when I wanted to create something really really specific. also it's 1000 times easier when you modify the original files to your liking because you don't have to (re)write everything you aren't modding, what I mean is that the EXIT button is already in the code and you probably aren't gonna do anything to that(maybe reposition it a little bit to match with whatever you add but that's about it) so it would be quite time consuming to rewrite 80% of the shit that's already present in the code
really though, open up assets.pk3 and start exploring and come with more specific questions. everything else is covered by google
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users




