@coltongit: (quote:) 'I wonder how I can keep a repo updated with remote tracking?'
You already have a git account, so… by using git? https://help.github.com/articles/syncing-a-fork/
You can also use SVN, though it seems most prefer git (at least on github).
Ah, I thought your name represents some affinity for git/github.
P.S.: I’m using SVN, so I can’t help you with git in detail! Github has a nice help section https://help.github.com/.
I’m trying to say at the same time where the main code section for iamamonkey is too, @KuehnhammerTobias.
Either my english, or yours is too bad.
I have absolutely no idea what you mean by that.
Hmm, seems like a blind is leading a blind…
The cheat words, like iamamonkey or iamacheater, have to be somewhere in either the spearmint engine or the spearmint gamecode.
iamamonkey and iamacheater are in code\q3_ui\ui_atoms.c.
You can serch for it! Didn’t you have any IDE? Or are you lazy?
OK, I have modified ui_atoms.c to reference the new function in ui_gameinfo.c, as well as correcting a minor code error. It’s fixed in the latest gist of my version of the file. ui_atoms.c uses a new cheat for the function, entitled iamagod.
It doesn’t compile with the new function… Here’s what I get for it:
Colton@ColtonsPC ~/mint-arena
$ make
make[1]: Entering directory ‘/home/Colton/mint-arena’
Building in build/release-mingw32-x86_64:
PLATFORM: mingw32
ARCH: x86_64
VERSION: 0.3_GIT_914aff4-2016-05-25
COMPILE_PLATFORM: cygwin
COMPILE_ARCH: x86_64
CC: /usr/bin/x86_64-w64-mingw32-gcc
WINDRES: /usr/bin/x86_64-w64-mingw32-windres
CFLAGS:
-Wall -fno-strict-aliasing -Wimplicit -Wstrict-prototypes -DUSE_ICON
-DWINVER=0x501 -m64 -DPRODUCT_VERSION="0.3_GIT_914aff4-2016-05-25"
-DBASEGAME="baseq3" -Wformat=2 -Wno-format-zero-length -Wformat-security
-Wno-format-nonliteral -Wstrict-aliasing=2 -Wmissing-format-attribute
-Wdisabled-optimization -Werror-implicit-function-declaration -MMD -DNDEBUG
-O3 -ffast-math
LDFLAGS:
LIBS:
-lws2_32 -lwinmm -lpsapi
Output:
baseq3/mint-cgame_x86_64.dll
baseq3/mint-game_x86_64.dll
missionpack/mint-cgame_x86_64.dll
missionpack/mint-game_x86_64.dll
baseq3/vm/mint-cgame.qvm
baseq3/vm/mint-game.qvm
missionpack/vm/mint-cgame.qvm
missionpack/vm/mint-game.qvm
make[2]: Entering directory '/home/Colton/mint-arena'
CGAME_CC code/q3_ui/ui_atoms.c
code/q3_ui/ui_atoms.c:818:15: error: ‘UI_SPUnlock_Skill5_f’ undeclared here (not in a function)
{ "iamagod", UI_SPUnlock_Skill5_f, 0 },
^
Makefile:1357: recipe for target 'build/release-mingw32-x86_64/baseq3/ui/ui_atoms.o' failed
make[2]: *** [build/release-mingw32-x86_64/baseq3/ui/ui_atoms.o] Error 1
make[2]: Leaving directory '/home/Colton/mint-arena'
Makefile:786: recipe for target 'targets' failed
make[1]: *** [targets] Error 2
make[1]: Leaving directory '/home/Colton/mint-arena'
Makefile:760: recipe for target 'release' failed
make: *** [release] Error 2
& can you also please add txt support to this forum as well? I do have the main code function for it in ui_gameinfo.c as you might already know.
Probably you should declare ‘UI_SPUnlock_Skill5_f’ in a header? Though, I didn’t have a look on your code.
Why are you so immune against the hints people already told you? I mean, Zack already said you should at least make diff.patches to show on gist, I bet nobody want to search for your code changes, even more when nobody is really much interested in unlock maps in nightmare mode…
So, do what Zack already said, make readable git diff! THAN, eventually(!) people will help you fixing your problems.
BTW, zturtleman is not nobody, so if he is willingly to point you in the right direction, so if I were you, I would be happy and grateful.
I don’t want to belittle you, but it seems to me you look for some Quake 3 coding basics. Check these tutorials, they are outdated, but they helped me a lot when I was starting to play with the Q3 code: Code3Arena
Wouldn’t that mean I would have to make a .h file to use when the function’s compiled? And define it there? I’m not really sure how to do that, but I think it’s #DEFINE (function name) or something like that.
q3_ui has it’s header file already, you don’t need to make a new header (.h) file. Open ui_local.h, there all the needed functions are declared (iirc).
I already asked you, why aren’t you searching for the code you need for yourself? Do you have MSVC or something?
You simply can search for ‘UI_SPUnlockMedals_f’ or something, as a reference, and than create your own function…
I really wan’t to know what IDE you use! NOTE: Discussion is no ‘one-way street’!
I use Cygwin to compile the engine/gamecode BTW. & I already HAVE the function ready to go in ui_gameinfo.c. EDIT: Yes, it seems it wasn’t declared there. Now it is.
Cygwin is for compiling your code. You need a program to write your code (with a search function etc.)
You can’t write code with Cygwin. You need an IDE: https://en.wikipedia.org/wiki/Integrated_development_environment
like MSVC:
I copy the code out of the raw stuff and write it using Notepad. Not really a code geek, but at least it’s minimalist! LOL
Notepad++ is also minimalist, and can let you code @KuehnhammerTobias. Also I don’t like how much space MSVC costs on your HDD.
Yes I know, most modern HDD only have 15 GB space… If you have one with more than 20 GB you need an extra fan!
I have a 1TB HDD in my laptop, but I don’t really have that much space on it right now… Just over 100GB left…
c’mon most of them are free. Coding with Notepad: 